HDTenEightyP/NetNews huggingface dataset:
From: datta@cs.uwp.edu (David Datta)
Subject: WAIS & Ultrix 
Organization: University of Wisconsin - Parkside
X-Newsreader: Tin 1.1 PL5
Distribution: comp
Date: Thu, 3 Sep 1992 01:40:06 GMT

I have grabbed the new Gopher sources and made the links to ir & ui and
tried to make Gopher with WAIS and I get a bunch of redeclaration
errors. I remember a discussion about this but don't remember the
outcome.

(I am using Ultrix 4.2a)
-- 
-Dave datta@cs.uwp.edu: Man made machines make music for the man.  Now
machines make music while the man makes plans. A second generation, a
generation lost. While the man prepares for the holocaust.- A Flock of Seagulls
Date: Tue, 15 Sep 92 08:37:01 EDT
From: BDESIMON@uga.cc.uga.edu (Bert)
Subject: Links to Finger Ports
Original-To: Gopher Folks <gopher-news@boombox.micro.umn.edu>
Newsgroups: comp.infosystems.gopher
Distribution: comp

Okay, please indulge me on this list for a minute, but I am dying to know
something.  I see now that I can use unix gopher server (and presumably other
servers) to create a link to a finger port (79) with a path (nasanews, quake,
etc.) and a host (space.mit.edu, geophys.washington.edu) and a type (0).

But how the devil does it work???  There is apparently nothing that has to be
done other than create the correct link.

Call me curious, but I am afraid I am missing something fundamental or
even fundamentally obvious.

 ---------------------------------------
| Albert DeSimone, Jr.                  |
|   BITNET:    bdesimon@uga             |
|   Internet:  bdesimon@uga.cc.uga.edu  |
 ---------------------------------------
Newsgroups: comp.infosystems.gopher
From: daniel@mudhoney.micro.umn.edu (Daniel Torrey)
Subject: Mark Thacker, are you out there?
Organization: University of Minnesota, Minneapolis
Date: Sat, 12 Sep 1992 14:33:18 GMT

Mark Thacker --

I received your mail re: pc gopher source, and tried to respond,
but thacker@cc1.unt.edu (the address in your reply-to field) only
results in bounced mail.  What address should I use?

--

Daniel A. Torrey                           daniel@bauhaus.micro.umn.edu
University of Minnesota                                  (612) 626-8663
CIS/UAP/ETC               In gopherspace, no one can hear you scream...
Newsgroups: comp.infosystems.gopher
From: datta@cs.uwp.edu (David Datta)
Subject: Gopher, Ultrix and netstat
Organization: University of Wisconsin - Parkside
X-Newsreader: Tin 1.1 PL5
Date: Tue, 8 Sep 1992 02:00:26 GMT


I have been running gopherd as a server for quite a while now and
recently I did a netstat and lo and behold, there were over 100
connections on port 70 with a status of FIN_WAIT_2. Is this normal?
-- 
-Dave datta@cs.uwp.edu: Man made machines make music for the man.  Now
machines make music while the man makes plans. A second generation, a
generation lost. While the man prepares for the holocaust.- A Flock of Seagulls
From: phillips@fozzie.nrl.navy.mil (Lee Phillips)
Newsgroups: comp.infosystems.gopher
Subject: Macintosh GopherApp truncates large texts
Date: 14 Sep 1992 07:59:28 -0500
Organization: UTexas Mail-to-News Gateway
Distribution: usa
NNTP-Posting-Host: cs.utexas.edu


What gives here?  This program will receive large binhex files and decode
them, but a large (> 50k?) text file causes it to stop with a message that
the file was too large, after asking me for a storage location on disk after
reaching the ~32k limit.  Why is there a limit on the length of a text file,
other than my disk space?  This severely reduces the utility of this otherwise
fine program!

                                           Lee Phillips
                                           phillips@fozzie.nrl.navy.mil
From: bense@heart3.ucsd.edu (Booker C. Bense)
Newsgroups: comp.infosystems.gopher
Subject: Re: Index of what is on every gopher server....
Summary: BZZZZT- Wrong Answer
Date: 15 Sep 92 04:29:39 GMT
Organization: San Diego Supercomputer Center @ UCSD

In article <BEAUDOIN.92Sep11133506@felix.ireq-robot.hydro.qc.ca> beaudoin@ireq-robot.hydro.qc.ca (Martin Beaudoin) writes:
>I am looking for an index describing the sort of information available
>on every gopher server... There is a lot of gopher servers out there,
>so I would like to narrow my search to the servers specialized in
>the specific topics I am interested in.
>
>Maybe that information is already available via gopher... If so, on
>which server???
>


- Some very dedicated gopherMeisters have attempted to do this, I've
tried in my own little way to organize ftp sites into "Categories".
However, ``catagorizing'' is ( at least ) an O(n^2) process while
generating information is an O(n) process, so the amount of gopher
info available is always going to be much larger than any catagorizing
system can handle. This is something we all have to work on, the great
thing about gopher is that you can remember where you've been and
share this with other people ( bookmarks ). Currently, only
gopherMeisters can do this, however I'm volunteering to put other
people's bookmark files on our ( SDSC's ) site. I think this is 
a interesting idea and if it recieves enough interest I could even
build a mail filter to do it automagically, ( one like this already
exists at UNC, but for single items only. )

So, mail your bookmark files to benseb@sdsc.edu and I'll put them
in our gopher. BWT, we have two gophers currently

darth.sdsc.edu 70      ( The standard gopher thing )
darth.sdsc.edu 800     ( Experimental gopher2ftp gateway code Talks
			VMS as well as less ``unixy'' ftp servers )

- Booker C. Bense               "News, News, It's long, It's ASCII?,  
prefered: benseb@grumpy.sdsc.edu   It's Wood. News, News, It's better
NeXT Mail: benseb@next.sdsc.edu      than bad, It's Good!"  Ren&Stimpy
Date: Fri, 11 Sep 92 16:35:03 CDT
From: michele@boombox.micro.umn.edu ("Michele LaVallee Hu" )
Original-To: gopher-news@boombox.micro.umn.edu
Subject: Novell's ODI and PC Gopher client software
Newsgroups: comp.infosystems.gopher
Distribution: comp

The PC Gopher client software is written to work with a packet driver such as 
the Clarkson/Crynwr packet drivers.  These packet drivers make it possible for 
your ethernet board to easily handle more than one kind of packet.  Novell has 
come up with another way to do the same thing.  It is called ODI (Open Data-Link
Interface).  

However, Novell's ODI software and the Clarkson/Crynwr packet drivers will not 
co-exist and the PC Gopher client software doesn't work with just Novell's ODI 
software.

A solution is to use Novell's ODI software along with ODIPKT, written by Dan 
Lanciani.  ODIPKT.ZIP is available via anonymous ftp at 

boombox.micro.umn.edu:pub/netware


     

Michele LaVallee Hu                          University of Minnesota
michele@boombox.micro.umn.edu      Computer and Information Services            
(612) 625-1300                                     190 Shepherd Labs
Date: Fri, 4 Sep 92 16:51:39 EST
From: cooper@utopia.cc.nd.edu
Original-To: gopher-news@boombox.micro.umn.edu
Subject: campaign '92
Newsgroups: comp.infosystems.gopher
Distribution: comp

Look into the following link:

Name=Campaign '92 documents
Type=1
Port=+
Path=ftp:nptn.org@/pub/campaign.92/
Host=+

the org is the National Public Telecomputing Network.  They are  
putting up etexts of the 92 presidential campaign so we can get away  
from the soundbyte/factoid thing.  Way cool.

The Government department here is pretty excited.

Happy labor day (U.S.),

Joel
---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joel P. Cooper                         Phone: 219-239-7221
Asst. Director, Networking Services    Fax:   219-239-8201
Office of University Computing         Email: cooper@utopia.cc.nd.edu
University of Notre Dame
Notre Dame, IN  46556

    "Gentlemen!  You can't fight in here!  This is the War Room!"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: comp.infosystems.gopher
From: blake@milton.u.washington.edu (Blake Hannaford)
Subject: Re: Basic Question
Keywords: gopher 
Organization: University of Washington
Date: Wed, 9 Sep 1992 06:14:31 GMT

Sorry about my dumb question (prev. post).  I found that 
curses gopher seems to be more comphrensive than xgopher 
at this point.

BH
Date: Thu, 10 Sep 92 16:18:40 EDT
From: BDESIMON@uga.cc.uga.edu (Bert)
Subject: T Type and PCG2 1.05
Original-To: Gopher Folks <gopher-news@boombox.micro.umn.edu>
Newsgroups: comp.infosystems.gopher
Distribution: comp

This is really for the Gopher Development team, but I thought others
might be interested.

Type T for tn3270 sessions does not seem to be supported on the PC client.
Where there sould be an item, there is nothing.  Is this type gonna be
supported soon?

Thanks for the time ... usual kudos to the Gopher Development Team for
their efforts.

 ---------------------------------------
| Albert DeSimone, Jr.                  |
|   BITNET:    bdesimon@uga             |
|   Internet:  bdesimon@uga.cc.uga.edu  |
 ---------------------------------------
Newsgroups: comp.infosystems.gopher
From: scott@sklib.usask.ca
Subject: Gopher in Chile
Organization: University of Saskatchewan
Date: Thu, 10 Sep 1992 02:37:25 GMT

                Pontificia Universidad Catolica de Chile

TELNET TOLTEN.PUC.CL or 146.155.1.16
login: gopher

            Servicio de Informacion de Internet-CHILE (Gopher v1.02)

1.  Acerca de Gopher Chile.
2.  Coneccion a servidor de gopher USACH/
3.  SECICO On-Line (Agosto-1992)/
4.  Hytelnet (ayuda) (login: hytelnet) TEL
5.  Coneccion a servidor de gopher internacional/
6.  Informaciones varias Universidad Catolica/
7.  Informaciones varias Universidad Catolica de Valparaiso/
8.  Informaciones varias Universidad de Santiago de Chile/
9.  Servicios Internacionales Varios/
10. Servicios Nacionales Varios/
11. Servidores de FTP anonimo/
Date: Tue, 8 Sep 92 12:44:11 -0700
From: tsai@teetot.acusd.edu (Allen Tsai)
Original-To: gopher-news@boombox.micro.umn.edu
Subject: Novell Lan WorkPlace & Gopher
Newsgroups: comp.infosystems.gopher
Distribution: comp


Our PCs are currently running NOVELL 3.11 using Intel's EtherExpress 16 NICs.
And they have Novell's Lan WorkPlace TCP/IP software as well. Now, we
would like to run Gopher client application, but it requires Clarkson
packet driver, which EXP16ODI driver, came with NIC, does not support for.
On the other hand, both EXP16ODI in the NIC and EXP16 in Gopher package
must coexist to make NOVELL server connection, TCP/IP applcations,
including Telnet, FTP, Gopher, all working harmoniously. But it turned
out in the following scenario: if both drivers loaded, then server
connection failed; if EXP16 loaded, then only Gopher worked and vice versa. 
Any information regarding this is HIGHLY appreciated. Please direct
information to me. I will summerize and post it later. 
	Allen Tsai
	tsai@usdcsv.acusd.edu
	University of San Diego
Newsgroups: comp.infosystems.gopher
From: tiktin@idiotix.cs.uoregon.edu (David Mark Tiktin)
Subject: problems with check_access in g2webster and g2whois
Reply-To: tiktin@cs.uoregon.edu
Organization: University of Oregon
Distribution: compinfosystems.gopher
Date: Wed, 9 Sep 1992 21:31:09 GMT


I've installed go4gw on a Sequent Symmetry running DYNIX(R) V3.2.0 and Perl
4.033.  When I tried to run the whois and nntp gateways, the gopher clients
just hung.  Using telnet to invoke the gateways I got:

Escape character is '^]'.
nntp
x outside of string at /net/gopher/.go4gw/g2nntp line 282, <CONF> line 7.
Connection closed by foreign host.

The problem is in the check_access subroutine:

sub check_access {
   local($group)=@_;

   return 1 if (-t STDIN);
   $sockaddr = 'S n a4 x8';
   $mysockaddr = getpeername(STDIN);
   ($ramily,$rport,$raddr) = unpack($sockaddr,$mysockaddr);  <-- dies here
   ...

I'm new to perl, but after consulting the manual, it seemed to me that the x8
part of the template for unpack was causing the problem.  So I replaced

   $sockaddr = 'S n a4 x8';

 with

   $sockaddr = 'S n a4';

That fixed it, but I don't know perl well enough to know whether it's working
by chance or because it's right.  Is it right?  Is there a better fix?

Thanks in advance,

Dave Tiktin
tiktin@cs.uoregon.edu
Date: Tue, 15 Sep 92 16:35:56 -0700
From: foster@cs.unr.edu (Steve Foster)
X-Mailer: Mail User's Shell (7.1-unr.1 5/02/90)
Original-To: gopher-news@boombox.micro.umn.edu
Subject: New location UNCED docs
Newsgroups: comp.infosystems.gopher
Distribution: comp

The UNCED docs have been moved to:

Name=UNCED Documents
Type=1
Port=70
Path=1/Selected/Social/UNCED
Host=hunter.cs.unr.edu

Apologies to those who might have been inconvenienced by the
dislocation....

Steve Foster
Original-To: gopher-news@boombox.micro.umn.edu
From: TJW@buc.edu.au ("Tim wise" )
Date: 14 Sep 92 16:13:45  EST
Subject: GIF files and Macintosh gopher Clients
X-Mailer: Pegasus Mail v2.3 (R1).
Newsgroups: comp.infosystems.gopher
Distribution: comp

    I've had a few people using gopher clients (Hyper Gopher,Sextant,etc.) on
the MAC and whenever they click on a remote .GIF file all they get is a window
full of gibberish.
I assume they are just getting and ASCII representation of the file? Does the
file have to be converted from ASCII to binary (surely its' BIN already?), or
is there a binary switch that must be set in the gopher client? I suspect
that maybe you can only see that the file is there, then you must FTP it back
and load it into a .GIf viewer.
    If this is the case does anyone know a MAC gopher client that allows you
to retrieve and view .GIF in one easy step?<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
=> Tim Wise
=> SYSOP BFS1(Novell)
=> Division Of Business and Information Management
=> BALLARAT UNIVERSITY COLLEGE
=> MT HELEN
=> Ballarat 3350
=> Victoria
=> Australia
=> Ph:  053 339428
=> Fax: 053 339405
=> E-Mail: tjw@bfs1.buc.edu.au
       or  tjw@nova.buc.edu.au
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
From: lecom@slhp1.epfl.ch (Claude Lecommandeur)
Newsgroups: comp.infosystems.gopher
Subject: xgopher unofficial patches
Date: 14 Sep 92 13:54:53 GMT
Organization: Ecole Polytechnique Federale de Lausanne


    I just put on boombox.micro.umn.edu:/pub/gopher/incoming the files :
xgopher.unofficial.patch and xgopher.unofficial.patch.README.

$ cat xgopher.unofficial.patch.README



    This is a patch to xgopher that implement 2 things :

    1 - I generalized the sound code to understand *any* data type that
can be 'played' with a unix command. i.e. when you want to play sound
you have to do a 'play' or 'cat > /dev/audio' or whatever, when you want
to see a gif file you have to call xv or xloadimage, etc...

    You have a set of new resources to do this :

   extendedTypes : the list of such types (any name that can be a resource name is OK).

   and for each type :

	selector:        (no defaults) : The type of the data.
	prefix:          (no defaults) : The prefix to display.
	command:         (no defaults) : The command to execute.
	needTmpFile:     (True)        : Does the command need a temporary file,
                                         if False, the command is supposed to accept
                                         the data on its standard input.
	onlyOneAtATime:  (False)       : True, if only one of this command can run at a time.
	wait:            (False)       : Does xgopher waits the termination of the command
                                         to continue.

Example :

Xgopher.extendedTypes:                  Images Sound

Xgopher.Images.selector:                I
Xgopher.Images.prefix:                  <Pic>
Xgopher.Images.command:                 xv

Xgopher.Sound.selector:                 s
Xgopher.Sound.prefix:                   <snd>
Xgopher.Sound.command:                  cat > /dev/audio
Xgopher.Sound.needTmpFile:              False
Xgopher.Sound.onlyOneAtATime:           True


    In addition, the command can contain a '$' which means where to place
the tmp file in the command, for example :

Xgopher.Sound.needTmpFile:              True
Xgopher.Sound.command:                  cat $ > /dev/audio

    As long as the sound feature is a special case of this, i suppressed the 
sound code and the above resources are set.


    2 - An info button has been added, which toggle the mapping of an info
window. This window give informations on which servers you are querying, on
which port and which path.

  Have fun.


-- 


                    Claude Lecommandeur
                    Service Informatique Central
                    Ecole Polytechnique Federale de Lausanne
                    1015 LAUSANNE (SWITZERLAND)
                    E-Mail : lecom@sic.epfl.ch
                    Tel : (41 21) 693-22-97
Newsgroups: comp.infosystems.gopher
Subject: Hah!  Finally a good setup!
From: gnat@kauri.vuw.ac.nz (Nathan Torkington)
Date: Sun, 6 Sep 1992 06:25:37 GMT
Distribution: comp
Organization: Contract to CSC, Victoria Uni, Wellington, New Zealand

I've finally worked out a good way to setup the gopher, to make the
the structure traversable by humans *and* gopher - as well as making
the ultimately displayed menus logically ordered.

The big problem is that the gopher server lists the filenames as
entries (which is ugly - filenames which are easy to understand
probably aren't easy to type), unless you make a .cap directory (which
is ugly - I want everything in this menu to be in this directory).  I
first tried to get around it by giving all my files names beginning
with .s - gopher doesn't list those.

The bummer is, though, that it *does* search files beginning with a
dot, looking for links.  When I had lots of text files, it would take
*ages* to search them.  I got around this, by have two parallel
structures in the gopher data directory.  One was solely for links,
and the other was solely for data.  I used the top-level directory
"etc" (which isn't displayed by gopher) for the data files, and made
all my directories begin with .s.

In each directory was a .links file, that defined the menu for that
level.  It has links to the . directories and to the files in etc/ as
well as giving each entry a Numb= ordering in the final menu.  Voila!
A working system.

As an example, suppose the data directory was ~/gopher-data - the
directory structure would look something like this:

	~/gopher-data/.links
	~/gopher-data/.local/
	~/gopher-data/.local/.links
	~/gopher-data/.gophers/
	~/gopher-data/.gophers/.links
	~/gopher-data/etc/about.Z
	~/gopher-data/etc/local/
	~/gopher-data/etc/local/about.Z
	~/gopher-data/etc/local/ ... whatever text you have locally
	~/gopher-data/etc/gophers/about.Z
	~/gopher-data/etc/gophers/ ... whatever text about other gophers

I generally call the "about this directory file" about.Z to make
things simple.

What do you all think?  Has anyone come up with anything better?

Nat
(gnat@kauri.vuw.ac.nz -- Nathan Torkington -- is the electronic text and
 MS-DOS archivist for the Victoria University of Wellington, New Zealand)
Newsgroups: comp.infosystems.gopher,comp.infosystems.wais,alt.wais,alt.gopher
From: edc@dna.bchs.uh.edu
Subject: Looking for: Technical Papers
Organization: University of Houston
Date: Thu, 10 Sep 1992 17:32:02 GMT


Looking for any technical papers on the use of WAIS or Gopher.  (ie:
a paper detailing scientific reasons for setting up a server, and their
uses)  Please mail responses, and a summary will be posted.  Thanks much,

Ed Chen
edc@evolution.bchs.uh.edu
"That's the University of HOUSTON, not HAWAII"

--
..You either kiss the future or the past goodbye...
                          -- Ringo Starr (written by O'Deherty / Velez)

                                
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: Gopher1.03 and Ultrix
Organization: University of Minnesota, Minneapolis
Date: Fri, 4 Sep 1992 21:58:21 GMT

In <1992Sep4.152018.1754@welchgate.welch.jhu.edu> danj@welchgate.welch.jhu.edu (Dan Jacobson x-8453) writes:

>I`m trying to compile the new Gopher server on a DEC station (5000)
>running under Ultrix 4.2A.  Wais-8-b5 compiled fine and works as normal.
>The gopher client compiles and runs just fine BUT the compiler barfs on
>the server code and gives me the following message:

>(...)

Erg, grumble, grumble...  I had this fixed, but my ultrix system
wasn't NFS mounted so I forgot to put the patch back into 1.03
Grrrrr... 

Okay, here it is:

*** waisgopher.c~       Mon Aug 31 15:57:19 1992
--- waisgopher.c        Fri Sep  4 16:56:09 1992
***************
*** 21,27 ****
  #include <docid.h>
  
  #define MAIN
! 
  #include "wais.h"
  
  #define WAISSEARCH_DATE "Fri Sep 13 1991"
--- 21,27 ----
  #include <docid.h>
  
  #define MAIN
! #define _sockets_h
  #include "wais.h"
  
  #define WAISSEARCH_DATE "Fri Sep 13 1991"
--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | Gophermaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
From: emv@msen.com (Edward Vielmetti)
Newsgroups: comp.infosystems.gopher
Subject: Re: Links to Finger Ports
Date: 15 Sep 1992 10:52:20 -0400
Organization: Msen, Inc. -- Ann Arbor, Michigan
NNTP-Posting-Host: nigel.msen.com
X-Newsreader: Tin 1.1 PL3

BDESIMON@uga.cc.uga.edu (Bert) writes:
: Okay, please indulge me on this list for a minute, but I am dying to know
: something.  I see now that I can use unix gopher server (and presumably other
: servers) to create a link to a finger port (79) with a path (nasanews, quake,
: etc.) and a host (space.mit.edu, geophys.washington.edu) and a type (0).

The gopher protocol, at the level that you're sending things over the
wire, is identical to the finger protocol.  I think it's also close enough
to quote-of-the-day and to chargen (and a few other tcp based simple
streaming protocols) that you could glue in links to those servers if you
cared.

--Ed

Newsgroups: comp.infosystems.gopher
From: JONESD@kcgl1.eng.ohio-state.edu (David Jones)
Subject: Improved VMS gopher client for UCX TCP/IP
Organization: The Ohio State University
Date: Thu, 10 Sep 1992 04:09:16 GMT

I fixed some problems I had with the v0.6 VMS client program and placed the
the VMSSHARE file, GOPHER_CLIENT.SHARE in the anonymous directory of host
job.acs.ohio-state.edu.

The original code I got from boombox.micro.umn.edu doesn't work with UCX 2.0.
A call to setsockopt() in gopher.c was messed up and the new UCX hoses itself
rather than gracefully ignoring it.

In addition to that fix, the client includes the following modifications:

    The telnet command was changed to UCX format (i.e. "telnet host port"
    instead of "TELNET/PORT=port host").  This should be #ifdef'ed but I
    was too lazy.

    Screen management now adjusts itself to the screen dimensions rather than
    assuming 24x80 (I frequently use 48 line DECterm windows).

    The code was changed to behave in a more cannonical VMS fashion when
    control-Z is entered in response to the prompts (i.e. exit).

    Fixed showfile()'s failure to close the connection.  The dead connections,
    1 for every text object retrieved, tie up resources until the program exits.

    The readline() and readfield() routines were optimized. Character-at-a-time
    I/O is horribly inefficient with UCX socket routines (2K QIOs/sec when
    receiving text).

Before you compile the thing, don't forget to edit conf.h to make DEFAULT_HOST
point to your local server.


David L. Jones               |      Phone:    (614) 292-6929
Ohio State Unviversity       |      Internet:
1971 Neil Ave. Rm. 406       |               jonesd@kcgl1.eng.ohio-state.edu
Columbus, OH 43210           |               jones-d@eng.ohio-state.edu

Disclaimer: A repudiation of a claim.
Newsgroups: comp.infosystems.gopher