![]() |
|
|
|
|
|
|
VM/COM, May - June 1986
1
-
OO OO OOO OOO // OOOOOOO OOOOOOO OOO OOO
OO OO OO OOO OO // OO OO OO OO OO OOO OO
OO OO OO O OO // OO OO OO OO O OO
oo oo oo oo // oo oo oo oo oo
oooo oo oo // oo oo oo oo oo oo
oo oo oo // ooooooo ooooooo oo oo
0 ------------------------------------------------------------
May/June 1986 Edition Volume 3 Number 3/4
- CsNews Network Newsletter
-
-
Staff:
0 Michele Robinson CSMICH at MAINE Editor
Andrew T. Robinson ANDY at MAINE CsNews Director
David Eckhardt DAE at PSUVAX1 Assistant Editor
Prof. G. Markowsky MARKOV at MAINE Faculty Advisor
-
0 Ôçççççççççççççççççççççççççççççççççççççççççççççççççççççççä
³ Newsletter article contribution Userid: CSNEWS@MAINE ³
³ ³
³ Contributions from readers welcomed and encouraged! ³
¨ççççççççççççççççççççççççççççççççççççççççççççççççççççççç]
1
0 Vm-Com Issue 3.1
-
0 Table of Contents
+ _____ __ ________
- Introduction to Vm/Com 3.3 . . . . . . . . . . . . . . . 1
CSNEWS Notes . . . . . . . . . . . . . . . . . . . . . . 2
Life in the Fast Lane: Column #2 . . . . . . . . . . . . 4
The Beginning of The VAX Toolbox . . . . . . . . . . . . 8
PSYCHNET . . . . . . . . . . . . . . . . . . . . . . . . 9
LTERM and SIM3278 . . . . . . . . . . . . . . . . . . . . 10
CS Books . . . . . . . . . . . . . . . . . . . . . . . . 13
Games--And a Look at the Future . . . . . . . . . . . . . 15
Why I Hate Computer Games . . . . . . . . . . . . . . . . 17
OpCodes . . . . . . . . . . . . . . . . . . . . . . . . . 19
-
-
-
-
-
-
-
-
-
-
-
-
-
2
1
0 Vm-Com Issue 3.3
0 Introduction to Vm/Com 3.3
+ Introduction to Vm/Com 3.3
-
Hello again Vm/Com fans! Yes much to everyone's
surprise (including mine) Vm/Com is still alive, many months
late, but still alive. I suppose this is a good time to ask
help from those of you who would like to keep seeing this
newsletter in the future. Vm/Com is running out of articles
and running out of people to write articles. So in other
words I need more people to write something, write anything,
write about why you hate your least favorite computer
lanquage, tell the world what its like to stay up all night
writing massive impressive programs, WRTIE SOMETHING!
Vm/Com needs YOU!
0 In this issue you can find part two of 'Life in the Fast
Lane', two articles on new newsletters (at least they were
new when I got the articles). One describes a newsletter
written just for the Vax world and the other describes
Psychnet a psychology newsletter. Next is an article
describing SIM3278 and LTERM and then a few 'opinion'
articles. First is a review of a few computer books then
there are two opposing views on computer games. And last but
not least OpCodes
0 Until the next issue comes out... (whenever that manages
to happen) think about writing an article. Read and enjoy!
See ya in V3-5.
0 Michele Robinson,
Editor
-
-
-
-
-
-
-
- 1
1
0 Vm-Com Issue 3.3
0 CSNEWS Notes
+ CSNEWS Notes
0 Andrew T. Robinson, (ANDY@MAINE)
-
Well, it seems that we are finally going to see another
VM/COM issue after a long absence. Actually, the material
for this one has been lying around for a while as I
understand it. We simply haven't had enough to put together
a reasonably-sized issue. Well, here it is, in all its
glory... and with it, a new heaping portion of CSNEWS NOTES!
0 As you have heard many times in the past, CSNEWS is being
largely rewritten to improve its speed and decrease its
resource usage. This work has been progressing unusually
slowly due to the fact that our all-volunteer programming
staff does not seem to have the time after other things to
complete the many necessary projects associated with such a
large-scale upgrade of software.
0 However, after much adieu, it seems that some portions of
the new software system are slowly falling into place.
Among these include several new utilities specifically
designed with the server-writer in mind. Some of these
utilities will be made available to interested users as they
are completed. They are in what would rougly correspond to
the initial development and "alpha testing" stages at this
point in time. If anyone is interested in what types of
utilities we are working on, feel free to contact me by e-
mail at ANDY@MAINE.BITNET.
0 Some major improvements for the CSNEWS spoolfile handler
and interface and the CSBB bulletin board system are in the
discussion stage at this time. We are planning to add such
enhancements as accurate mail-header parsing and batch-mode
execution of CSNEWS commands submitted in mail files or
other types of files.
0 One enhancement that has already been applied to CSBB is
that of the INFORM LIST for a topic. Users on the inform
list for a given topic will receive each new entry for that
topic in a mailfile as it arrives. In this manner, CSNEWS
provides a primitive form of interest list processing, with
automatic collection of entries into forum-style files
(CSNOTICEs).
0 As a closing note, I would like to add some comments
about Vm/Com writership. In 1985, we had a very successful
year as far as Vm/Com goes. However, with the onset of
1986, we found that the volume of material coming in for new
Vm/Com issues was insufficient to meet our monthly
requirements. Many of our writers simply stopped producing,
others graduated, and still others could not be contacted.
0 2
1
0 Vm-Com Issue 3.3
0 Vm/Com is nothing more than a collection of articles
submitted by users across the network who want to share
their computing experiences and knowledge with others. I
know there are many, many talented individuals in the BITNET
community who have such experience and knowledge, and I
would like to invite them to consider writing an article or
two for Vm/Com. The most common excuses we hear from people
we ask is "I can't write" and "I don't have the time." For
those who can't write, that is why we have an editor,
capable of fixing even the most botched copy so that it
comes off reading well. For those who claim lack of time, I
would ask you to consider how much time a Vm/Com article
takes. It is not very long, and I honestly believe that
most people could find the time if they looked.
0 Vm/Com lives or dies by the contributions of its readers.
At this point in time it is deathly ill, and we need more
articles to bring it back to its previous vitality. If you
have an inspiration, WRITE! Free-write, it doesn't make any
difference, as long as you get it down. Fix it up so that
its readable and pass it along to us. Any submission will
be considered, and if it's computer related (humorous,
instructional, or narrative) we'll probably find a place for
it in a future issue!
0 Well, I guess I'll call it quits for this collection of
random sentences. Hope to see you all next issue (provided
we get enough articles to put the next issue out)!
-
-
-
-
-
-
-
-
-
3
1
0 Vm-Com Issue 3.3
0 Life in the Fast Lane: Column #2
+ Life in the Fast Lane: Column #2
0 Chris Condon BITLIB@YALEVMX
-
This is old news, but there are hackers in BITNET. You
aren't surprised, I'm sure. "Hacker" isn't a dirty word,
and all hackers are NOT slavering, demented, animals waiting
to break into, crash, and destroy systems, illegally using
their resources, plundering userids that are not their own,
and making a general mess out of everything.
0 Only some are.
0 That is an exaggeration, of course, but it is not too
far from reality (except for the "slavering" part). There
exists in this network a group of hackers who broke into a
userid at Fermilab via BITNET. They used the RELAY
conference machine system to keep in contact.
Administration types at Cornell University, hearing of this,
came to this conclusion:
0 "The Cornell Relay has been shut down forever due
to the misuse of BITNET by some hackers in West Germany
who discussed their trade on the Relay. It is
Cornell's desire to not be associated with the Relay
system in the future..."
0 The reaction by these people seems a bit reactionary and
unfounded, but that is not the case. There are several
factions in BITNET that would like to see students
completely banned from the network, or chatting banned from
the network, or both. These are not forces to be reckoned
with. They are in a positions of power to such things at
their own nodes, given enough reason or the right excuse.
The hackers breaking into Fermilab turned out to be a
convenient excuse. It need not be anything so extreme.
0 Their actions, your actions, my actions, are a
reflection on the students in BITNET. It has been said (not
enough) that BITNET usage is a privilege. It brings with it
a great responsibility. Everything we do may have far
reaching affects without our knowing it. The hackers that
broke into Fermilab were not from Cornell, had no intention
of getting MAS@CORNELLC shut down, nor did they probably
consider that it would happen.
0 I posted a notice on this subject for the Usage
Guidelines Group via LISTSERV@BITNIC. These are some of the
resonses:
-
0 4
1
0 Vm-Com Issue 3.3
0 "The problem, as I see it, stems from a lack of
moral and ethical standards in the computer world, as
well as the natural inquisitiveness of young people
specifically and computer type people generally. If
these are in fact the reasons, what short term or long
term solutions do we have? At this juncture, I don't
see any (though I'm not a systems person) short of
regulating usage or more dramatically shutting down the
RELAYs. Either of these measures would jeopardize the
quantum leaps we have made in the area of
communications (and as a result intellectual
intermingling). As for the future (if we can survive
this onslaught), it would seem that the new directions
that BITNET and other networks have taken the mainframe
dictates that system development types must work to
provide a safe, yet accessible, environment to work and
play."
0 "I'm not surprised hackers are cracking BITNET
like a egg; once SP/4 with native VTAM and Multi-System
Networking Facility (MNSF) supersedes passthru for
interactive access, such activities will be even more
widespread, and a lot of schools will simply shut the
front gate rather than keeping the valuable household
goods under lock and key. Never mind that most schools
have dial ports for access, if the initial breach is
via BITNET, then the network and it's facilities will
be blamed. This is easier, of course, because BITNET
is external to its member schools, and thus the blame
is external. Of course, if each school locked up all
its own facilities the hackers would have no access to
BITNET; that's HARD, and the money is not there for
hard projects that have no visible results."
0 "I don't know what, if any, audit trail is left
from interactive traffic on the net. If there isn't
any, I think there aught to be and installations with
security concerns about chatting should monitor the
traffic for suspicious activity. This of course would
require cooperation among the nodes across which the
chatting is occurring."
0 "We plan to turn off access to Bitnet for anybody
who abuses it. We will use exits in Mailer and RSCS to
make sure a person is allowed to use Bitnet. I don't
think anybody here plans to actively look for hackers,
but if we do come across abuse, or are informed of it
by somebody being harassed at another site, we will
certainly take action."
-
-
5
1
0 Vm-Com Issue 3.3
0 "We were having a real problem with student abuses
of BITNET, so we decided to place restrictions on its
use. We still allow student acess to the network via
mail and sending files, but we took away their ability
to send interactive messages and do queries."
0 "I would just like to make a point about the
policy. A totally restrictive policy, one that makes
absolute and unbending restrictions, especially to
undergraduate students, will have two effects. 1:
Those persons who are borderline on being responsible
or abusive with the system may just go the wrong way,
partly out of challenged to their perception of a
"cold-hearted" system. 2: Students will lack (unless
they break in and get away with it which is what we try
to prevent) a practical education of how real life
computers are implemented. I know these things to be
true from first hand experience, because I used to be
such a hacker. I did get away with it and I did learn
enough to go right into an upper level systems
programming job right out of school. There was no
Bitnet for me then, but there was plenty of other
things. The school I attended had a very closed
policy. They were, however, not effective in
implementing that policy, and so some of us got into
the system.
0 "Not everyone who "breaks in" will avoid doing
damage. Not everyone who "breaks in" will learn things
from it. I am NOT suggesting to let this happen. I AM
suggesting that alternatives be put in place to make it
totally unneeded for a student to "break in". Remember
that the undergrad students who will not be going on to
graduate school are the ones seeking a more practical
education (compared to graduate students). Access to a
network (WITH SUPERVISION) will provide more of that
practical education that is not easily acquired from
the classroom. My suggestion is that a policy be
established to deal properly with "curious students"
who show promise. Just how you do this has to depend
on your resources. The academic department(s) involved
in teaching computers to these students should be
involved in the process. These students will, if
properly taught, can become resources in their own
right, and benefits to industry reflecting on your
school. A first suggestion is to exchange limited and
supervised computer access for some programming work.
I think some students will jump at the chance. They
will be learning in two ways, and you get some
programming done and a more responsible student."
-
- 6
1
0 Vm-Com Issue 3.3
0 Like it or not, someone is looking over your shoulder.
Maybe you won't get caught when you do something
irresponsible via BITNET, but somebody will pay the
consequences. Somebody out there is looking for an excuse to
shut you, or some other student, out of BITNET. He is not an
ogre or an evil person. The actions of some students have
simply led him to believe that shutting students out is a
good thing. It will take your example to convince him
otherwise.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
0 7
1
0 Vm-Com Issue 3.3
0 The Beginning of The VAX Toolbox
+ The Beginning of The VAX Toolbox
0 Bob Boag, (BOAG@MUVMS1)
-
Some time ago, while chatting on RELAY, I joined a
conversation in which everyone was talking about
newsletters. I discovered that many newsletters existed,
varying in topics from using IBM's computers, to science
fiction and fantasy, to outrageous comedy, to what's new in
chatting. Surprisingly, I noticed a vacant spot in this
list of topics. A newsletter did not exist (that I could
find) for the user's of VAX computers. So, as you can
guess, I started one which I called The VAX Toolbox.
0 The main idea I had in starting this newsletter
(magazine) was to help make life easier for the VAX/VMS and
UNIX users. This newsletter is published monthly, and is
just loaded full of articles about DCL (Digital Command
Language), The Librarian, System Services, Run-Time Library
Routines, the EDT editor, JNET, and much more. So, if you,
or anyone you know would be interested in receiving such a
newsletter, please send electronic mail to
|