TeXhax@cs.washington.edu (TeXhax Digest) (10/26/89)
TeXhax Digest Tuesday, October 24, 1989 Volume 89 : Issue 95
Moderators: Tiina Modisett and Pierre MacKay
%%% The TeXhax digest is brought to you as a service of the TeX Users Group %%%
%%% in cooperation with the UnixTeX distribution service at the %%%
%%% University of Washington %%%
Today's Topics:
%%Moderator`s note: This issue of the Digest is dedicated to Peter Flynn`s
%%file servers.tex. We felt the file was important enough to devote a full
%%issue to it. Please circulate this document or post it in a highly
%%visible TeX location for the benefit of others.
-------------------------------------------------------------------------
Date: Mon, 25 Sep 89 13:06 GMT
From: Peter Flynn UCC <CBTS8001%IRUCCVAX.UCC.IE@UWAVM.ACS.WASHINGTON.EDU>
Subject: This is file servers.tex
Keywords: file servers, information
% SERVERS This is a file describing how computer network users
% can access the various file-servers on the academic and
% research computer networks in order to retrieve TeX-related
% software. This file itself is in the public domain and
% may freely be copied without restriction.
%
% New users
% --------- To process this document, type (usually)
%
% TEX SERVERS
%
% When it has finished, type the command for your local
% printer driver, usually in the form
%
% DVIxxx SERVERS
%
% replacing the `xxx' with the abbreviation for the printer
% you are actually using, as detailed in your local or site
% doicumentation. You should consult your local TeX support
% person for details of what printers you can use. On some
% networks and mainframes you may have to type an additional
% command to submit the print job to a shared printer.
%
% [The line above contains a CTRL-Z to halt typeout at this point.]
% [Manufacturers' distributions may specifically modify the above text.]
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\newcount\version\newcount\revision\newtoks\date
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Status [Please add change dates if you update this file]
% ------
% 1st draft (Karlsruhe, September 1989) Peter Flynn <cbts8001@vax1.ucc.ie>
% Revised 30/9/89, PF, Cork
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\version=1 \revision=2 \date={September 1989}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% First, some setting-up: if you are printing the plain ASCII version of this
% file, ignore this stuff.
\magnification=\magstep1
\font\bx=cmssbx10
\font\bf=cmssdc10
\font\trm=cmr7
\font\tit=cmti7
\font\sc=cmcsc10
\font\btt=cmtt10 scaled \magstep1
\font\sans=cmss10
\parskip=\smallskipamount
\catcode`\<=\active \catcode`\>=\active
\def<{\ifnum\fam=\ttfam\char'074 \else$\langle$\fi}
\def>{\ifnum\fam=\ttfam\char'076 \else$\rangle$\fi}
\def\element#1 {\item{{#1}}}
\def\csc#1{{\sc\lowercase{#1}}}
\def\nl{\hfil\break}
\spaceskip=3pt plus3pt minus2pt
\headline={{\trm Version \number\version.\number\revision\hfil\ifnum\pageno=1
\else{\tit Network Sources of \TeX ware}\fi\hfil\the\date}}
%
% Now the text
%\vfill\eject
\centerline{{\bx{}NETWORK SOURCES OF \TeX{} WARE (servers)}}
\bigskip
\centerline{{\bf{}How to get public domain and shareable software}}
\centerline{{\bf{}for the \TeX{} typesetting system}}
\bigskip
\centerline{Peter Flynn}
\centerline{{\it{}Computer Centre, University College, Cork, Ireland\/}}
\centerline{<{\tt{}cbts8001@iruccvax.ucc.ie}>}
\bigskip
\bigskip
\noindent {\bf{}Introduction}
\noindent On the international computer networks there is a variety of
computers where generous individuals and institutions have placed
freely accessible software, including files for the \TeX{}
typesetting system. These computers are known as {\it{}servers\/}, and
anyone attached to the networks should be able to request copies
of files from these servers.
The \TeX{} software available ranges from simple routines for
formatting, right up to complete implementations of the whole package,
and can be downloaded to your computer for immediate use. Several people
and organisations also operate a mail-order service for those users
without network access.
Before you start to use the servers, you should have a familiarity with
the way in which your local computer systems allows you to access the
network. This varies according to the make of computer, the software
already on it and the network to which you are connected. You should
check with your local computer centre or network operator if you are
unsure.
Please note some software is in the {\it{}public domain\/} ({\sl{}ie\/}~it
can be used by anyone without charge), and some is {\it{}shareware\/}
({\sl{}ie\/}~it can be tried out without charge, but must be registered and
paid for if you continue to use it).
\noindent {\bf{}Principles}
\noindent As with your own electronic mail address, each server has a
{\it{}network address\/}, made up of the server \csc{ID},
the {\it{}nodename\/} and the {\it{}network name\/} or {\it{}domain name\/}.
The first two are separated by an ``at''-sign ({\tt{}@}) and the second two
by a dot. For example, the address <{\tt{}listserv@dhdurz1.bitnet}> is
made up of ``{\tt{}listserv}'' (the \csc{ID} or ``name'' of the server), the
nodename ``{\tt{}dhdurz1}'' (Heidelberg University), and the network or
domain name ``{\tt{}bitnet}''. When you are on the same network as the
server, you can usually omit the network name from the address. On
some networks, the portion after the ``at''-sign contains several
elements separated by dots (eg~{\tt{}sun.soe.clarkson.edu}): in all cases
the name of the domain is the righthandmost element. In the \csc{UK},
the order of the parts of the nodename and domain is usually used
in reverse order: consult your local computer centre or network
operator for details.
You can access the servers by various methods, depending on what
network you yourself are attached to, and what networking facilities
it provides. You should check with your local computer centre or
network operator if you do not know what facilities are currently
provided or how to use them.
The only facility common to all networks is {\it{}electronic mail\/}.
Electronic mail therefore should function across most networks,
including commercial mailing and messaging services. Other facilities
are {\it{}file transfer protocol\/}, known as \csc{FTP};
{\it{}interactive login\/}; and {\it{}interactive messaging\/}.
Not all of these other facilities are available on all networks, and
they do not usually work at all if the server is on another network
using different software to that on your own network.
Whichever method you choose, you use it to send {\it{}commands\/} to the server
address, for example, a command to send a file, followed by the name of
the file you want. These commands are then recognised by the server and
the relevant action taken (eg~sending a file of software back to you).
Provided you have typed the address and command(s) correctly, the result
will be the arrival on your computer of the software you ordered.
\bigskip
\noindent {\bf{}Handling files you have retrieved}
\noindent Plain text files should cause no problems. If the file you are
ordering is not a plain text file (for example, if it is ``binary'':
that is, an executable program, or a compressed archive of files), it
cannot usually be sent in its raw state by electronic mail,
particularly between two machines of different makes, or between
different networks. Remember also that an executable program for one
operating system will not work on a different one: make sure you request
the right files!
Many servers are able to overcome this by encoding such files into
printable characters only, which they {\it{}can\/} then send by electronic mail.
The most commonly-used method (for \csc{IBM} and \csc{DEC} mainframes,
most minis, \csc{UN*X} and \csc{PC}s) is called \csc{UU}encoding, but you will
require the \csc{UUDECODE} program to be on your machine first in order to
decode such files if you order them. The catch is, because this
program is itself binary, and thus not directly sendable by electronic
mail, you must request it in source code form and compile it yourself,
or obtain an executable copy on disk from some other source before
proceeding. Your local University computer centre should be able to
supply a copy of \csc{UUDECODE}. A known location for the source code is
given at the end of this document. Apple Macintoshes use a similar
concept, but differently implemented because of the Mac's filing
system: the program needed for a Mac is called \csc{BINHEX}, and again,
you need to get a copy of it from someone on disk before you can
start.
Collections of related files, especially for \csc{PC}s, Macs and \csc{UN*X},
are often compressed into a single file for ease of transmission.
This is called ``archiving'', and the filename for a \csc{PC} usually
ends with {\tt{}.arc}. A similar mechanism for \csc{UN*X} is called \csc{TAR},
and for Macintoshes it is called \csc{STUFFIT}. To unpack the file once
you have received it, you need a de-archiving program: there are
several available under various names from most bulletin boards and
servers. For \csc{MS-DOS PC}s, the two common ones are called \csc{ARCE} and
\csc{PKUNPAK}; if you are using \csc{UN*X} the \csc{TAR} programs should
already be on your system. The Mac program \csc{UNSTUFFIT} is freely
distributable and should be available from your dealer.
\bigskip
\noindent {\bf{}Known \TeX{} servers as at \the\date}
\noindent Note that there are many more servers handling a wide range of
non-\TeX{} software, text and data; and that there are many other
commands as well---only the most important are given here---as a
general principle, sending the single word ``{\tt{}HELP}'' (without
quotes) to an address claiming to be a server is as good a way as
any of testing its likely usefulness!
\par\parindent=1truein
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}listserv@dhdurz1.bitnet>} \nl
(Heidelberg University--also at various other \csc{EARN/BITNET} nodes---see
below)
\element{\sl{}Access by:\/} Mail, Interactive message, \csc{RSCS FTP}
\element{\sl{}Commands:\/} {\tt{}HELP}
sends you back a help file describing what \csc{LISTSERV} can do.
\element~ {\tt{}SENDME}
followed by the specification of the file you want. The file specs are
all in \csc{IBM VM/CMS} format, consisting of a filename and a filetype
separated by a space.
{\tt{}SEND} and {\tt{}GET} are synonyms for {\tt{}SENDME}.
Some servers will accept a filename and filetype separated by a dot
instead of a space.
\element~ {\tt{}INDEX} sends back a list of files.
\element{\sl{}Examples:\/} {\tt{}sendme listserv filelist}
will send you the list of files on the server.
\element~ {\tt{}help}
would request the help file from the \csc{LISTSERV}.
\element{\sl{}Notes:\/}
If you send your request by mail, the response comes back by mail. If
you send it by interactive message or by \csc{FTP}
(the {\tt{}TELL} or {\tt{}SENDFILE} commands on \csc{IBM VM/CMS};
the {\tt{}send/remote} or {\tt{}send/file} commands on \csc{VAX/VMS JNET}),
the response comes back by file transfer.
\element~ If you are ordering a non-printable (program or archive) file,
you can follow the filetype with the tag ``{\tt{}(UUE}'' in order to have the
file sent in \csc{UU}encoded form, {\sl{}eg\/}
{\tt{}sendme mtex arc (uue}
\noindent $\bullet$$\bullet$ <{\tt{}listserv@tamvm1.bitnet>} \nl
(Texas A\&M) is another \csc{LISTSERV} on \csc{BITNET} and operates in the same
way as the Heidelberg server.
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}texserver@tex.aston.ac.uk>} \nl
(Aston University, Birmingham) \csc{UK} users should use
<{\tt{}texserver@uk.ac.aston.tex}>
\element{\sl{}Access by:\/} Mail, Colour Book \csc{FTP}, Post
\element{\sl{}Commands:\/} {\tt{}HELP}
sends you back a help file describing what \csc{TEXSERVER} can do.
\element~ {\tt{}GET}
followed by the specification of the file you want. The file specs are
all in \csc{VAX/VMS RMS} format, consisting of a subdirectory in square
brackets starting with {\tt{}[tex-archive.~]}, a filename and a filetype
separated by a dot---see `{\sl{}Examples\/}' below.
\element~ {\tt{}DIR}
followed by a directory specification in square brackets. This returns a
list of the files in that directory.
\element\csc{FTP:}
Use your local {\tt{}TRANSFER} command (part of the Colour Book suite of
\csc{XXX} implementations) with the user\csc{ID} `{\tt{}public}' and the
password `{\tt{}public}'. The top-level directory is {\tt{}[tex-archive]}.
A file transfer gateway between \csc{JANET} and \csc{EARN/BITNET} will be
introduced shortly.
\element{\sl{}Examples:\/} {\tt{}get [tex-archive]000directory.list}
will return a directory of all files in the archive.
\element~ {\tt{}get [tex-archive.msdos.tex]sb08tex.arc}
will retrieve the \csc{PC} file (in \csc{ARC} format) containing the
\csc{SB08TEX} implementation of \TeX{}.
\element~ {\tt{}dir [tex-archive.digests.texhax89]}
will return a list of the 1989 issues of the \TeX{} hax bulletin.
\element{\sl{}Notes:\/}
Users outside the \csc{UK}'s \csc{JANET} system using mail access must start
their mail message with the two lines\nl
{\tt{}---}\nl
{\tt{}userid\%nodename.netname@EARN-RELAY}\nl
The first of the two lines must contain just three hyphens on their own.
The second line is {\it{}your own mail return address\/} in
\csc{JANET}-recognisable form, for example
{\tt{}fred\%ubvmsc.bitnet@earn-relay}
\element~ If you are unsure about how to express your return
address in \csc{JANET} form, send mail to Peter Abbott
<{\tt{}abbottp@aston.ac.uk}> (for \csc{DARPA} Internet users, the address
<{\tt{}pabbott@nsfnet-relay.ac.uk}> may be faster; \csc{UUCP/EUNET} users I'm
not too sure about).
\element{\sl{}Post:\/}
You can send snailmail to Peter Abbott, Computing Service, Aston
University, Aston Triangle, Birmingham B4 7ET, England, enclosing blank
formatted media: floppy disks or magnetic tape.
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}archive-server@sun.soe.clarkson.edu>} \nl
(Clarkson University) is the principal \TeX{} ware repository.
\element{\sl{}Access by:\/} Internet \csc{FTP}, Mail
\element{\sl{}Commands:\/}
These vary depending on the implementation of Internet \csc{FTP}. You should
ask your System Administrator for details.
\element{\sl{}Examples:\/}
See below for an example of an Internet \csc{FTP} session.
\element{\sl{}Notes:\/}
This server is also accessible by mail: place your sequence of \csc{FTP}
commands in a mail message to the address above.
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}archive-server@wsmr-simtel20.army.mil>} \nl
is a large file server on the Internet and operates as above for
the Clarkson server. The \TeX{} ware is mainly for \csc{PC}s and is held in
directory {\tt{}<msdos.tex>}. Non-Internet users can use the \csc{TRICKLE}
or \csc{BITFTP} servers detailed below to access these files.
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}bitftp@pucc.bitnet>} \nl
is a mechanism for those without direct access to the Internet to
request files from Internet servers
(eg~<{\tt{}archive-server@sun.soe.clarkson.edu}>)
\element{\sl{}Access by:\/} Mail, \csc{RSCS FTP}
\element{\sl{}Commands:\/}
The body of your mail message or file should contain the sequence of
Internet \csc{FTP} commands you would have used, had you been doing a direct
Internet \csc{FTP} connection yourself.
\element{\sl{}Example:\/} {\tt{}ftp sun.soe.clarkson.edu}\nl
{\tt{}user anonymous guest} (ie, a user\csc{id} called `{\tt{}anonymous}'
and a password called `{\tt{}guest}')\nl
{\tt{}cd} followed by the directory where the file you require resides\nl
{\tt{}get} followed by the name of the file you require\nl
{\tt{}mget} followed by a wildcarded file specification for requesting
several files with similar names, eg {\tt{}texhax89.*}\nl
{\tt{}dir} to list the names of all files in the current directory\nl
{\tt{}quit} to sign off
\element{\sl{}Notes:\/}
[This description needs checking by someone on the Internet]
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}trickle@trearn.bitnet>} \nl
This is a mechanism for ordering files from the archives of the
\csc{SIMTEL-20} server for those users not connected directly to the
Internet.
\element{\sl{}Access by:\/} Mail, \csc{RSCS FTP}, Interactive message
\element{\sl{}Commands:\/} {\tt{}/HELP} sends you a help file
\element~ {\tt{}/PDDIR}
followed by the name of a directory lists the names of files in that
directory
\element~ {\tt{}/PDGET}
followed by a full directory-and-filename will send you that file.
\element{\sl{}Example:\/} {\tt{}/pdget <msdos.tex>pcwritex.arc (uue}
will order the given file from directory {\tt{}<msdos.tex>} in \csc{UU}encoded
form.
\element~ {\tt{}/pddir <msdos.tex>}
will send the list of all files in the {\tt{}<msdos.tex>} directory.
\element{\sl{}Notes:\/}
The command can be followed by ``{\tt{}(UUE}'' in order to have the file sent
in \csc{UU}encoded form. Further \csc{TRICKLE} servers are at \csc{EARN} nodes
{\tt{}awiwuw11},
{\tt{}banufs11},
{\tt{}imipoli},
{\tt{}dtuzdv1},
{\tt{}db0fub011} and
{\tt{}eb0ub011}.
They are all peered, so you should use the one which is logically
nearest to your node (measured in network hops).
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}jonradel@icecream.princeton.edu>} \nl
Jon Radel offers a mail-order service for those users with no access to
networking.
\element{\sl{}Access by:\/} Post
\element{\sl{}Commands:\/} I quote from his message in the \TeX{}hax
bulletin 1989 No.~13:
\noindent {\tt{}Date: Tue, 7 Feb 89 03:41:23 EST }\nl
{\tt{}From: jonradel@icecream.Princeton.EDU (Jon Radel) }\nl
{\tt{}Subject: For those who don't have access to TeX for PCs on the net...}\nl
{\tt{}Keywords: general, TeX, PCs}
\noindent Time to introduce myself again.
As a service for people who do not have decent access to \TeX{} on
\csc{PC}s material on the net, I distribute much of that material on floppies
for a handling charge. That includes the 75 font, 5 mag step collection
for a couple of the more popular printers, two versions of \TeX{}, and a
variety of smaller items.
\noindent For various reasons, I do all my dealings on this matter by ``snail''
mail, so you have to send me a self-addressed envelope to get the list
of material that I have. 45 cents postage inside the \csc{USA}, 4
International Reply Coupons or \csc{US}\$1.60 for airmail elsewhere, half that
for surface (and Canada/Mexico, where surface is air as far as the \csc{USPS}
is concerned).
\element{\sl{}Example:\/} Jon Radel,
\csc{PO} Box 2276,
Reston,
\csc{VA} 22090,
\csc{USA}
\element{\sl{}Notes:\/} The \TeX{} community's thanks are due to Jon
for his provision of this service.
\bigskip
\noindent $\bullet$$\bullet$ <{\tt{}listings.tex@bytecosy.tower.bix.us>} \nl
is the shortly-to-be-started \TeX{} conference listings area of \csc{BYTE}
magazine's \csc{BIX} online conferencing and filestore system
\element{\sl{}Access by:\/}
Interactive login {\it{}via\/} an X.29 (packet-switched) call to [0]310690157800
or using an ordinary modem ({\tt{}8,n,1}) to +1~617~861~9767.
Press the {\sans{}Enter} or {\sans{}Return} key and at the login prompt type
{\tt{}bix}, then when asked for your name, type {\tt{}bix.flatfee}
and you will automatically be taken throught the new-user signup
routine.
\element{\sl{}Commands:\/} {\tt{}join}
followed by the name of the conference. For file downloads this is
called {\tt{}listings}
\element~ {\tt{}area}
followed by the filestore area, for example {\tt{}tex}
\element~ {\tt{}receive}
followed by the name of the file you want. At this point you need to
instruct your workstation to receive a file using the \csc{XMODEM} protocol
(by default---other protocols are available, such as \csc{KERMIT}.
\element~ {\tt{}option receive kermit}
instructs \csc{BIX} to use the \csc{KERMIT} protocol to send you a file.
\element~ {\tt{}quit} leaves the listings area.
\element~ {\tt{}bye} signs you off.
\element{\sl{}Example:\/} {\tt{}join listings }\nl
{\tt{}area tex}\nl
{\tt{}receive dostex.arc}\nl
{\tt{}quit}\nl
{\tt{}bye}
\element{\sl{}Notes:\/}
You can only use \csc{BIX} for downloading files if you are equipped with a
computer running terminal emulation software which includes
file-download protocols such as \csc{KERMIT}, \csc{XMODEM},
\csc{YMODEM} or similar.
\bigskip
\noindent Source code for the \csc{UUDECODE} program is known to reside on
the \csc{SIMTEL-20} server in the following files. They may be ordered
from \csc{TRICKLE} in the manner detailed above.
\noindent {\tt{}<CPM.STARTER-KIT>UUDECODE.PAS}\nl
{\tt{}<MSDOS.STARTER>UUDECODE.BAS}\nl
{\tt{}<MSDOS.STARTER>UUDECODE.EXE}\nl
{\tt{}<MSDOS.STARTER>UUDECODE.C}\nl
{\tt{}<UNIX-C.MAIL>UUENCODE-UUDECODE.TAR-Z}
\bigskip
\noindent Users of commercial mailing and messaging systems will need access
to the academic and research networks in order to use these
servers. This is currently available through an organisation called
\csc{DAS}net. With a subscription to \csc{DAS}net you can send and receive
mail from your local commercial mailbox to and from the academic
and research networks. The format of address depends a little on
your host system, but for an example I quote a mail from their
coordinator:
\noindent {\tt{}From: IN\%"AnnaB@11.DAS.NET"}\nl
{\tt{}To: cbts8001@IRUCCVAX.UCC.IE }\nl
{\tt{}Subj: DASnet}
\noindent Peter,
\noindent How one addresses \csc{BITNET} through the \csc{DAS}net Service
depends on the source system. From GeoMail, it's as follows:
\noindent To use \csc{DAS}net(\csc{R}) to send me electronic mail from GeoMail,
send mail as follows:
\noindent {\tt{}To: GEO4:DASNET }\nl
{\tt{}Subject: user@site.bitnet!the subject}
\noindent One could address to anyone on the Internet in the same way.
\noindent [\csc{DAS}net are on +1 408 559 7434]
\baselineskip=12pt \bye
-----------------------------------------------------------------------
%%% Further information about the TeXhax Digest, the TeX
%%% Users Group, and the latest software versions is available
%%% in every tenth issue of the TeXhax Digest.
%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%%
%%% BITNET: send a one-line mail message to LISTSERV@xxx
%%% SUBSCRIBE TEX-L <your name> % to subscribe
%%% or UNSUBSCRIBE TEX-L
%%%
%%% Internet: send a similar one line mail message to
%%% TeXhax-request@cs.washington.edu
%%% JANET users may choose to use
%%% texhax-request@uk.ac.nsf
%%% All submissions to: TeXhax@cs.washington.edu
%%%
%%% Back issues available for FTPing as:
%%% machine: directory: filename:
%%% JUNE.CS.WASHINGTON.EDU TeXhax/TeXhaxyy.nn
%%% yy = last two digits of current year
%%% nn = issue number
%%%
%%%\bye
%%%
End of TeXhax Digest
**************************
-------