info/mirror-textfiles.com
1
0
Fork 0
mirror of https://github.com/opsxcq/mirror-textfiles.com.git synced 2025-08-11 20:34:20 +02:00
Code Issues Releases Wiki Activity

update

Browse Source
This commit is contained in:
OPSXCQ
2018-01-08 04:15:18 -03:00
parent ba0d2aaa4b
commit 2583126416
80 changed files with 103612 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

554
textfiles.com/internet/ncsa.em Normal file
View File

@@ -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: <kadie@cs.uiuc.edu>
Date: Tue, 23 Apr 91 04:42:14 -0500
Sender: "Carl M. Kadie" <kadie@cs.uiuc.edu>
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: <kadie@cs.uiuc.edu>
Date: Tue, 23 Apr 91 04:42:59 -0500
Sender: "Carl M. Kadie" <kadie@cs.uiuc.edu>
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: <kadie@cs.uiuc.edu>
Date: Tue, 23 Apr 91 04:43:19 -0500
Sender: "Carl M. Kadie" <kadie@cs.uiuc.edu>
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

53
textfiles.com/internet/nearnet Normal file
View File

@@ -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.

1273
textfiles.com/internet/netcat.txt Normal file
View File

File diff suppressed because it is too large Load Diff

100
textfiles.com/internet/netcount.hst Normal file
View File

@@ -0,0 +1,100 @@
<NIC.MERIT.EDU> /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.

9971
textfiles.com/internet/netguide.txt Normal file
View File

File diff suppressed because it is too large Load Diff

463
textfiles.com/internet/netiquette Normal file
View File

@@ -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.

.

152
textfiles.com/internet/netmail.info Normal file
View File

@@ -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 <Alderson@SU-Score> 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:<youruid@yournode.BITNET>
RCPT TO:<user@node.UUCP>
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.

42
textfiles.com/internet/netnews.10 Normal file
View File

@@ -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


466
textfiles.com/internet/netserv Normal file
View File

@@ -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

51
textfiles.com/internet/netsurf Normal file
View File

@@ -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.


365
textfiles.com/internet/networks.lis Normal file
View File

@@ -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

265
textfiles.com/internet/news_dw.txt Normal file
View File

@@ -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 <Tyagi@houseofkaos.abyss.com>; 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 <Tyagi@houseofkaos.abyss.com>; 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 </afs/andrew.cmu.edu/service/mailqs/q002/QF.ciGNUqa00bkU40OEFk>;
Wed, 10 Aug 1994 23:17:11 -0400 (EDT)
Received: from ccon-weh.weh.andrew.cmu.edu via qmail
ID </afs/andrew.cmu.edu/usr23/sk4p/.Outgoing/QF.4iGNUpi00bkU45mMw4>;
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: <EiGNUpe00bkU45mMoq@andrew.cmu.edu>
Date: Wed, 10 Aug 1994 23:17:09 -0400 (EDT)
From: Shawn Clayton Knight <knightster+@CMU.EDU>
To: Tyagi <Tyagi@houseofkaos.abyss.com>
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 <topic>' where
<topic> 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 <topic>'.
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 <obj> = <field>;/<oldtxt>/<newtxt>
changes the text of a field
detail <obj>:<tag> [;tag2;tag3;...] = <textstring>
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
<bogus> - 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

62
textfiles.com/internet/nfs494.hi Normal file
View File

@@ -0,0 +1,62 @@
<NIC.MERIT.EDU> /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.

3015
textfiles.com/internet/nha-003.txt Normal file
View File

File diff suppressed because it is too large Load Diff

27
textfiles.com/internet/nis.txt Normal file
View File

@@ -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.

946
textfiles.com/internet/nixpub Normal file
View File

@@ -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 <mason@tmsoft> / 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 <ssanbeg@visual.spk.wa.us>
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 <no password>. 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 <ggw%wolves@cs.duke.edu>
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

989
textfiles.com/internet/nixpub.txt Normal file
View File

@@ -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 <mason@tmsoft> / 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 <no password>. 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

65
textfiles.com/internet/northwes Normal file
View File

@@ -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

91
textfiles.com/internet/ns101.txt Normal file
View File

@@ -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!)

57
textfiles.com/internet/nsfnet Normal file
View File

@@ -0,0 +1,57 @@
<NIS.NSF.NET> [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.

6246
textfiles.com/internet/nug.txt Normal file
View File

File diff suppressed because it is too large Load Diff

1681
textfiles.com/internet/nwerthy.man Normal file
View File

File diff suppressed because it is too large Load Diff

2153
textfiles.com/internet/o Normal file
View File

File diff suppressed because it is too large Load Diff

143
textfiles.com/internet/onet Normal file
View File

@@ -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

268
textfiles.com/internet/packet.txt Normal file
View File

@@ -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 ------


741
textfiles.com/internet/pdial Normal file
View File

@@ -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
<cr> 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
<cr> 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
<cr><cr><cr> at 1200 baud or '@'<cr><cr> 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 <cr><cr><cr> at 1200 baud or '@'<cr><cr> 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

84
textfiles.com/internet/posting.rsk Normal file
View File

@@ -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.

170
textfiles.com/internet/powrpost.net Normal file
View File

@@ -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!


120
textfiles.com/internet/prepnet Normal file
View File

@@ -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:____________________________________________

296
textfiles.com/internet/privatiz.nre Normal file
View File

@@ -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

256
textfiles.com/internet/q Normal file
View File

@@ -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 <hanker@binbi.roy.or.us>
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!

279
textfiles.com/internet/r Normal file
View File

@@ -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

189
textfiles.com/internet/read.me Normal file
View File

@@ -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.

339
textfiles.com/internet/rfc2441.txt Normal file
View File

@@ -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]

146
textfiles.com/internet/s Normal file
View File

@@ -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

430
textfiles.com/internet/sbjan95.www Normal file
View File

@@ -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</a>
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

541
textfiles.com/internet/sec_ftp.faq Normal file
View File

@@ -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 <command> | <command>\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 <mjr@tis.com>
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);

365
textfiles.com/internet/sendmail Normal file
View File

@@ -0,0 +1,365 @@
From: Eliot Lear <lear@NET.BIO.NET>
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.

364
textfiles.com/internet/sendmail.faq Normal file
View File

@@ -0,0 +1,364 @@
From: Eliot Lear <lear@NET.BIO.NET>
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.

56
textfiles.com/internet/sendmailwb.txt Normal file
View File

@@ -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

284
textfiles.com/internet/services.faq Normal file
View File

@@ -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 <aftp-list@netcom.com>. 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.


36192
textfiles.com/internet/sitelist Normal file
View File

File diff suppressed because it is too large Load Diff

570
textfiles.com/internet/sl-inet.txt Normal file
View File

@@ -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 <LIBPACS@UHUPVM1.BITNET>
Subject: Special Librarians and the Internet
To: Ernest Perez <EPEREZ@UTDALLAS.BITNET>
From: "Sharyn Ladner, Business Librarian, University of Miami Richter Library"
<SLADNER@UMIAMI>
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.
==== <g INTERNET> 13 links in glossary topic

152
textfiles.com/internet/slfp.faq Normal file
View File

@@ -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.

106
textfiles.com/internet/slip_win.faq Normal file
View File

@@ -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

1450
textfiles.com/internet/slipdoc.txt Normal file
View File

File diff suppressed because it is too large Load Diff

704
textfiles.com/internet/smiley Normal file
View File

@@ -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 %-<I> 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 ===============================

1594
textfiles.com/internet/soc-sci.txt Normal file
View File

File diff suppressed because it is too large Load Diff

390
textfiles.com/internet/softhis.txt Normal file
View File

@@ -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 <AA06358@pit-manager.MIT.EDU>; Sun, 12 Apr 92 12:36:05 -0400
Date: Sun, 12 Apr 92 12:36:05 -0400
From: Mr Background <daemon@pit-manager.MIT.EDU>
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: <spaf-software_698911822@cs.purdue.edu>
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: <spaf-software_692072013@cs.purdue.edu>
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 <ONASCH@iravcl.ira.uka.de> 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 <crash@ckctpa.uucp>,
and available from Larry Rosenman <ler@lerami.lonestar.org>. Also,
Matt Dillon <dillon@overload.berkely.ca.us>, 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
<connolly@coins.cs.umass.edu> and maintained by Richard Welty
<welty@lewis.crd.ge.com>. 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 <pc@bellcore.com>
A TOPS-20 reader was developed by Dave Edwards of SRI
<dle@kl.sri.com>, 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 <seb1525@mvs.draper.com> 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

838
textfiles.com/internet/soup12.txt Normal file
View File

@@ -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:
prefix<TAB>area name<TAB>encoding[<TAB>description[<TAB>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:
offset<TAB>subject<TAB>author<TAB>date<TAB>mesgid<TAB>
refs<TAB>bytes<TAB>lines[<TAB>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:
offset<TAB>subject<TAB>author<TAB>date<TAB>bytes<TAB>lines[<TAB>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 <address>
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:
prefix<TAB>reply kind<TAB>encoding
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 name<TAB>encoding[<TAB>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.
sendme<TAB>area<TAB>selector[<TAB>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.

981
textfiles.com/internet/source12.txt Normal file
View File

@@ -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:<msdos.filedocs>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 <x> package in source newsgroup <y> 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 <x>."
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 <x>," where <x> 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 <x> 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 <x> 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 <x>."
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
<adam@soda.berkeley.edu>, 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 <x>?" Say,
"Would someone please tell me where I can get <x>, or what's
available that does <x>? 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 <wohler@sap-ag.de> provided many of the addresses in the
"Other mail servers" section above, and provided suggestions for
several other sections. Andrew Purshottam <andyp@ibmpa.awdpa.ibm.com>
also provided many mail archive server addresses. Bjorn P. Brox
<brox@dms.corena.no> provided information about Trickle.
These people provided feedback and corrections:
Denis.Buffenoir@inria.fr
Rusty Carruth <rusty@anasazi.com>
Tom Cunningham <tomc@bouwsma.sps.mot.com>
Eric Gross <ehg@research.att.com>
Dan Jacobson <Dan_Jacobson@ATT.COM>
Peter Deutsch <peterd@opus.cs.mcgill.ca>
<FACN320@saupm00.bitnet>
Charles Geyer <charlie@umnstat.stat.umn.edu>
Edwin Kremer <edwin@cs.ruu.nl>
Rene Lampe <yzrnur!rene@sq.uucp>
Kent Landfield <kent@IMD.Sterling.COM>
Jonathan Leech <leech@cs.unc.edu>
Lee McLoughlin <L.McLoughlin@doc.ic.ac.uk>
Allen McAuley <s3007588@mackay.mpce.mq.edu.au>
Mark Maimone <mwm@cmu.edu>
Michael Meyer <mikem+@andrew.cmu.edu>
Dick Munroe <munroe@dmc.com>
Petri Ojala <ojala@funet.fi>
Douglas Quist <quist@thing1.sim.es.com>
George V. Reilly <gvr@cs.brown.edu>
John_Rouillard@dl5000.bc.edu
Timo Salmi <ts@uwasa.fi>
Rich Salz <rsalz@bbn.com>
Heribert Schuetz <schuetz@informatik.tu-muenchen.de>
Dan Shearer <ccdps@lux.levels.unisa.edu.au>
Richard S. Smith <RSS%CALSTATE.bitnet@VM.USC.EDU>
Mike Stump <mrs@charlie.secs.csun.edu>
Steve Sullivan <sullivan@teal.csn.org>
Steve Summit <scs@adam.mit.edu>
Sydney S. Weinstein <syd@DSI.COM>
Joe Wells <jbw@bigbird.bu.edu>
Jon Whellams <mgjmw@cc.flinders.edu.au>
George Wilson <gwilson@mrj.com>
Bill Wohler <wohler@sap-ag.de>
Christophe Wolfhugel <wolf@frwolf.gna.tfd.com>
Adri Verhoef <a3@rivm39.rivm.nl>
Ed Vielmetti <emv@msen.com>
------------------------------
--
Jonathan Kamens | OpenVision Technologies, Inc. | jik@security.ov.com
-------------------------------------------------------------------------------

1009
textfiles.com/internet/sp4rpt.txt Normal file
View File

File diff suppressed because it is too large Load Diff

1083
textfiles.com/internet/spamfaq.txt Normal file
View File

File diff suppressed because it is too large Load Diff

418
textfiles.com/internet/span01.vir Normal file
View File

@@ -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 <a bunch of garbage>
NCP> DEFINE OBJECT TASK USER DECNET PASSWORD <a bunch of garbage>
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 <renamed file>)
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

178
textfiles.com/internet/span03.vir Normal file
View File

@@ -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=<something> !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 <something> !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 <type an INCORRECT password>
$ MCR NCP DEF OBJECT TASK PASSWORD <type an INCORRECT 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

BIN
textfiles.com/internet/span04.vir Normal file
View File

Binary file not shown.

396
textfiles.com/internet/spec1130.txt Normal file
View File

@@ -0,0 +1,396 @@
* SPECIAL INTERNET CONNECTIONS: Last Update: 11/30/92 *
* Compiled By: Scott Yanoff - yanoff@csd4.csd.uwm.edu *
* A + by an entry designates new entries/changes to the list since last update *
* Finger yanoff@csd4.csd.uwm.edu to find ways to receive this list!
-Agricultural Info. telnet psupen.psu.edu or telnet 128.118.36.5
PENpages (Login: PNOTPA)
telnet caticsuf.csufresno.edu or telnet 129.8.100.15
CSU Freso ATI-NET (Login: super)
telnet eureka.clemson.edu or telnet 130.127.8.3
CUFAN (Clemson U Forestry & Ag. Net.) (Login: PUBLIC)
ftp ftp.sura.net (get file pub/nic/agricultural.list,
it contains agricultural email lists & services.)
mail almanac@oes.orst.edu
body-of-message: send guide also: send mail-catalog
offers: Agricultural info (livestock reports, current market prices, etc.)
+Almanac mail servers mail almanac@esusda.gov
mail almanac@ces.ncsu.edu
mail almanac@oes.orst.edu
mail almanac@ecn.purdue.edu
mail almanac@silo.ucdavis.edu
offers: USDA market news, articles about the use of computer in agricultural
science, and Extension Computing Technology Newsletters.
In body of letter: send guide
-Am. Philos. Assoc. telnet atl.calstate.edu or telnet 130.150.102.33
offers: BBS for APA. (Login: apa)
-Amateur Radio mail info@arrl.org
offers: Ascii files about Amateur Radio and electronics.
Body of letter: help, info, send <filename> 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@<INSERT ONE OF ABOVE ADDRESSES HERE>
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: <last name>)
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 <address here> 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 <your full name> 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.

805
textfiles.com/internet/sprint Normal file
View File

@@ -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 <CR> <CR>
for your baud/parity type. For
E,7,1 1200/2400, type <CR> 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<CR>
dumb terminal.
6 NUI Input: After SprintNet gives
the "@" prompt, type "ID ;" and @ID ;ABCD<CR>
then your ID code, follwed by a PASSWORD=123456<CR>
<CR>. Then enter your password
followed by another <CR>. If you
don't have an NUI, you can always
access systems which allow collect
calls.
7 At the "@" prompt, you can enter @02341123456790<CR>
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 "<CR>@<CR>" 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 "<NUA>,<ID>,<PW>" 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?<CR>"
The PAD will respond with: "PAR1:<VALUE>,2:<VALUE>,..."
To modify parameter(s): "SET? <PARM>:<VALUE>,<PARM>:<VALUE>,..."
The PAD will respond with: "PAR<PARM>:<VALUE>,..."
ITI Parameters
--------------
To display current parameters: "PAR? 0,<PARM>,<PARM>,..."
The PAD will respond with: "PAR<PARM>:<VALUE>,<PARM>:<VALUE>,..."
To modify parameter(s): "SET? 0:33,<PARM>:<VALUE>,<PARM>:<VALUE>,..."
The PAD will respond with: "PAR0:33,<PARM>:<VALUE>,..."
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.
<NUA> DISCONNECTED AA BB TT:TT:TT:TT CCC DD
Where:
<NUA> 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 <CR><CR>
7 1 EVEN 300-1200 HALF <CR>;<CR>
7 1 EVEN 2400 FULL @<CR>
7 1 EVEN 2400 HALF @;<CR>
8 1 NONE 300-1200 FULL <CR>D<CR>
8 1 NONE 300-1200 HALF <CR>H<CR>
8 1 NONE 2400 FULL @D<CR>
8 1 NONE 2400 HALF @H<CR>
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
----------- -------------------------------------------------------------
<NUA> Connects to the host specified by that NUA.
C <NUA> 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 <TERM> Changes the terminal specification to that of <TERM>.
MAIL Request connection to SprintNet Telemail.
TELEMAIL Request connection to SprintNet Telemail.
ID ;<ID> Enter NUI, <ID> 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=-=-=-=-=-=-=-=-=-=

1571
textfiles.com/internet/sslfaq.103 Normal file
View File

File diff suppressed because it is too large Load Diff

380
textfiles.com/internet/sterling Normal file
View File

@@ -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)


132
textfiles.com/internet/style.txt Normal file
View File

@@ -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 <AA06238@pit-manager.MIT.EDU>; Sun, 12 Apr 92 12:33:06 -0400
Date: Sun, 12 Apr 92 12:33:06 -0400
From: Mr Background <daemon@pit-manager.MIT.EDU>
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: <spaf-style_698911845@cs.purdue.edu>
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: <spaf-style_692072017@cs.purdue.edu>
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

1526
textfiles.com/internet/surfing.int Normal file
View File

File diff suppressed because it is too large Load Diff

1401
textfiles.com/internet/surfpoly.txt Normal file
View File

File diff suppressed because it is too large Load Diff

466
textfiles.com/internet/surfwild.txt Normal file
View File

@@ -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.

1003
textfiles.com/internet/sw56gu.txt Normal file
View File

File diff suppressed because it is too large Load Diff

3471
textfiles.com/internet/tcp-ip-a.txt Normal file
View File

File diff suppressed because it is too large Load Diff

1761
textfiles.com/internet/tcp-ip-i.txt Normal file
View File

File diff suppressed because it is too large Load Diff

2821
textfiles.com/internet/tcpadmin Normal file
View File

File diff suppressed because it is too large Load Diff

1706
textfiles.com/internet/tcpip.hac Normal file
View File

File diff suppressed because it is too large Load Diff

1233
textfiles.com/internet/tcpiso.txt Normal file
View File

File diff suppressed because it is too large Load Diff

151
textfiles.com/internet/telecom.txt Normal file
View File

@@ -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 <ALT> 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
<F5>. Then, you can press <F5> 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.
===========================================================

BIN
textfiles.com/internet/telenet.access Normal file
View File

Binary file not shown.

265
textfiles.com/internet/telenet.directo Normal file
View File

@@ -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 ! ! <No response>
!60968 ! ! <No response>
+-------+-----------+-------------------------------------------+
!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" <CR>
!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 ! ! <Connect/disconnnect>
+-------+-----------+-------------------------------------------+
!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 ! ! <no response>
!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

963
textfiles.com/internet/telex_an.int Normal file
View File

@@ -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 <Telecom-Request@delta.eecs.nwu.edu>); 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 <Telecom-Request@delta.eecs.nwu.edu>
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]

492
textfiles.com/internet/teln0418.txt Normal file
View File

@@ -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<oint>.F<idoNode>.N<et>.Z<one>.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 <B>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.


168
textfiles.com/internet/telnet.txt Normal file
View File

@@ -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 <cr> 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 <host>
or
TELNET <cr> followed by OPEN <host> 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 (<cr> or <cr><lf> -- 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.
==== <g REMOTE> 2 links in glossary topic


243
textfiles.com/internet/the-plan Normal file
View File

@@ -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: <jennifer@algol.astro.virginia.edu>
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 <must> 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

112
textfiles.com/internet/thumb.txt Normal file
View File

@@ -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.

1021
textfiles.com/internet/top1000.use Normal file
View File

File diff suppressed because it is too large Load Diff

1702
textfiles.com/internet/tour.crt Normal file
View File

File diff suppressed because it is too large Load Diff