HDTenEightyP/NetNews huggingface dataset:
From: HELMUT@bonnie.physik.uni-stuttgart.de (Helmut Springer)
Subject: GOPHER-client for VMS with CMU-Tek ?
Organization: Physics Dept, University of Stuttgart, FRG
Date: Thu, 30 Jul 1992 20:01:21 GMT
X-News-Reader: VMS NEWS 1.23

Hi all,

I'm looking for a GOPHER-client running on our VAXen under VMS using the 
tcp/ip-software CMU-Tek.

Anybody heared of something like this ?

Please answer with mail, I'll summerize.

Thanks in advance
        helmut

--
Helmut Springer                    University of Stuttgart, FRG
User HelpDesk Computing Center           CipPool Physics Department
springer@rus.uni-stuttgart.de            springer@physik.uni-stuttgart.de
phone: +49 711 685-4828                  1284::helmut (BelWue)

%SYSTEM-W-MAILONSYS, there is real mail installed on this system
Newsgroups: alt.gopher
From: mark@opus.pass.wayne.edu (Mark Murphy)
Subject: Re: CMS Pipelines?
Organization: Wayne State University, Detroit
Date: Mon, 27 Jul 1992 19:35:39 GMT


In article <1992Jul27.162350.15606@rs6000.cmp.ilstu.edu>  
dbeedle@rs6000.cmp.ilstu.edu (Dave Beedle) writes:
>    Hello.  I'm working on setting up the rice Gopher client on a VM machine.  
> At one point the client says that it needs something called CMS Pipelines.  
> What is this and where is it available?  Thanks!
> -- 
>   Dave Beedle                                    Office of Academic Computing
>                                                     Illinois State University
>   Internet:  dbeedle@rs6000.cmp.ilstu.edu                    136A Julian Hall  
>   "Relax, don't worry!  Have a homebrew!"                  Normal, IL   61761

You need to get VM CMS Pipelines PRPQ. Check with the VM administrator about  
ordering this program. The HESC lists this product as program number 5799-DKF.
--

Mark Murphy
Wayne State University
mark@opus.pass.wayne.edu   (NeXT)
mmurphy@cms.cc.wayne.edu   (VM/CMS)
From: BDESIMON@uga.cc.uga.edu (Bert)
Newsgroups: alt.gopher
Subject: Waisindex -t dash Question
Date: 29 Jul 92 20:05:18 GMT
Distribution: alt
Original-To: Gopher Folks <gopher-news@boombox.micro.umn.edu>

While this question may be more appropriate for a wais list, I am hoping
that some Gopher Folks might have encountered this.

The dash option to -t does something I don't really understand.
While a single document is broken up into its dash-marked components, the
headline is real long ... like the first 100 or so characters.  If I take
the same document and wais it with the para option, the one line after the
blank delimiter line is used as the headline, which is what I want the dash
option to do.

By the way, I am using the wais-8-b5.  Any help or comments would be
appreciated.

Thanks in advance.

 ---------------------------------------
| Albert DeSimone, Jr.                  |
|   BITNET:    bdesimon@uga             |
|   Internet:  bdesimon@uga.cc.uga.edu  |
 ---------------------------------------
Newsgroups: alt.gopher
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: Bug in xgopher client
Organization: Draper Laboratory
Date: Sun, 26 Jul 1992 20:36:00 GMT

Using xgopher 1.1a from a SunOS 4.1.2 host, if I issue an index query
where the query contains one or more asterisks, the file display seems
to pick a random character and highlight it throughout the display.

This is apparently an extension of the normal (correct) behavior of
highlighting the words specified in the search query.  It looks quite
bizarre, though, not to mention making the text difficult to read.

I have also seen the text get lost completely if the search argument
consists only of asterisks.

(Note:  The request is being passed to a keyword-indexed data base
which is not WAIS, so it may have a different syntax for searching.)

 - SEB

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Xref: sparky alt.gopher:1141 comp.org.eff.talk:5087
From: jonabbey@cs.utexas.edu (Jonathan David Abbey)
Newsgroups: alt.gopher,comp.org.eff.talk
Subject: Re: Looking for new root server for SOUND
Followup-To: comp.org.eff.talk
Date: 31 Jul 1992 14:10:07 -0500
Organization: CS Dept, University of Texas at Austin
Distribution: world
NNTP-Posting-Host: ozona.cs.utexas.edu
Keywords: SOUND

In article <ed.712594855@cwis> ed@cwis.unomaha.edu (Ed Stastny) writes:
>As some may have noticed...SOUND is "suspended indefinately" on
>odin.unomaha.edu.  The system administrator has done this in question of
>it's "academic relation".  SOUND is an entertainment and news paper in
>the Omaha area.  
> 
>My brief request is for gopher-administrators on commercial or other
>friendly servers who would be interested in carrying the SOUND News and
>Arts.

Interesting.. I read a good part of the issue you had on the gopher, and
I found it to be very interesting, and very educational.  The commentary
in particular I found to be more engaging than those in our own professionally
published school newspaper, The Daily Texan, which is available on-line from
the University of Texas at Austin Computation Center Gopher.  In addition, it
gave a quite personable representation of your university scene.  SOUND seemed
to me to be one of the best additions to the network that I have seen recently.

If you feel it would help, please feel free to use this letter as evidence
in striving to get disk space (which is the issue, as gopher uses neglible
computer time) for the electronic publishing of SOUND.  I think it has
considerable educational merit.

Trying to find a publisher to take SOUND to the net is an interesting issue,
opening up all kinds of questions of commercial vs. public funding for
distribution, and of establishing a market to provide information distribution
services over the TCP/IP Internet.

While I originally intended to e-mail you, your machine cwis.unomaha.edu
disclaimed any knowledge of an 'ed'.  I've cross-posted this to 
comp.org.eff.talk and set followups there, since this may profitably go
beyond a gopher discussion.

>--
>| Ed Stastny                   | SOUND Now available via: email (from me), |
>| ed@cwis.unomaha.edu          | gopher (cwis.unomaha.edu), and snailmail. |
>|                              |===========================================|
>| SOUND newspaper and netzine  | Death has far too short a fuse...live.

Good luck with a good publication.


-- 
Jonathan Abbey                                    jonabbey@cs.utexas.edu
the university of texas at austin                 Working, not speaking for
computer science/math/psychology                  Applied Research Laboratories
Newsgroups: alt.gopher
From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Subject: Re: index for all of gopherspace
Organization: University of North Texas
Date: Mon, 27 Jul 1992 22:17:55 GMT

hirai@cc.swarthmore.edu (Eiji Hirai) writes:

>Whoa!  What's this?  Is this something that's being organized as a BOF at
>one of the upcoming Usenix conferences or are you just visiting U of
>Minnesota?

Oppppsssss, not sure if the conference was public knowledge or not.  CICNET
is hosting a VERY, VERY small conference on Gopher next month, where at least
2/3rds of the people going to be there are from CICNET sites.  I'll let the
CICNET people comment on the status of the conference.  It is still being
organized to a large extent and is a get your hands dirty thing (not for a
novice Gopher admin).  I highly suspect that the conference is full though.
From: dparter@fyvie.cs.wisc.edu (David W. Parter)
Newsgroups: alt.gopher
Subject: Re: problems with gopherd under inetd
Date: 27 Jul 92 14:15:03 GMT
Organization: U of Wisconsin CS Dept

splite@mtu.edu (Steven Plite) writes:

>I'm having a problem in getting gopherd to use both a log and a security file.
>The relevent line in inetd.conf is:

>gopher  stream  tcp     nowait  root    /local/mining/lib/gopherd       gopherd
>-I -l /local/mining/gopher/.log -s /local/mining/gopher/.secure /local/mining/go
>pher 70

>If I remove either the '-l ...' or the '-s ...' part, it works.  If both are
>present, the server won't grant access.  My gopher directory looks like so:

Inetd has an internal limit of 5 arguments for a daemon. This is not
documented in the sun man pages.  Call a shell script from inetd, 
(I call mine run.gopherd), and in the shell exec gopherd with the
arguments you want.

Perhaps this should be noted somewhere in the unix gopherd documentation...

	--david

--------
david parter				university of wisconsin -- madison
dparter@cs.wisc.edu			      computer sciences department
Newsgroups: alt.gopher
From: peterd@bunyip.com (Peter Deutsch)
Subject: Re: index for all of gopherspace
Organization: Bunyip Information Systems (the archie people)
Distribution: na
Date: Tue, 28 Jul 1992 00:29:02 GMT

In article <1992Jul27.214401.10120@ra.msstate.edu> fwp@CC.MsState.Edu  
(Frank Peters) writes:
> In article <1992Jul27.180509.27470@mercury.unt.edu>  
billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager) says:
> : >You send a query to the meta-database server, and it returns a
> : >list of databases.  You pick one [or several- but we can't do this  
without
> : >overhauling the client] of those, and your client sends a search  
off to
> : >them.
> : >Now, why couldn't we do this with gopher?
> : >
> : This could be done.  Actually, I don't really care to make this a  
"user"
> : feature.  It would involve some major coding and maybe a protocol  
change.
> : Just something us sysadmins use to figure out where we would like  
to place
> : links to.
> 
> I think making it only a gopher administrator's resource sort of
> defeats the purpose.
> 
> I'm a twinkie eating UNIX weanie and could care less about a recipe
> server, for example.  But that doesn't mean that none of my gopher
> users are interested in them...or in a bejillion other things I don't
> care about.  But, of course, if I link in EVERYTHING then they still
> have the problem...it has just been translated into one of traversing
> my gopher tree hierachy (which would, of course, be huge and  
constantly
> out of date).
> 
> I think it would be a very useful thing indeed if Joe Random
> Entomologist had some way to go out and find some bug databases  
without
> requiring me to explicitly support a link to them (bugs give me the
> willies).  Sort of an archie server for gopher/wais/www resources is
> what I have in mind (possibly with hooks to automagically "go there"  
in
> various clients or servers).
> 
> This is the sort of thing that is going to be necessary to get these
> resources out there to the user in the age of information overload.


This echoes the point I was trying to make in one of my previous posts. 
Providing a good Yellow Pages service is a different puppy from 
providing a great tool for easy interactive browsing of collections of 
information. your browsing tool is a great way to access the 
information once it is built up (so a gateway to this service, with
a suitable link at the top of every Gopher hierarchy, seems to make 
sense) but I don't see that it is inherently a "Gopher problem"
at all. It is a general Internet services problem, and we should be
looking at generalized solutions, not ad hoc solutions for deployment
within each new service.

If you do it right, you will solve a problem faced by just
about all of the other services now coming onto the net. Solving it 
has little to do with building better browsing tools and a lot to do 
with  resource discovery, fast indexed searching and automated or 
semi-automated operations for services discovery. I would suggest
people looking for such services take a step back and look around
before proposing YAPC (Yet Another Protocl Change).


				- peterd
Newsgroups: alt.gopher
From: peterd@bunyip.com (Peter Deutsch)
Subject: Re: index for all of gopherspace
Organization: McGill University
Distribution: na
Date: Tue, 28 Jul 1992 00:18:35 GMT

In article <1992Jul27.180509.27470@mercury.unt.edu>  
billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager) writes:
> daniel@nstn.ns.ca (Daniel MacKay) writes:
> 
> >Now, the WAIS thang works because all the people who run WAISs, have  
sent
> >in to the mother of all WAISs, an abstract for each database they've
> >published.  
> >
> Not all.  I've found quite a few WAISs that are NOT in the master  
directory.
> This also is the biggest problem with WAIS.  The directory is flat  
and getting
> too big.

I submit that the problem is that neither WAIS nor Gopher are an
ideal tool with which to build a distributed Yellow Pages service. 
Gopher does interactive browsing well, while WAIS does large text 
indexing well. What you need is a service that does Yellow Pages well, 
which is both accessible from either service (or as an adjuct to it) 
and is able to keep an up-to-date view of the world.

> >Here's the problem I'm trying to solve: I know somewhere in  
gopherspace
> >there's a really good recipe database.  But where is it?
> >
> I agree this is a BIG problem.  I was going to bring it up at the  
Gopher
> Developer's Conference in a couple of weeks and see what could be  
worked
> out.
> 
> >You send a query to the meta-database server, and it returns a
> >list of databases.  You pick one [or several- but we can't do this  
without
> >overhauling the client] of those, and your client sends a search off  
to
> >them.
> >Now, why couldn't we do this with gopher?
>
> This could be done.  Actually, I don't really care to make this a  
"user"
> feature.  It would involve some major coding and maybe a protocol  
change.
> Just something us sysadmins use to figure out where we would like to  
place
> links to.

I don't see Yellow Pages as fitting into the Gopher paradigm as such.
It seems that all you want is to ensure that the index of services is 
available _through_ the Gopher clients. This seems like an ideal case
for another gateway function, similar to the one that was recently
discussed for reaching WHOIS servers (which are after all, the White
Pages equivalent of a services listing).

Even if our particular hammer is not the right tool to hit this one
with (and I obviously think it is) I would caution against trying to
make every tool do everything. In this case, a well-defined and 
publicised gateway seems to make more sense here(BTW, I would make the 
same arguement for White Pages services. I  definitely think the 
"gateway to WHOIS" approach is the way to go, here, rather than trying 
to extend the Gopher protocol to handle user record searches).



				- peterd
Newsgroups: alt.gopher
From: rww@mugwump.cl.msu.edu (Richard W. Wiggins)
Subject: Re: Gopher and Hypertext links
Keywords: hypertext
Organization: Michigan State University
Distribution: alt
Date: Thu, 23 Jul 92 02:07:52 GMT

In article <m0mAmhB-0009iYC@nigel.msen.com> emv@msen.com (Edward Vielmetti)  
writes:
> Brad, there is a hypertext system that knows how to deal with gopher
> systems and that provides in-document links.  See the World Wide Web
> stuff available for FTP from info.cern.ch:/pub/WWW/.  They use SGML
> as their markup scheme and embed link information into the tags.
> 
> --Ed

But of course that's not really the same thing as having hypertext
built into Gopher to begin with, eh?

I'm of two minds about Hypertext.  As Brad says, with careful organization
you can mitigate the temptation to put in multiple links, at least to
some extent.  The nice thing about Gopher right now is that is a 
simple metaphor; I think that's why it's so successful.  It seems to
me that if you put in too many redundant links you lose all context
in your hierarchy; you end up with a twisty maze of corridors all alike.

On the other hand, making people cruise through the hierarchy to find
a particular arcane item may not be the best scheme either.  Even
if a full Hypertext scheme isn't implemented, it'd be nice if the
user could do a string search on the current menu (as the CMS Gopher
client allows) or across all the titles in the hierarchy, allowing
a quick shortstop to the data desired.  It seems systems that grow
big (like Compuserve and Prodigy) all provide some sort of fast path.

/Rich Wiggins, Michigan State U
Newsgroups: alt.gopher,comp.windows.x.apps
From: rhb@hotsand.cnet.att.com (Richard H. Brandwein +1 908 949 2135)
Subject: Re: Problem compiling XGopher/Imake problem
Reply-To: rich.brandwein@att.com
Organization: AT&T Bell Labs - Holmdel, NJ
Date: Wed, 22 Jul 1992 15:37:13 GMT
Originator: rhb@hotsand
Keywords: xgopher imake xmkmf problem


In article <1992Jul21.154252.13664@trentu.ca>, ccgwt@trentu.ca (Grant Totten) writes:
|> 
|> Hello World,
|> 
|> 	This is probably a simple question for you Xperts out there.  I
|> looked in the FAQs for the approproate groups and RTFM until blue in the
|> face...
|> 
|> System:	DECstation 5000
|> 	Ultrix 4.2
|> 	X11R4 DECwindows (not Motif)
|> 
|> Problem:
|> 
|> 	I ftp'd and untarred the xgopher-1.1 release (is this the most
|> recent version?) and read the README file.  Then did an xmkmf.  No
|> problems.  Then did a make depend and got:
|> 
|> Make: Must be a separator on rules line 266.  Stop.
|> 
|> I checked the Makefile at line 266 and it's the definiton of emptyrule::
|> that it dies on.  I've seen this error before but for the life of me can't
|> figure out why it does this.  Is it something connected to DEC's less-than-
|> standard setup for X windows stuff?  Is it something silly I'm missing in
|> the Makefile?  My environment?  Phases of the moon?  :)
|> 
|> 	Any help would be appreciated as I'm stumped.  Please e-mail me
|> and I will summarize to the net if there is enough interest.
|> 
|> Thanks!
|> 
|> 
|> Grant Totten, Programmer/Analyst      |     THIS SPACE FOR RENT
|> Trent University, Peterborough Ontario| 
|> GTotten@TrentU.CA                     | 

I get my error on line 275:

	make: Fatal error in reader: Makefile, line 275: Unexpected end of
	line seen

which has a "InstallNonExecFile(xgopher,help,$(XGOPHERDIR))"
statement.
-- 
--
	Rich Brandwein		rich.brandwein@att.com
Newsgroups: alt.gopher
From: ury@humus.cs.huji.ac.il (My Friend Of Misery)
Subject: What gopher is?
Organization: Indiana University
Date: Wed, 22 Jul 92 09:58:26 GMT

What exacly is Gopher?

-- 
Ury Segal          | The opinions expressed are not necessarily those of the 
ury@cs.huji.ac.il  | University or IBM, Digital, Apple, HP or anyone else.
Phone: 02-971187   | They are mine, LO MIN HAHEFKER, as Bialik once said.
From: robertson@sdsc.edu (MR Mac)
Newsgroups: alt.gopher
Subject: please take me off the distribution list. Thx!
Date: 21 Jul 92 21:17:37 GMT
Distribution: alt
Original-To: gopher-news@boombox.micro.umn.edu




Michael


======================================================
MR Mac  	       	       	  robertson@sdsc.edu
                          San Diego Supercomputer Ctr.
Michael Robertson         (619) 534-5107
======================================================
From: emv@msen.com (Edward Vielmetti)
Newsgroups: alt.gopher
Subject: Unix and Hypertext
Date: 22 Jul 1992 21:57:39 -0400
Organization: Msen, Inc. -- Ann Arbor, Michigan
NNTP-Posting-Host: nigel.msen.com
X-Newsreader: Tin 1.1 PL3

This pulled from alt.hypertext; it's another system that knows how to
talk to gophers, and the first I've heard of it anywhere.  --Ed

[ Author was montulli@kuhub.cc.ukans.edu ]
[ Posted on 22 Jul 92 12:58:01 CDT ]

In article <1992Jul5.024817.11595@mnemosyne.cs.du.edu>, dmajumde@isis.cs.du.edu (deeptendu majumder) writes:
> 
> I always wondered why there is such a scarcity of public domain Hypertext
> system under Unix/X Windows environment. There seems to be plenty out there
> for PC & Mac. May be I am wrong. We seem to have a few public domain multi-media
> systems for Unix/X windows environment. But for some reason I do not seem
> to find interesting enough hypertext systems. Do all the work in this area
> go on in Mac/PC environment ?
> 
> I do not know whatever happened to Viola from Berkeley ??? Last time I 
> heard about it, it had incorporated hooks for WWW. That was sometime ago.
> 
> I am waiting for a version of Hyperbole with a GUI front end :-) I am not
> an emacs fan.
> 
> May be some day.. 
> 
> d.
The University of Kansas has developed a distributed unix (and others)
hypertext package, for use in its Campus Wide Information System (CWIS).
This package is simalar to WWW in fuction, and related to Hyperrez in
document design.  At this time there isn't an X windows version, but we're
working on it.  There will also be a MS-DOS, MAC, and VMS version available
in the future.  The hypertext reader, called Lynx, is also a nearly complete
gopher client as well.  This software is currently in Beta test, but it
can be obtained at the asking.  If you would like to try out a sample
distributed hyper-base, telnet to acs5000.cc.ukans.edu and login as "info".
The controls are alot like Hyperrez. (Please don't sue:)
-- 
  **************************************************************************
  *            T H E  U N I V E R S I T Y  O F  K A N S A S                *
  *      Lou  MONTULLI @ UKANVAX.bitnet                 Nothing difficult, *
  *                      Kuhub.cc.ukans.edu                is ever easy!   *
  *  UNIX,               Aixaix.cc.ukans.edu        ACS Computing Services *
  *   have more fun!     Ukanaix.cc.ukans.edu          Lawrence, KS 66044  *
  **************************************************************************
From: fwp@CC.MsState.Edu (Frank Peters)
Newsgroups: alt.gopher
Subject: Re: index for all of gopherspace
Date: 28 Jul 92 01:27:27 GMT
Distribution: na
Organization: Computing Center, Mississippi State University

In article <1992Jul28.002902.8570@sifon.cc.mcgill.ca> peterd@bunyip.com (Peter Deutsch) says:
:
:              your browsing tool is a great way to access the 
: information once it is built up (so a gateway to this service, with
: a suitable link at the top of every Gopher hierarchy, seems to make 
: sense) but I don't see that it is inherently a "Gopher problem"
: at all. It is a general Internet services problem, and we should be
: looking at generalized solutions, not ad hoc solutions for deployment
: within each new service.

Indeed.  I didn't use the reference to archie lightly.  It seems to
provide a very nice framework for indexing an uncoordinated and
distributed information pool like the internet.

The problem is that the information necessary to build a useful
information index isn't really there in a lot of protocols including
FTP and gopher.  I used archie to find a software package recently.  I
found files at a site that had a recently created version of the
package...yet that version turned out to be older than other versions
made available previously.

It might be a useful exercise (one that, no doubt, has been done
before) to identify what information about a given gopher entry or
package available for FTP would be useful for indexing and see how much
of it can be practically made available.  Things like (this isn't a
complete list...just off the top of my head) size, version ID, a brief
(one line or so) description, a keyword list, an archive date.
--
Frank Peters  -  UNIX Systems Programmer  -  Mississippi State University
Internet: fwp@CC.MsState.Edu  -  Phone: (601)325-7030  -  FAX: (601)325-8921
Original-To: Brad_Stone@byu.edu
Original-Cc: gopher-news@boombox.micro.umn.edu
Subject: Re: Gopher and Hypertext links 
             <01GMOH7RY2N68ZE4X0@yvax.byu.edu> 
Date: Wed, 22 Jul 92 15:49:41 EDT
From: emv@msen.com (Edward Vielmetti)
Newsgroups: alt.gopher
Distribution: alt

Brad, there is a hypertext system that knows how to deal with gopher
systems and that provides in-document links.  See the World Wide Web
stuff available for FTP from info.cern.ch:/pub/WWW/.  They use SGML
as their markup scheme and embed link information into the tags.

--Ed