[comp.protocols.appletalk] Hints on getting CAP by uucp

roy@phri.UUCP (Roy Smith) (01/09/88)

	For the last 6 or so months phri has had available, via "anonymous
uucp", the Columbia CAP distribution.  Periodically I get mail from people
complaining that they can't get the files.  If you have sent me such mail and
think you are being ignored, fear not.  Using the instructions outlined below,
you can initiate a uucp login on phri, but since you are not in our L.sys
file, if you send me mail through that connection, it appears to come from a
host we don't talk to and I have no way to reply.  If you need to mail me, see
the addresses in my signature.  This note is to clear up what seem to be the
most common mistakes people make (judging from our uucp logs).

	To get the CAP files you should set up a temporary uucp connection
to us by putting one of the following in your L.sys file.  Note: that the
phone number is the start of a multi-line rotary; if 890 is busy it could
be that the rotary is wedged (a depressingly common occurance).  You could
try manually hunting up to 894.

phri Wk2300-0700,Sa,Su ACU 2400 2125780890 ogin: Uanon word: ArchServ
phri Wk2300-0700,Sa,Su ACU 1200 2125780890 "" \r ogin: Uanon word: ArchServ

	The CAP files are in /usr/spool/uucppublic.  It was my impression that
if you did "uucp phri!~uucp/CapFile localfile", the "~uucp" would be expanded
on this side to /usr/spool/uucppublic.  From the number of log entries which
show people trying to get stuff from /usr/lib/uucp (the normal Sys5 uucp home
directory?), I'd have to guess that, at least in some cases, the "~uucp" is
getting expanded on your side instead of mine.  The way around that is to
spell out the full path.  CapFile can be one of:

total 2401
-rw-r--r--  1 root       242012 Jan  8 21:30 at-kip.shar
-rw-r--r--  1 root       110101 Oct 30 17:01 at-kip.shar.Z
-rw-r--r--  1 root        11211 Jan  8 21:31 bugs.01-05
-rw-r--r--  1 root         6299 Jan  8 21:32 bugs.01-05.Z
-rw-r--r--  1 root         4709 Jan  8 21:31 bugs.06-09
-rw-r--r--  1 root         2836 Jan  8 21:32 bugs.06-09.Z
-rw-r--r--  1 root        12690 Jan  8 21:31 bugs.10-11
-rw-r--r--  1 root         6399 Jan  8 21:32 bugs.10-11.Z
-rw-r--r--  1 root         3764 Jan  8 21:31 bugs.12
-rw-r--r--  1 root         2191 Jan  8 21:32 bugs.12.Z
-rw-r--r--  1 root         2743 Jan  8 21:31 bugs.13
-rw-r--r--  1 root         1806 Jan  8 21:32 bugs.13.Z
-rw-r--r--  1 root       813636 Aug 31 11:13 cap4
-rw-r--r--  1 root       340063 Aug 31 11:24 cap4.Z
-rw-r--r--  1 root        41110 Aug 31 11:14 cap4.patch5
-rw-r--r--  1 root        20049 Aug 31 11:21 cap4.patch5.Z
-rw-r--r--  1 root       149580 Aug 31 11:14 cap4.patch6
-rw-r--r--  1 root        67937 Aug 31 11:21 cap4.patch6.Z
-rw-r--r--  1 root       352315 Aug 31 11:14 cap4.patch7
-rw-r--r--  1 root       149883 Aug 31 11:22 cap4.patch7.Z
-rw-r--r--  1 root        55434 Aug 31 12:52 compress.shar

	Please don't attempt anything other than uucp'ing the above files.
I'm pretty sure uucp won't allow you access to any other directory (or
execution of anything other than rnews and rmail; neither of which should you
do via Uanon), but I see no reason to turn this into an experiment in uucp
security.  I've seen occasional minor abuses.  If I see too many of them, I'll
cancel this service.  I peruse the logs on occassion.

	The ".Z" files are compressed versions of their corresponding un-.Z
brethren, made with compress version 4.0, with 16 codes.  If you can handle
those, you are strongly urged to do so and save on phone charges.  If you
don't have compress, you can snarf and compile compress.shar first.

	At-kip is the kinetics gateway code from Stanford.  Cap4 is the basic
distribution.  You will also want cap4.patch5 and cap4.patch6 (and, if you
want to run aufs, cap4.patch7).  The "bugs.*" files are collected bug fixes,
taken from the net as I saw them.

	Finally, please note that we are distributing CAP in this way only
because we use it here, think it is wonderful, and thought it might be a nice
service to provide to the uucp community (who can't get CAP via the usual ftp
method direct from Columbia).  We cannot provide any support or advice for
what to do with the files once you get them (in fact, given my comparatively
limited understanding of networking and Macintoshes in general, and AppleTalk
in particular, you wouldn't want any advice I could give anyway).
-- 
Roy Smith, {allegra,cmcl2,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016