HDTenEightyP/NetNews huggingface dataset:
From: lindner@danzig.micro.umn.edu (Paul Lindner)
Subject: Re: Weather service on gopher:
Keywords: weather gopher downwind
Organization: University of Minnesota, Minneapolis
Date: Fri, 20 Nov 1992 18:21:25 GMT

In <1992Nov17.204601.25657@cs.cornell.edu> raman@cs.cornell.edu (T. V. Raman) writes:



>I am trying to access the weather server with the following in my
>.gopherrc:
>#
>Type=1
>Name=interactive weather service (from u of michigan)
>Path=
>Host=downwind.sprl.umich.edu
>Port=3000


>The gopher client hangs, even though telnet to the same host and port
>works immediately:

>I would like to use gopher instead of regular telnet because I am
>hoping that gopher will retrieve the weather forecast as a document
>similar to what the gopher interface to the geographic server on
>martini does.

>Does anyone have something like this working for the weather server?

Sorry, this won't work.  The service on downwind is interactive,
gopher is basically a query mechanism, it sends the query and it's
done.   

You can put the following on your gopher-server if you're interested
in getting weather info..



Name=National Weather Service Forecasts
Type=1
Port=70
Path=1/Weather
Host=ashpool.micro.umn.edu
--
 | 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: jboeske@namao.uucp (John Boeske)
Newsgroups: comp.infosystems.gopher
Subject: Re: Applying Vulcan Mind-Meld on a Gopher...
Date: 20 Nov 92 18:33:01 GMT
Organization: University Of Alberta, Edmonton Canada

SEB1525@MVS.draper.com (Steve Bacher) writes:

>In article <1992Nov17.154723.27357@macc.wisc.edu>,
>kaufman@macc.wisc.edu (Peter Kaufman) writes:
>>Hence, the Gopher Mindset I would recommend is to create the
>>subdirectory structure, load it with .link files and put all the data
>>files off the root.

>What I've often ended up doing is creating a directory with a .Links
>file, a handful of other files referenced by the .Links file, and
>an etc directory which contains all the real data.  The .Links then
>refers to the files in the etc directory, which (as we all know) is
>ignored by Gopher when building its menu.

>I sometimes include a bin directory with a "makegophermenu" script
>geared toward the unique needs of the kind of data stored in the
>directory in question, which can be run whenever files are added
>or changed to recreate the .Links file.

We've thought about these schemes but have some problem when we index
the files.  Pathnames to the data files show up as very different from
what the user sees when he gets to the file through the menus.  Do other
people see this as a problem?

John Boeske                                  jboeske@namao.ucs.ualberta.ca
From: cooper@UTSPH.SPH.UTH.TMC.EDU
Newsgroups: comp.infosystems.gopher
Subject: Trouble with latest PC gopher client
Date: 19 Nov 1992 00:29:08 GMT
Reply-To: cooper@UTSPH.SPH.UTH.TMC.EDU
Organization: University of Texas School of Public Health

Hi,

	I have downloaded the latest gopher client from boombox.micro.umn.edu
and can make it work fine with out network (PCSA) using the clarkson drivers.

However, when I do a word search on certain wais data bases, I get the
message "I looked and could'nt find anything" (or something like that)
However, when I do a search with the previous version (maybe a couple of 
version back), the search works fine.   I also can do a search from our
VAX gopher client and it works fine.  Has anyone else experienced such 
a problem with the latest gopher (r3) and if so were you able to fix
the problem?

Thanks for you help

Charles Cooper
Univ. of Texas
School of Public Health

cooper@utsph.sph.uth.tmc.edu   (cooper@129.106.2.1)
From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
Newsgroups: comp.infosystems.gopher
Subject: Re: Gopher/WAIS Problem...???
Date: 13 Nov 92 08:05:21 GMT
Reply-To: M.Whidby@mcc.ac.uk
Organization: Manchester Computing Centre

In article <dgaraffa-061192091225@bigmac.mskcc.org>, dgaraffa@bigmac.mskcc.org
(Dave Garaffa) writes:
|> I have a problem and I am not too sure where to post it so here goes....
|> 
|> 
|> Unix    : A/UX v3.0
|> Hardware: Quadra 950 w/16Meg
|> Software: gopher 1.0.3
|>           wais-8-b5
|> 
|> 
|> I am running gopher 1.0.3 (on a side note how is Gopher+ development
|> going?)
|> and wais-8-b5, all *seemed* well.
|> 
|> Here is the problem:  When I do a wais search and I get LESS than 40
|> responces
|>                       everything is A-OKAY!!!
|> 
|>                       But... *IF* I get MORE than 40-50... CORE DUMP
|>                       location of the CORE is my root gopher dir.

There was a post about this the other day I think. There's a call to
Abortoutput in waisgopher.c which only had 1 argument; there should be
2, the first of which should be sockfd. Sorry I can't remember which
line number it is!
-- 
_____________________________________________________________
Mark Whidby, Distributed Systems, Manchester Computing Centre
Newsgroups: comp.infosystems.gopher
From: paulr@fulcrum.oz.au (Paul Rosham)
Subject: Re: Is There an Open Look Xgopher?
Organization: The Fulcrum Consulting Group
Date: Tue, 17 Nov 1992 08:07:37 GMT

rick@sjsumcs.sjsu.edu (Richard Warner) writes:

[quite a bit, deleted for brevity. But the crux of the post is...]

>This is not an abstract ideal.  There are a half-dozen major X based
>UI's, and a lot more minor variants.  Do we have one client for each?
>The *ENTIRE* idea of X was to have one, unifying protocol.  To add
>multiple interfaces somewhat debases this ideal.

Then a style guide should have been specified so that everyone could write
software that acted the same. No-one did. Only one company did a survey of
s/w developers and _major_ end users to find out what they wanted in a GUI
and then spent the time and effort and money to design one, as well as
software to implement it. "Everyone" then bucketed that same company publicly
for "going their own way".

You neither support a standard GUI for X applications, nor desire one, do
you?

>The ideal is *real*,
>not abstract.  Do you want to port and support a dozen different 
>X clients for each application?  That is what will happen *if* this
>stupid, idiotic "we need a separate version for my favorite UI" crap
>continues.

No, no-one wants to support that much software, especially if they have to
use Xt, OLIT or Motif (YUK!).

>The UI in X was meant to be a function if the Window
>Manager.  The basic cults have violated this by making the UI
>dependent on external factors.  Let's stop the wars, tell the idiots
>to put the UI back in the window manager, and get back to the ideal
>of an X world in which every X application is independent of UI and
>Window Manager.

Please try to get your feet back near the ground. Software just don't work
like this. Especially _this_ software!

>(if folks want an Open Look interface, all the
>SHOULD require is that they run an Open Look WM!  Period!).

Nice try, but again, this does not work. What we really needed was a stricly
enforced look and feel inside the toolkits _that matched_ with the ability to
innovate. Unfortunately, some of our friends, the major computer vendors,
decided that it should look and feel "like a PC", so blame them for the GUI
wars, please. They foisted the problem on us.

-PaulR.
[Phew, off the soapbox, and back in the asbestos tent...]
From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
Newsgroups: comp.infosystems.gopher
Subject: Re: building gopher wais search server
Keywords: build gopherd wais index search
Date: 17 Nov 92 09:29:32 GMT
Reply-To: M.Whidby@mcc.ac.uk
Organization: Manchester Computing Centre

In article <1992Nov13.145937.13625@ai.univie.ac.at>, paolo@ai.univie.ac.at
(paolo petta) writes:
|> In article <1992Nov12.202515.18657@news2.cis.umn.edu>
|> lindner@danzig.micro.umn.edu (Paul Lindner) writes:
|> >
|> >Use wais8-b5.  As soon as gopher1.1 comes out you'll want to try out
|> >Don Gilberts boolean wais.
|> >
|> 
|> Does this mean that I should not bother with the iubio-gopher-v1.patch
|> and just patiently wait for a (very?) few days for the next
|> official gopher release containing all the functionality + fixes?

As I understand it, you will still need to apply the patch to the WAIS
stuff.
-- 
_____________________________________________________________
Mark Whidby, Distributed Systems, Manchester Computing Centre
Newsgroups: comp.infosystems.gopher
From: raman@cs.cornell.edu (T. V. Raman)
Subject: Shakespeare: got it again!
Keywords: Gutenberg shakespeare from gopher accessible again!
Organization: Cornell Univ. CS Dept, Ithaca NY 14853
Date: Sun, 15 Nov 1992 19:31:20 GMT




Readers of this group probably remember seeing a couple of postings
from me saying that the Shakespeare link caused the unix gopher client
to hang.

The author of the gopher client Paul Lindner in his reply to me said
he could get to the directory from his site, but I had no success.
Well, I just did a search on the search electronic books  and it
retrieved a document from Shakespeare, and I saw that the path it
listed was /Gutenberg/shake. All the shakespeare links I have seen at
the various gopher sites point to /Ebook/title/shake or something
similar (I am writing this from memory) and this link hangs on the
unix client for some reason.  I created a personal bookmark entry for
shakespeare that looks like:

#
Type=1
Name=complete works of shakespeare
Path=1/Gutenberg/shake
Host=mudhoney.micro.umn.edu
Port=70


and it works just fine.

Just thought I would let the net know so that either the path that
/Ebook/... can be fixed, or sites can change their gopher link to
point to the above directory.

--Raman
-- 
   T. V. Raman <raman@cs.cornell.edu>Tel: (607)255-9202  R 272-3649
                       Office: 4116 Upson Hall,
Department of Computer Science, Cornell University Ithaca NY 14853-6201
                Res: 226 Bryant Avenue Ithaca NY 14850
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: unix gopherd -s and -l don't work togeather
Organization: University of Minnesota, Minneapolis
Date: Tue, 17 Nov 1992 08:22:45 GMT

In <1ea4fuINNo5v@golem.wcc.govt.nz> brockie@golem.wcc.govt.nz (Roger Brockie) writes:

>In article <BxtyKC.B39@uxa.ecn.bgu.edu> xcea@uxa.ecn.bgu.edu (Chad Adams) writes:
>>I am tring to use the following in inetd.conf on SunOS 4.1.2 and it does
>>not work:  (line split up to into 80 column chunks to put in article)
>>
>>gopher stream tcp nowait root /usr/local/etc/gopherd gopherd -I
>>-s/home/uxa/xgopher/public_access -l/home/uxa/xgopher/log/public -uxgopher
>>/home/uxa/xgopher/gopher-public 70
>>
>>It can't access the main menu.  If I take out the -s or the -l it works.
>>We need to use both -s and -l.

>You can only have 5 parameters in inetd.conf.  You have 6 which is why it works
>when you remove one.

>I think you'll find that the last 2 (the directory and port) are not needed
>because they are builtin into the code via the Makefile.  But that maybe
>1.1b1.

>But it is a problem.  Maybe we need an /etc/gopherd.conf file instead ?

hehehe, I'm one step ahead of you :-)

I'm working on the code to do that right now (ahh long recompiles..)
--
 | 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: bill@rsphys.anu.edu.au (Bill Alford)
Newsgroups: comp.infosystems.gopher
Subject: Re: More people would use gopher if ...
Date: 19 Nov 92 00:30:35 GMT
Reply-To: bill@rsphys.anu.edu.au (Bill Alford)
Organization: SCU, RSPhyScE, Australian National University
NNTP-Posting-Host: 150.203.15.145


The dictionary definition of gopher is: any of various American burrowing
rodents (as a ground squirrel) that mostly have cheek pouches. This came from
our local gopher and if you asked people outside of the US what a gopher was
you would probably get a reply of 'I don't know'. I know roughly what a gopher
is but the rest of the world would not know any of the Americanisms associated
with the name, just as the rest of the world is unaquainted with some
Australianisms (like 'back of Bourke'). So please, if you are going to change
the name, make it meaningful for the rest of the world outside the US and
include 'info' or something like that in its name to make it much more
meaningful (like 'Word' in the case of a word processing package). Something
like infosource (if that name is not taken already). You could have a
competition for a name suggestion.
  
===========================================================================
| Bill Alford,                            | Email: bill@rsphys.anu.edu.au |
| School Computer Unit,                   | Tel: 61 6 249 2143            |
| Research School of Physical Sciences    | Fax: 61 6 249 1884            |
|     and Engineering,                    |                               |
| Australian National University,         |                               |
| GPO Box 4,                              | "Life's a chain reaction"     |
| Canberra City, ACT 2601                 |                               |
| Australia                               |                               |
===========================================================================
Newsgroups: comp.infosystems.gopher
From: kirk@cc.uow.edu.au (Kirk)
Subject: Expiring information ???
Organization: University Of Wollongong
Date: Fri, 20 Nov 92 04:53:22 GMT

G'day,
     I am currently involved in setting up a gopher server on campus here at
The University of Wollongong and was wondering if anyone knows of a way of 
setting expiry times on files or links withing gopher. The idea we have is 
that when links or information is added to the gopher server they can be 
given an expiry. When this expiry time is reached the information is removed
and the owner of the files is notified by mail although the notification is 
really only the icing on the cake.

Does anyone know if this is part of or planned for gopher ?  Maybe someone
has written something similar themselves, I would be interested to hear.
Thanks in advance,

Kirk Barrett.
--
Kirk Barrett          	        AARnet: kirk@uow.edu.au            
Consultant Programmer		UUCP: ...!munnari!uow.edu.au!kirk  
Information Technology Services ARPA:  kirk%uow.edu.au@uunet.UU.NET 
University of Wollongong	Phone: +61 42 213121                       
N.S.W.  2500  Australia		Fax :  +61 42 213262                       
--
From the newsgroups description file:
alt.sport.bungee        Like alt.suicide with rubber bands.

-- 
Kirk Barrett          	        AARnet: kirk@uow.edu.au            
Consultant Programmer		UUCP: ...!munnari!uow.edu.au!kirk  
Information Technology Services ARPA:  kirk%uow.edu.au@uunet.UU.NET 
University of Wollongong	Phone: +61 42 213121                       
Newsgroups: comp.infosystems.gopher
From: raman@cs.cornell.edu (T. V. Raman)
Subject: Re: Veronica: an Archie for Gopher
Organization: Cornell Univ. CS Dept, Ithaca NY 14853
Distribution: comp
Date: Thu, 19 Nov 1992 19:30:20 GMT

doelz@comp.bioz.unibas.ch (Reinhard Doelz) writes:


I finally succeeded in connecting, but even a single word search fails
to return after more than an hour, so that server is definitely very
very dead or choking under the load.

>Sorry but I fail to connect to futique.scs.unr.edu for about a full 
>day now. Is the VERONICA site dead ? 

>-- 
>+----------------------------------+-------------------------------------+
>|    Dr. Reinhard Doelz            | RFC     doelz@urz.unibas.ch         |
>|      Biocomputing                | DECNET  20579::48130::doelz         |
>|Biozentrum der Universitaet       | X25     022846211142036::doelz      |
>|   Klingelbergstrasse 70          | FAX     x41 61 261- 6760 or 267- 2078     
>|     CH 4056 Basel                | TEL     x41 61 267- 2076 or 2247    |   
>+------------- bioftp.unibas.ch is the SWISS EMBnet node ----------------+
>               -----------------------------------------
-- 
   T. V. Raman <raman@cs.cornell.edu>Tel: (607)255-9202  R 272-3649
                       Office: 4116 Upson Hall,
Department of Computer Science, Cornell University Ithaca NY 14853-6201
                Res: 226 Bryant Avenue Ithaca NY 14850
Newsgroups: comp.infosystems.gopher
From: jboeske@namao.uucp (John Boeske)
Subject: Re: Waisindex indexing the index.* files
Organization: University Of Alberta, Edmonton Canada
Date: Fri, 20 Nov 1992 16:26:30 GMT

boone@convex.cl.msu.edu (Dennis Boone) writes:

>In article <1992Nov17.064002.9696@news2.cis.umn.edu> lindner@mudhoney.micro.umn.edu (Paul Lindner) writes:
>>Okay, here's whatcha do:
>>
>>Say you have a directory /home/foo, you store your indexes in
>>/home/foo/.index.
>> ...
>>waisindex -r /home/foo/*
>>
>>Most shells don't expand dot files when you give it a asterick to chew
>>on. 

>I recently discovered one of my indices wasn't rebuilding because the *
>expanded to over-many filenames.  You'd think WAIS would be smart enough
>not to index its own files.  Lose lose.

Or here's what else you can do when you're in /home/foo/.index

find /home/foo  -name .\?\* -prune \
  -o -type f -print \
  -o ! -name dev ! -name bin ! -name etc ! -name usr \
  -o - prune \
| waisindex -d $user -stdin

Don't look at anything starting with .
Print all file names to waisindex
Recurse into directories not called dev, bin, etc, or usr
Don't recurse 

John Boeske                            jboeske@namao.ucs.ualberta.ca
From: SEB1525@MVS.draper.com (Steve Bacher)
Newsgroups: comp.infosystems.gopher
Subject: Re: unix gopherd -s and -l don't work togeather
Date: 17 Nov 92 23:04:00 GMT
Organization: Draper Laboratory

In article <1992Nov17.070258.10075@news2.cis.umn.edu>,
lindner@mudhoney.micro.umn.edu (Paul Lindner) writes:

>SunOS is really braindamaged in that it only allows four real
>parameters to an inetd.conf entry.

The braindamage is not merely that this limitation exists.
Limitations are a fact of life in a finite world.  The real
braindamage is Sun's total failure to have documented this
limitation, as if it didn't matter and nobody would care.

I'll shut up now... :-)

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Newsgroups: comp.infosystems.gopher
From: mark@opus.pass.wayne.edu (Mark Murphy)
Subject: MVS Gopher and TCP/IP
Organization: Wayne State Univ.
Date: Fri, 20 Nov 1992 15:37:57 GMT


   I have a question concerning using Gopher on MVS. Does this require a  
particular version of TCP/IP? We have SNS TCP/IP running on MVS, not the IBM  
TCP/IP. Would this make a difference? Any and all information on MVS Gophers  
and the use of TCP/IP with these gophers is welcome. Thanks.

--

Mark Murphy
Wayne State University
mark@opus.pass.wayne.edu   (NeXT)
mmurphy@cms.cc.wayne.edu   (VM/CMS)
From: heycke@sumex-aim.stanford.edu (Torsten Heycke)
Newsgroups: comp.infosystems.gopher
Subject: Save Me from MTan...
Followup-To: comp.infosystems.gopher
Date: 17 Nov 1992 21:05:52 GMT
Organization: Center for Advanced Medical Informatics at Stanford
Distribution: world
NNTP-Posting-Host: ksl-mac-66.stanford.edu

and the Department of Redundancy Dept (e.g., other unfortunate resendings
of messages to gopher-news@boombox.micro.umn.edu). I've been receiving
MTan's message (the same one) every 15-30 minutes. Gosh, M., I feel like I
know ya, but you seem, well, so one-dimensional.

I suspect it has nothing to do with MTan, but the distribution mechanism.
Can anything be done to save us from this inundation. Please help.

Thanks,

Torsten

PS Just in case you missed it, here's the message (no, no, not again...):

------------------------------------------------------------------
Subject: Re: Apple Gopher Server
Date: Tue, 17 Nov 1992 07:26:34 +0200
From: MTan@uci.edu
To: m.connell@ucq.edu.au
CC: gopher-news@boombox.micro.umn.edu


  Here is the info you requested.

     Name=Apple Computer Higher Education gopher server
     Type=1
     Port=70
     Path=
     Host=info.hed.apple.com

  Mary

>Can anyone give me the details of the Gopher server at Apple ?
>
>Thanks.
>
>Merv Connell
>m.connell@ucq.edu.au
------------------------------------------------------------------------


"A horse may walk to water, but a pencil must be led."
Newsgroups: comp.infosystems.gopher
From: mtm@CAMIS.Stanford.EDU (Mike Macgirvin)
Subject: Re: Waisindex a file containing keywords pointing to other files
Keywords: waisindex keywords HyperText
Organization: Stanford University, California, USA
Date: Fri, 20 Nov 1992 19:21:13 GMT

zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby) writes:

>In article <3338@accucx.cc.ruu.nl>, henny@accucx.cc.ruu.nl (Henny Bekker)
>writes:
>|> 
>|> Hello All,
>|> 
>|> 	I like to known if someone has succeeded in waisindex-ing a
>|> (short) file containing lines with keywords pointing to other (the
>|> real big ones) files..
>|> I like to use gopher as a frontend for it..
>|> Imagine:I have a file containing descriptions of titels of documents.
>|> 	I like to index the file with waisindex so that a 'hit' results
>|> 	not in a seacrch to the description but to the original file
>|> 	of the descriptions..
>|> I don't known how to implement this with waisindexing and gopher.. (if
>|> possible at all ??)

>The only thing I can think of is to ensure that the real files have as
>their first line the title of the file and then use the -t first_line
>option when you waisindex them. Forget about the short file. I don't
>know if this will work - best to try indexing a couple of files first
>and see what happens.
>-- 
>_____________________________________________________________
>Mark Whidby, Distributed Systems, Manchester Computing Centre

	I've just done this for our own work, but the patches are as
yet incomplete. The basic approach is to modify the function
"FixTitleandPath" in Waisindex.c so that it reads the entire .cap
entry and will replace the document pointer with the one you supply on
the "Path=" line. The distributed version reads the "Name=" string but
ignores all other lines in the .cap file. I will also have to check
that this function existed in the 1.1b1 distribution as I have also
added in the iubio WAIS stuff which patched this file significantly,
and the function didn't exist in the 1.02 distribution...
	At any rate, I can probably produce a patch in about a week or
so, after I've answered all these questions and seen how it might also
fit into the latest release...

"mike" (Mike Macgirvin)     Mike_Macgirvin@MED.Stanford.EDU
Unix Server Administrator   Center for Advanced Medical Informatics at Stanford
From: tpm@ecs (TP Monks)
Newsgroups: comp.infosystems.gopher
Subject: FAQ : saving bookmarks in xgopher?
Date: 18 Nov 92 16:41:45 GMT

Says it all really - is there a way of saving bookmarks to file
from xgopher so you can have quick access to your most used directories?

Tim


--
-----------------------------------------------------------------------------
Tim Monks                                Vision, Speech and Signal Processing
tpm@ecs.soton.ac.uk                                    Southampton University
Tel: +44 (703) 592774                                   Fax: +44 (703) 592895
Newsgroups: comp.infosystems.gopher