HDTenEightyP/NetNews huggingface dataset:
From: nigelm@ohm.york.ac.uk (Nigel Metheringham)
Newsgroups: comp.infosystems.gopher
Subject: Re: Anyway to pass args from user to shell script being exec'ed?
Date: 25 Jan 93 13:12:34 GMT
Organization: Electronics Department, University of York, UK

In <1jp7feINNhj6@zippy.telcom.arizona.edu> (Tim Conery) writes:
>Gopher can pass arguments into shell scripts one of two ways that I know
>about.

>One way is by providing the arguments in the cap file.

>Host=+
>Port=+
>Type=0
>Path=exec:arguments to pass:script_name
>Name=Whatever

>The second way is to use type 7 to query the user for the arguments.  This
>works
>fine, BUT The shell script should write out standard gopher directory
>protocol.

You also need to modify your gopherd to accept more arguments in the
search string field (by default 1.1/1.11 doesn't).  However this fix
is trivial to put in - here's one I did, but it may need work when
gopher+ turns up (no checking for additional fields after the
arguments).

	Nigel.

Index: gopherd/gopherd.c
--- gopher1.11b/gopherd/gopherd.c	Mon Jan 11 19:07:42 1993
+++ gopher1.11b_x/gopherd/gopherd.c	Tue Jan 19 17:37:47 1993
@@ -659,6 +659,10 @@
      int length;		/* Length of the command line */
      char logline[MAXLINE];
      char *selstr;
+#ifdef VARIABLE_EXEC
+     char * more_args;
+     char arg_list[MAXLINE];
+#endif
 
      /*** Reopen the log file ***/
 
@@ -950,8 +954,20 @@
 	       *command = '\0';
 	       command++;
 	       
+#ifdef VARIABLE_EXEC
+	       more_args = strchr(command, '\t');
+	       if (more_args == NULL)
+		   EXECargs = args;
+	       else {
+		   *more_args++ = '\0';
+		   strcpy(arg_list, args);
+		   strcat(arg_list, " ");
+		   strcat(arg_list, more_args);
+		   EXECargs = arg_list;
+	       }
+#else
 	       EXECargs = args;
-
+#endif
 	       printfile(sockfd, command, 0, -1);
 	  }
 	  break;
-- 
#   Nigel Metheringham  -- (NeXT) EMail: nigelm@ohm.york.ac.uk    #
#   System Administrator, Electronics Dept, University of York    #
#   York YO1 5DD. Phone: +44 904 432374, Fax: +44 904 432335      #
Newsgroups: comp.infosystems.gopher
From: schemers@leland.Stanford.EDU (Roland Schemers)
Subject: Re: Gopher *client* over inetd
Organization: Distributed Computing Group, Stanford University
Date: Thu, 28 Jan 93 00:04:07 GMT

In article <1993Jan27.062306.1361@rat.csc.calpoly.edu> guy@library.calpoly.edu (Guy Martin) writes:
>over inetd?  My problem is that, althougth it runs, of course all input is
>in raw mode, so arrow keys are useless, and since the client uses curses,
>things come out in strange places.  I have tried writing several different
>C programs to allocate pty's and such, but have had no success at all...

What you need to do is grab source to telnetd and change the part where
it execs login to exec your gopher client (with the secure option, of
course). We do that here and it works great. I also hacked it so it
would reject off campus telnets.

Roland

-- 
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            G16 Redwood Hall (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
From: zlsiimw@info.mcc.ac.uk (Mark Whidby)
Newsgroups: comp.infosystems.gopher
Subject: Re: trouble with searches on PC client
Date: 25 Jan 93 09:32:26 GMT
Reply-To: M.Whidby@mcc.ac.uk
Distribution: comp
Organization: Manchester Computing Centre

In article <01GTTDVB7TQQ8ZHLNH@vx.cis.umn.edu>, HOMERK@VTVM1.BITNET (Kimberley
Homer) writes:
|> We have a link to NC State's "Search ERIC archives" on our Gopher.
|> When I do a search using my PC client, I get the message "Sorry!
|> When I looked I didn't find anything!" But when I do the search
|> with the Unix gopherd (1.1) client, it works fine.  Is there some
|> kind of query time-out parameter I should set on the PC client?
|> If so, how do I get to the "Advanced" configuration menu without
|> a mouse?  When I tab over to it, or type Alt-A, nothing happens.
|> Is there a command I can try before I start the Gopher up?

This is the (known) bug with index searches in PC gopher; it exists because
of a limitation in Turbo Pascal. I don't think there can be anything done
about it. On the 'Advanced' config. menu question, I have no problems getting
there without a mouse; I do Alt-C and then Alt-A. This is on version 1.05r3;
what version are you using?
-- 
_____________________________________________________________
Mark Whidby, Distributed Systems, Manchester Computing Centre
From: mn87537@cs.tut.fi (Marko Nordberg)
Newsgroups: comp.infosystems.gopher
Subject: Re: Help With Search Mechanisim
Date: 27 Jan 1993 07:03:40 GMT
Organization: Tampere University of Technology
Distribution: world
NNTP-Posting-Host: kaarne.cs.tut.fi

In article <1993Jan27.004025.27198@muddcs.claremont.edu> you write:
>Hi,
>I am trying to establish a search which will return the results of a grep  
>on a file. Here is my setup:

...

And here is my setup:

In gopher-data directory I have this file

#!/bin/sh
echo=/usr/5bin/echo
$echo "0Hakutulos tekstist{
$1\texec:\"$1\":/bin/puhluet\tcc.tut.fi\t70"
$echo ".\r"

And in .cap subdirectory file with the same name as the previous file

Type=7

And command 'puhluet' comes from the gopher-data/bin directory

#!/bin/sh
cat bin/puhluet.dat | tr '\204\224\231\216\206\217' '{|\[}]' | egrep -i "$1"

as you can see, it also translates characters from IBM-international
character set to corresponding replacement characters in 7-bit ASCII.
and file puhluet.dat is file which i am grepping. It is a telephone
catalog with one item in a line.

Remember that gopher can not see files above it's own data directory.
You must have all necessary items in gopher's own bin. However you can
use links and refer to files in the outside world in your scripts if
you have started gopher with the -c option. This is a security risk,
because if you invent to use general search grep which takes file name
as one parameter then it is very easy to search also your /etc/passwd
file.

-- 
______________________________________________________________________
! Marko Nordberg, Aaltosenkatu 29 A 2, 33500 TRE    ! "Puhun omiani" !
! markon@cc.tut.fi mn87537@cs.tut.fi (931) 557 171  !         -MN-   !
Xref: sparky comp.infosystems.gopher:2080 comp.sys.next.software:3634
From: lebay@mercury.cl.msu.edu (Jim LeBay)
Newsgroups: comp.infosystems.gopher,comp.sys.next.software
Subject: new release of NeXT Gopher client - version1.3.2
Date: 26 Jan 93 02:30:49 GMT
Reply-To: lebay@msu.edu
Organization: Michigan State University
NNTP-Posting-Host: mercury.cl.msu.edu

I have recently uploaded version 1.3.2 of the NeXT Gopher client to several  
archives.  You can retrieve:

/pub/gopher/NeXT/Gopher_1.3.2.tar.Z       from  boombox.micro.umn.edu
/pub/next/submissions/Gopher_1.3.2.tar.Z  from  sonata.cc.purdue.edu
/pub/next/submissions/Gopher_1.3.2.tar.Z  from  cs.orst.edu


New features - version 1.3.2
============================
- support for image type 'I' in addition to type 'g' (GIF)
- support for binary files of types: '4' (BinHex), '5' (DOS archive), 
  '6' (uuencode) and '9' (raw binary).  Files are saved directly to disk.
- fixed a bug with launching Terminal under NeXTStep 3.0

Features added in version 1.3
=============================
* mini-icons are used in the browser to identify Gopher-types
* added support for GIF graphics files (type 'g')
- the Find menu is fully implemented - including a Find Panel
- fixed-width font (Ohlfs) used in the text window
- larger default window size
- Gopher will remember whenever you change its window size
- 'play' (for sounds) is bundled into an .app wrapper
- removed limitation on size of text files
- Alternate-clicking on an item will update its "Item info"
  without retrieving its contents
- a default has been added to allow listing all items in the 
  browser, including unsupported types.  In a Terminal window 
  you must do "dwrite Gopher ShowAllTypes YES".
- "Open..." remembers previous connection information
- double-clicks in the browser are ignored
- window closes when Gopher fails to open a new connection
- better error detection & notification
- fixed bug when closing a window from the menu (Command-w)
- fixed bug when selecting text items following an Index
- other minor improvements and bug fixes

---------
Jim LeBay                            (517) 353-1800
Computer Information Center          lebay@msu.edu
Michigan State University            lebay@mercury.cl.msu.edu (NeXTmail)
*=*=*   I feel better than James Brown!   *=*=*
Date: Tue, 26 Jan 93 16:06:24 -0500
From: carlosp@Rocinante.McRCIM.McGill.EDU (Carlos Perez )
Original-To: gopher-news@boombox.micro.umn.edu
Subject: WAIS Indexes
Newsgroups: comp.infosystems.gopher
Distribution: comp




I tried to set up some indexes as specified in gopherd.8.

%mkdir $gopher_data_dir/FAQ/.emacsindex
%cd $gopher_data_dir/FAQ/.emacsindex
%mv /tmp/emacs-faq  .     
%waissindex -t dash emacs-faq

Then I checked my indexes with waissearch,

%waissearch -d index dired

< This works, I found two hits >

Then I created the file $gopher_data_dir/FAQ/.Links :

Type=7
Name;Emacs Frequently Asked questions
path=7/.emacsindex/index

Then tried gopher/xgopher and went  to the menu entry 

<idx> Emacs Frequently Asked Question

clicked  on it, got the question box, typed "dired" and got a:

	"Server error: Unknown index type"

Tried the same with filetype=mail and with a mail folder and got same
response. I can't see what's wrong. 

My gopherd get's started by inetd 

	../../gopherd -I -c $gopher_data_dir 70

With the exception of the WAIS indexes everything seems fine.

-----------------------------------------------------------------------------
Carlos Perez, Systems Administrator               carlosp@mcrcim.mcgill.edu 
McGill Research Centre For Intelligent Machines       Phone: (514) 398-7155 
3480 University St., McConnell Eng. R-414             
Montreal, H3A 2A7, Quebec, Canada 
-----------------------------------------------------------------------------
Newsgroups: comp.infosystems.gopher
From: Eric Lease Morgan <eric_morgn@ncsu.edu>
Subject: Re: How do I avoid indexing the .cache files
X-Xxmessage-Id: <A7895D04EC01184D@ericmorgan.lib.ncsu.edu>
X-Xxdate: Mon, 25 Jan 93 09:01:56 GMT
Organization: NCSU Libraries
X-Useragent: Nuntius v1.1.1d12
Date: Mon, 25 Jan 1993 13:54:04 GMT

In article <1jpe1tINNpv5@gaia.ucs.orst.edu> Joe Hanus,
hanusj@ava.bcc.orst.edu writes:
>We've waisindexed several directories full of biological data.
>Gopher searches turn up the .cache files as hits since they contain
>the search strings.  How do we avoid producing entries in the index
>for the .caches?

Another approach, besides using fancy WAISINDEX commands, is to

  * separte your biological data into an FTP directory,
  * WAISINDEX the FTP directory, and
  * point your gopher to the FTP directory with .link files.

I find this a much cleaner method because you then provide access
to the information via Gopher, WAIS, and FTP. Additionally, when you
FTP to the directory you don't have to worry the user seeing .cache
files, and your gopher will have descriptive names as opposed to cryptic
ones.

Eric Lease Morgan
Date: Fri, 22 Jan 1993 08:14:36 -0500
From: xbaquero@ecnet.ec (Xavier Baquero)
Original-To: barrie@futique.scs.unr.edu, gopher-news@boombox.micro.umn.edu
Subject: Re:  Beta testers for "local-tree" for veronica
Original-Cc: xbaquero@ecnet.ec
Newsgroups: comp.infosystems.gopher
Distribution: comp


Fred, we will be glad to test your scrip. If this task requires
perl expertise, we won't be able to do it.

Regards

Xavier
Newsgroups: comp.infosystems.gopher
From: pendleton@ossenu.astro.nwu.edu (Jim Pendleton)
Subject: Fix: Gopher 1.11b, VMS, MultiNet
Organization: GRO/OSSE Northwestern U.
Date: Mon, 25 Jan 1993 16:43:37 GMT

Thanks to the guidance of JQ Johnson at the University of Oregon, we have
discovered the trick to making Gopher 1.11B work for us under VMS and
MultiNet.  Perhaps by posting this, we can save others some time.

Under VMS, it may be necessary to modify your include file search path to place
MULTINET_COMMON_ROOT:[MULTINET.INCLUDE] at the beginning.

The default NETDB.H found in SYS$LIBRARY (at least for our system, VMS 5.5-2,
without UCX) has an older, incompatible definition of the "hostent" structure. 
The symptom you will see is a "connection refused by host" error when you try
to connect with any server by name.  (An IP number will connect you, but you'll
be unable to access any items.)

The simplest solution is to redefine sys$library as

	$ DEFINE SYS$LIBRARY MULTINET_COMMON_ROOT:[MULTINET.INCLUDE], -
		SYS$COMMON:[SYSLIB]

before running MAKE or executing the COMPILE.COM's.
-------------------------------------------------------------------------------
Jim Pendleton, SysMgr
GRO/OSSE, Dept. Physics & Astronomy
Northwestern University
j-pendleton@nwu.edu		(708) 491-2748
Date: Mon, 25 Jan 93 11:13:54 EST
From: CCD@BROWNVM.brown.edu (Clare Durst)
Subject: Re: FTP/Gopher
Original-To: gopher-news@boombox.micro.umn.edu
Newsgroups: comp.infosystems.gopher
Distribution: comp

There seem to be more and more FAQ files out there for people to get to.
Has anyone gathered pointers to them into once place so we could put
them into our Brown gopher? I see FAQs for Pagemaker, Canines, etc., etc.
If no one HAS a source of a list of these FAQs, but knows of some of them,
let me know, so at least *I* can get them! Thanks.
Newsgroups: comp.infosystems.gopher,alt.drugs,comp.os.linux,alt.society.civil-liberty
From: jkp@cs.HUT.FI (Jyrki Kuoppala)
Subject: otax.tky.hut.fi gopher - Topics -> English/Topics
Reply-To: jkp@cs.HUT.FI (Jyrki Kuoppala)
Organization: Helsinki University of Technology, Finland
Date: Mon, 25 Jan 1993 17:15:52 GMT

Due to rearrangements in otax.tky.hut.fi gopher server the Topics
directory is now English/Topics.  Please update your link files and
other means of reference to the gopher server.

(I see lots of references to Topics/Linux, Topics/Drugs,
Topics/Civil-liberties)

Similarly, Aihepiireja is now Sekalaista/Aihepiireja.

//Jyrki
From: sharp@mizar.usc.edu (Malcolm Sharp)
Newsgroups: comp.infosystems.gopher
Subject: Re: Wanted: help with PC Gopher II version 1.05r3 vs. merlot.welch.jhu.edu
Date: 21 Jan 1993 10:08:21 -0800
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: mizar.usc.edu

In article <1993Jan21.165943.12179@alw.nih.gov> ado@elsie.nci.nih.gov (Arthur David Olson) writes:
>Using PC Gopher II version 1.05r3, if I connect to merlot.welch.jhu.edu,
>pick the "Search Databases of Welchlab..." selection, pick the
>"Cloning Vectors: plasmids, phage, etc." selection, then search for,
>for example, "rat", I get an apologetic popup window stating that gopher
>is "Sorry!  When I looked I didn't find anything."
...other deleted..

I have this same problem with the PC-Client (Clarkson drivers).  It
occurs with any search of a WAIS (ie, the "sorry ..." msg.).  I too
have confirmed that the search should have come up with something by
doing the identical search with a Unix client.  

DOes this PC client have a bug?

Malcolm Sharp, USC
From: jlukkari@phoenix.oulu.fi (Jyrki Lukkari)
Subject: Re: Chronological order ?
Organization: University of Oulu, Finland
X-Newsreader: TIN [version 1.1 PL6]
Date: Wed, 27 Jan 1993 06:59:16 GMT

I have made a tool, which does just what you want. It's not beautiful
and it wastes computer resources, but it works. Maybe I do later a advanced
version. I hope that some finnish words in the program don't confuse 
anybody.

The script is modified version of some news-script, which made links
to the newest items of Gopher database. The original designer is anonymous.

Sincerely yours  Jyrki


---------------------------------------------------------------------------

#!/bin/sh

# Constructs .cap directories to database files, ordered in cronological
# order from youngest to oldest. 
#

PATH=$PATH:$HOME/bin:$HOME/bin:/usr/local/bin:/usr/bin
export PATH

cd /home1/netservices/gopherot/gopher-data/Humanistinen 
mv .cap .cap.old
find . -name '.cap' -type d -print -exec rm -r {} \; 2> /dev/null
mv .cap.old .cap

gawk '

BEGIN {

	FIND=sprintf("find . -name %c*%c -type f -ctime ", 39, 39)

	ln=1
	for (days=0;days<=160 ;++days) {
		DOFIND = FIND days " -print"
		while (DOFIND | getline) {
		   name=substr($0,3)
		   if (index($0,".cap")) {
			;
		   } else {
			file= $0
			Sname=file
			for (i=length(file);i && substr(file,i,1) != "/";--i);
			dir =substr(file,1,i)
			base=substr(file,i+1)
			system("mkdir " dir ".cap 2> /dev/null")
			capfile = dir ".cap/" base
			printf "Name=%s\nNumb=%d\n", base, ln > capfile
			close (capfile)
			ln++
		    }
		}
		while (DOFIND | getline) {
			;
		}
		close (DOFIND)
	}
	printf "\n\n K{siteltyj{ tiedostoja oli %d\n\n\n", ln
}'

Newsgroups: comp.infosystems.gopher
From: nigelm@ohm.york.ac.uk (Nigel Metheringham)
Newsgroups: comp.infosystems.gopher
Subject: Re: Gopherising FAQ files
Date: 25 Jan 93 18:33:35 GMT
Organization: Electronics Department, University of York, UK

[Following up to my own posts - maybe I should just talk to myself]

In my previous article I wrote about the "gopher-ising" of Usenet
FAQ files.  This would mean that on a gopher server you would see a
list of FAQ directories, and in each directory you would see a set
of entries each being one section (question/answer?) of an FAQ file.

Additionally there would be an index for each FAQ set, and ideally
an index for all the FAQs from the top level.

Basically since FAQ files are free format we have to "persuade"
gopher and WAIS to recognise their subsectioning.  Actually all you
*need* to do is get them into a format that WAIS understands - you
can then put together a set of gopher links (using range addressing)
from the WAIS index.cat file with a simple piece of Perl.

FAQ files are mostly different from one another.  They also do not
fit neatly into any of the known WAIS document types.  It would be
quite easy to co-erce them into a pseudo mail-digest form, but this
doesn't really present the right information (the From: field would
tend to be redundant).

So of the types already handled by WAIS, it would seem best to munge
FAQs into a dash separated format, where each section is separated
by a line of dashes.   The first line following the dashes is the
section identifier.  This leaves the FAQ still readable, but able to
be directly indexed by WAIS.  A script can be written to modify most
FAQ sets into this format quite easily.

the disadvantage is that the FAQs need to be rewritten (ie sepearate
file store).

I have also, despite misplaced confidence, been unable to do
anything similar with NeXT indexing (ie I had to go and build WAIS
instead).  The NeXT indexer seems unable to cope with ranges within
a file even if you replace the commands it uses to analyse a file
(because the rotton thing stats the file before starting anything
else, and it objects if you give it a gopher range type filename).


I would appreciate it if anyone with strong feelings as to the
"right" way to split FAQs would contact me about it before I do too
much work on this technique!

	Nigel.

-- 
#   Nigel Metheringham  -- (NeXT) EMail: nigelm@ohm.york.ac.uk    #
#   System Administrator, Electronics Dept, University of York    #
#   York YO1 5DD. Phone: +44 904 432374, Fax: +44 904 432335      #
Newsgroups: comp.infosystems.gopher
From: pollard@pops.navo.navy.mil (Jesse Pollard)
Subject: Re: Gopher *client* over inetd
Nntp-Posting-Host-[nntpd-3692]: merlin.navo.navy.mil
Reply-To: pollard@pops.navo.navy.mil
Organization: POPS Supercomputer Center
Date: Fri, 29 Jan 1993 01:01:25 GMT

>gopher client to compile on our Sequent S27.  However, we would like to be
>able to run the Gopher *client* (not the server) over inetd, so that when
>users initiate a 'telnet' session from our campus net, they connect directly
>to the Gopher client, which in turn connects to our Gopher server..

This sounds like it would disable telnet...

Assuming this is what is desired then the easiest way to do this would be to
replace the login command with the following:

============= login script - name must be login =============
#!/bin/sh 
#       login - wrapper script to start gopher from an incoming telnet
#               NOTE: login is actually performed for non telnet operations
#------------------------------------------------------------------------

GOPHER=....	# path to the gopher system

if [ "$1" = "-h" ]; then	# must be a telnet...
    cd /tmp			# just for possible core dumps
    # enable terminal for message output
    reset=`stty -g`
    stty 2526:5:1ad:8a3b:3:1c:7f:15:4:0:0:0:11:13:1a:19:12:f:17:16:0
    # start gopher
    exec $GOPHER
fi
exec /bin/login.orig $*
============= end of login =================

The stty modes used must be appropriate for the system running this.

A script such as this is used on SUNOS 4.1.1 to output a warning message
before login.

bytheway.. the "quotes" around the stty -g really are back quotes. The
window I'm editing this in make it look like apostrophe's, so I don't
know exactly what is being sent.


---
Jesse I Pollard, II
Email: pollard@pops.navo.navy.mil

Any opinions expressed are solely my own.

Newsgroups: comp.infosystems.gopher
From: mje@pookie.pass.wayne.edu (Michael J. Edelman)
Subject: Dumb link-to-mac question
Reply-To: mje@pookie.pass.wayne.edu
Organization: Wayne State University
Date: Thu, 21 Jan 1993 21:30:51 GMT

For some reason my links from a unix-based server to mac servers aren't 
working. I've done this in the past, so when I recreated the structure 
of my gopher network I've obviously forgotten something simple.

I need to link to a mac called (for brevity's sake) a.b.c.edu. The server
and files are in Macintosh HD:server. I would have assumed that my link
file should look like this:

Name=Neat remote server machine
Type=1
Port=70
Path=:Macintosh HD:server
Host=a.b.c.edu

I can access this server directly, so I know it works. What dreadfully 
simple mistake am I making? I suspect it's the selector string, but I
don't have any Mac examples around to guide me.

  --mike   mje@pookie.pass.wayne.edu



Newsgroups: comp.infosystems.gopher
From: pjsmith@iastate.edu (Phil J Smith)
Subject: Problem with WAIS
Keywords: gopher, wais
Organization: Iowa State University, Ames IA
Date: Mon, 25 Jan 1993 20:10:35 GMT

I am having some problems getting WAIS searching set up on gopher.  Here is
what I have done:
  cd .index
  waisindex -r ../Classical_Map
  create a link file as follows
   Numb=1
   Type=7
   Name=Search Classical Map
   Host=+
   Port=+
   Path=7/.index/index

When I attempt to do a search I get the error message:
     server error: unknown index type

Does anyone know what's going on?


Thanks,


Phil Smith
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Newsgroups: comp.infosystems.gopher
Subject: Re: vt100 gopher with kermit
Date: 25 Jan 93 23:04:31 GMT
Article-I.D.: news2.C1FMrL.1p4
Organization: University of Minnesota, Minneapolis

In <1993Jan25.192713.25792@pslu1.psl.wisc.edu> hoymand@wissago.wisc.edu (Dirk Herr-Hoyman) writes:

>I'm looking for a vt100 gopher client that has the ability to kermit results  
>back to a local PC.  We are trying to replace an existing BBS with gopher, but  
>need a telecomm downline capabilty.   Ideally, the kermit download would be an  
>option just like saving or mailing results are in the gopher command line  
>client from the standard distribution.

>If someone has such a client, and is willing to let us use it, please let me  
>know.  Thanks.

There are two solutions to this:

1) set up a slip server and use the PC-Gopher across a phone line..
Very nice.

2) Let your users log into a UNIX or VMS box running gopher 1.11 or
higher.  You'll need to have kermit installed on the unix box for this
to work...  (i.e. it's external to the client)

Then the users can press 'D' for download on a document and receive it
using kermit, xmodem, ymodem, zmodem, or text.
--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | Gophermaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /