HDTenEightyP/NetNews huggingface dataset:
From: heycke@sumex-aim.stanford.edu (Torsten Heycke)
Newsgroups: alt.gopher
Subject: Gopher and NeXT Digital Librarian Problem
Date: 24 Jul 92 20:57:52 GMT
Distribution: alt
Original-To: gopher-news@boombox.micro.umn.edu
Content-Type: TEXT/plain; charset=US-ASCII

We've found the Boolean operator search capability derived from using the NeXT's
Digital Librarian to index our gopher files to be useful. Unfortunately, we also
find that multiple directories of files result in recursive links in the gopher
directories (because DL apparently wants pathnames relative to the directory in
which the index resides). 

Are there other Digital Librarian gopher users out there who have experienced
this? figured out a work-around?

Thanks for any help!

Torsten
Newsgroups: alt.gopher
From: peterd@cc.mcgill.ca (Peter Deutsch)
Subject: Oops! (was: Re: index for all of gopherspace)
Organization: Bunyip Information Systems (the archie people)
Date: Fri, 31 Jul 1992 15:56:30 GMT

Ooops, I'm afraid I posted incorrect info a couple of days
ago about the Gopher-archie gateway. A thousand lashing
with a wet noodle <whip, whip> and here's a correction.


In article <1992Jul29.153142.2281@sifon.cc.mcgill.ca> peterd@cc.mcgill.ca (Peter Deutsch) writes:
.  . .

>>On a related topic- Peter, does that mean that the archie data and the
>>whatis data will be integrated?  I had a complaint from a user the other
>>day that my gopher/archie gateway didn't deliver whatis data, and I
>>thought- right!  Why doesn't it?
>
>Well, the info templates we gather will automate the
>maintenance of the "whatis" database, but I believe that
>the reason you can't get to the current archie whatis data
>is simply that the current Gopher gateway doesn't support
>the "whatis" command. .  .  .

That's the wrong bit. The problem is not with Gopher, it
is with the current version of the Prospero protocol.  All
the archie clients (_except_ the telnet client) use the
Prospero client library to send and receive their queries
and the currently deployed version doesn't have a way to
specify multiple databases and return the result. Thus,
there is no way to issue the queries from the archie
clients. Since the Gopher-archie gteways is based upon one
of these clients, this functionality is missing in Gopher,
but it's not fair to blame the people working on Gopher
for our shortcomings.

To be fair to Cliff Neuman, the author of Prospero, it was
not created to be the archie query protocol and has proved
remarkably adaptable in its new role. We've had to ask
Cliff for a few extensions for the next release and it is
amazing how much of his work seems to anticipate our needs.
It's a very nicely engineered piece of work.


BTW, there are a couple of other things missing in the
current clients because we couldn't do them easily with
the current version of Prospero, although they are minor
(think of it as a "Where's WALDO" and try and find them! :-)
We have worked with Cliff Neuman to fix things and the
next release will definitely be supporting multiple
databases through the Prospero interface...

Once again, sorry for the unintentional slur. <whip, whip>


				- peterd
Newsgroups: alt.gopher
From: schemers@leland.Stanford.EDU (Roland Schemers)
Subject: Re: Wish List Re:  gopher<->NNTP et al.
Organization: Distributed Computing Group, Stanford University
Date: Thu, 30 Jul 92 00:26:59 GMT

In article <Bs687G.8Cp@knot.ccs.queensu.ca> hooper@ccs.QueensU.CA (Andy Hooper) writes:
>All these gopher<->xyz gateway scripts are really neat, but they're
>proliferating like crazy. A single, table driven, gopher gateway daemon
>would be nice, to pull them back under some kind of umbrella something
>like inetd does for TCP/IP daemons. 
>

Of course. What I'm doing right now is trying to fill the empty space
in our gopherspace to show management what can be done with gopher, thats
why I've been whipping out these little gopher gateways. :-) I had already 
planned on bringing some of them together. Basically the first word in
the selector string would be the switch:

webster default SPELL gopher
nntp ls alt.gopher
whois schemers

Then the "master" gopher gateway perl script would check which gateway
was being called. The master gopher gateway could either be written
like inetd and fork off the real gateway, passing it the arguments,
or have all the smaller gateways builtin to it.

Roland



-- 
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            168 Pine Hall   (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
From: boone@convex.cl.msu.edu (Dennis Boone)
Newsgroups: alt.gopher
Subject: Re: index for all of gopherspace
Date: 27 Jul 92 20:11:22 GMT
Organization: Michigan State University, East Lansing

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.

Use WAIS as a filter: search the directory of sources for databases with
appropriate keywords.  Then search the resulting sources for the stuff you're
interested in.  I suspect that some of the clients make this more difficult
than it should be, considering the basic need for this functionality.

Dennis Boone
Michigan State
--
 == Frustration is portable. ==
From: dan@engr.latech.edu (Daniel Len Schales)
Newsgroups: alt.gopher
Subject: Re: official g2nntp
Date: 31 Jul 92 16:27:36 GMT
Reply-To: dan@engr.latech.edu
Organization: Louisiana Tech University

In article 15389@mercury.unt.edu, billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager) writes:
>I am aware of at least two different Gopher to NNTP programs.  I am running
>the one from LSU and not the one from Stanford.  I think it would be preferable
>to standardize on ONE if possible.  The LSU one is straight-forward and has
>worked flawless for me.
>
>Any opinions especially from U of Minn?
>
>


That's Louisiana Tech, we take that kinna personal down this way if you know what I
mean!
:) 

Danny
From: chrisl@mirc00.ncms.org (Chris Lang)
Date: Wed, 22 Jul 1992 13:43:26 -0400
       "Is Less Really More?" (Jul 22, 12: 38pm)
X-Mailer: Mail User's Shell (7.2.3 5/22/91)
Original-To: gopher-news@boombox.micro.umn.edu
Subject: Re: Is Less Really More?
Newsgroups: alt.gopher
Distribution: alt

bert desimone <BDESIMON@uga.cc.uga.edu> writes:
> OK, let's say you have an environment varaible set for PAGER. Some
> people like to set this to less so that man and other utilites that
> look for this variable will use less.  Now, you leave the PAGER_COMMAND
> for the Gopher client -- set in conf.h -- as more.  Crank up Gopher,
> and behold the Pager command. It is less.  No problem??  Well, there
> seem to be a few.  The main one has to do with the way that less
> handles, or rather doesn't handle, the character sequences used for
> toggling screen highlighting for search terms in retrieved documents.
> Instead of the highlighting action taking place, the highlighting
> characters are displayed (..this is the ^[[7mterm^[[m searched for..).

This problem can be solved by using the 'r' and 'f' options to less.  Try
setting your LESS environment variable to '-rf'.  The -r option causes less
to enter 'raw' mode, where it passes the control characters through unchanged,
and -f forces it not to treat the file as a binary file, which it ordinarily
would if it saw the control characters in the file.

However, while that will fix 'less' for use with Gopher, I second the
suggestion of adding a GOPHER_PAGER variable, particularly since I don't
want to leave 'r' and 'f' in my global LESS variable.

Hope this helps anyone else who would rather use 'less' as their Gopher
pager...

 -Chris
Newsgroups: alt.gopher
From: schemers@leland.Stanford.EDU (Roland Schemers)
Subject: Better Better Gopher->whois script available
Organization: Distributed Computing Group, Stanford University
Distribution: alt
Date: Wed, 22 Jul 92 05:21:43 GMT

In article <199207220129.AA25891@mudhoney.micro.umn.edu> lindner@boombox.micro.umn.edu. writes:
> #
> # a straight whois query, expect format of "whois <hostname> query..."
> #

Actually there is a better way to send back the index.
For example:

>    &reply("0Raw Search Results\twhois $host $query\t$Gatehost\t$Port");

Could just be:

&reply("0Raw Search Results\t$query\t$host\t43");

This cuts out the middle man :-)

Same with all the other ones:

>	      &reply("0$1\twhois $host $newquery\t$Gatehost\t$Port");
	      &reply("0$1\t$newquery\t$host\t43");

Thats how my current script does it.

From my previous (long winded :-O) posting, the path becomes:

client "qwhois host query"  -> mudhoney
mudhoney "query"            -> whois server 
whois server "whois output" -> mudhoney
mudhoney "dir result"       -> client
client "give me raw result" -> whois server
whois server "whois output" -> client

This is still fairly long, but shorter then the first version :-)

Roland


-- 
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            168 Pine Hall   (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
Newsgroups: alt.gopher
From: peterson@choctaw.NoSubdomain.NoDomain (Bob Peterson)
Subject: Re: Gopher and Hypertext links
Keywords: hypertext
Reply-To: peterson@csc.ti.com
Organization: Texas Instruments
Distribution: alt
Date: Thu, 23 Jul 1992 14:08:14 GMT

In article <1992Jul23.020752.12706@msuinfo.cl.msu.edu>, rww@mugwump.cl.msu.edu (Richard W. Wiggins) writes:
|> ...
|> 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.

  For some time now I've used WAIS to index my file tree.  The following
two lines run as part of a script executed daily from crontab.

        ls -lLRA /conestoga/u2/peterson                               \
                >/conestoga/u3/peterson/WAISIndexes/ls-lRA
        /conestoga/u2/peterson/Bin/waisindex                          \
                -t para                                               \
                -d /conestoga/u3/peterson/WAISIndexes/Peterson_Tree   \
                /conestoga/u3/peterson/WAISIndexes/ls-lRA
        rm /conestoga/u3/peterson/WAISIndexes/ls-lRA

  If you do something akin to the above, perhaps based on Dennis
Boone's gophertree, and make the index available from Gopher, you have
exactly what you ask for: an index of the Gopher burrows.

|> /Rich Wiggins, Michigan State U

    Bob
From: fogel@jester.usask.ca (Earl Fogel)
Newsgroups: alt.gopher
Subject: Re: index for all of gopherspace
Date: 29 Jul 92 15:41:03 GMT
Organization: University of Saskatchewan

The problem with the Wais directory-of-servers is that the database
descriptions are woefully incomplete.  Searches for "Mac" and "Macintosh",
for example, produce very different results.

And I'm not convinced we can rely on gopher server administrators to
maintain up-to-date, keyword-rich site descriptions, as has been suggested.

Instead, I wonder if a site description database could be created
automatically, by waisindexing the information at each site, and
compiling a list of the top-scoring words.  The directory-of-servers
would then maintain a database of the most frequently occuring 1%
of the words in each database.

Presumably, "Mac" and "Macintosh" would make the most-frequent list
for Mac-related databases, while "dessert" and "cake" would make the
list for recipe databases.

Earl Fogel
-------------------------------------------------------------------
fogel@sask.usask.ca		Computing Services, Room 56 Physics
Phone: (306) 966-4861		University of Saskatchewan
Fax:   (306) 966-4938		Saskatoon, Sask. CANADA, S7N 0W0
Date: Wed, 29 Jul 92 07:42:40 +0200
From: fkappe@fiicmds04.tu-graz.ac.at (Frank Kappe)
Original-To: gopher-news@boombox.micro.umn.edu
Subject: Newspapers on Gopher
Newsgroups: alt.gopher
Distribution: alt

Hi,

I am looking for newspapers that are available on internet (through gopher or
otherwise). So far I found the "Daily Texan" and "Minnesota Daily". Is anybody
aware of any other newspapers (including non-english and non-gopherized ones)
on internet?

Thanks,
        Frank

----------------------------------------------------------------------------
Frank M. Kappe                                     fkappe@iicm.tu-graz.ac.at
Institute for Information Processing and Computer Supported New Media (IICM)
                  Graz University of Technology, Austria
----------------------------------------------------------------------------
Newsgroups: alt.gopher
From: schemers@leland.Stanford.EDU (Roland Schemers)
Subject: Re: official g2nntp
Organization: Distributed Computing Group, Stanford University
Date: Fri, 31 Jul 92 18:50:09 GMT

In article <1992Jul31.183208.18646@leland.Stanford.EDU> schemers@leland.Stanford.EDU (Roland Schemers) writes:

># ls $group                  -> list group's articles and sub-groups
># lsa $group                 -> like "", sends "article" & "lsa" commands back
># lsb $group                 -> "" sends "body" & "lsb" commands back
># lsh $group                 -> "" sends "header" & "lsh" commands back

I suppose something to go along with these would also be an option to
return either an article number or article id in the selector for an
article:

0Name#nntp article <id>#host#port
0Name#nntp article <id>#host#port
0Name#nntp article <id>#host#port

That would probably involve too much overhead because you would have to 
do a XHDR to get the Subject, then another XHDR to get the Message-IDs. 
Probably not worth it.

Roland


-- 
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            168 Pine Hall   (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
From: lindner@mudhoney.unet.umn.edu (Paul Lindner)
Newsgroups: alt.gopher
Subject: Re: Sockfd = 0???
Date: 21 Jul 92 20:45:04 GMT
Organization: Colorado SuperNet, Inc.

In alt.gopher you write:

>Can anyone explain why gopherd 1.01, when running as gopherls, would want
>to write to a file descriptor of 0, instead of 1 or 2?

Ooops, my mistake.  

The cleaned up code does the following:

listdir(fileno(stdout), "/");

Thanks!-- 
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | GopherMaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
Newsgroups: alt.gopher
Subject: Re: Executing shell scripts
From: pmurray@watson.lib.muohio.edu (Peter Murray)
Date: 24 Jul 92 13:01:34 -0500
Organization: Miami University Libraries

SEB1525@MVS.draper.com (Steve Bacher) writes:
: In article <1992Jul20.101113.11811@miavx1.acs.muohio.edu>,
: pemurray@miavx1.acs.muohio.edu writes:
: 
: >Interactive shell scripts aren't going to work in the standard release because
: >there is no mechanism for the client to pass information back to the server
: >(other than a "query" request or something along those lines).
: 
: Wouldn't these work if the "exec:" hack were modified to take the
: query data and pass it to the script following the args embedded
: in the "exec:" selector path?  The script would then see the options
: following the "hard-coded" ones.  Or else the tab character could be
: passed on the command line to delimit the variable options.  On Unix
: systems this would have to be quoted, of course.

This isn't an interactive shell script, though.  The application I have
in mind is forking of an expect script to automatically log a user on 
to our library automation system.  Data has to be passed interactively
between the client and the computer the user is telnetting to.

Peter
-- 
Peter Murray, Library Systems Manager        pmurray@watson.lib.muohio.edu
King Library Technical Support                      pemurray@miavx1.bitnet
Miami University, Oxford, Ohio                              W:513/529-2884
Newsgroups: alt.gopher
From: schemers@leland.Stanford.EDU (Roland Schemers)
Subject: xgopher and 'q' type
Organization: Distributed Computing Group, Stanford University
Date: Wed, 22 Jul 92 00:50:14 GMT

I've hacked up the xgopher.1.1a client to support (some what) the
'q' type.  The limitations (due to time and other things I'm 
supposed to be doing :-), it has the following limitations:

 Query Types must return type '0' (file)
 Only the first prompt is displayed and returned from input.

Its mainly for "seeing" the 'q' in action with xgopher.

Considering how ambitious the 'q' type is (although the curses client
was trivial to modify), and lack of interest, I would still like to see a 
simple type like '7' that returns a file. This patch to xgopher basically
gives you that.

In any event, I've placed the file:

 xgopher.query.shar

In the pub/gopher/incoming directory on boombox.

Roland
-- 
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            168 Pine Hall   (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
Newsgroups: alt.gopher
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: xgopher segmentation violation after applying query patch
Organization: Draper Laboratory
Date: Wed, 22 Jul 1992 15:34:00 GMT


After application of the query patch to xgopher (1.1a),
it core dumps with a segmentation violation when I try to
retrieve a file from the server.  It dies at line 414 in util.c,
function getFile, because the indexString is null.  (Actually it dies
in writeString, presumably.)

Apparently the addition of the writeString(s,indexString) did it.
Should be trivial to fix.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Newsgroups: alt.gopher
From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Subject: Re: Conversion Confusion!
Organization: University of North Texas
Date: Tue, 21 Jul 1992 17:01:42 GMT

heidis@sfsuvax1.sfsu.edu (Heidi Schmidt) writes:

>We have experienced some difficulty in converting from Gopher 0.9 and
>the Wais gateway to Gopher 1.01.  Any assistance would be appreciated!

>Our Gopher data directory is: /usr/mail1/gopher
>Our Wais directory is: /usr/support/wais/wais-sources

>We tried creating a link to "test.src" using the example in server.c:

>Name=Test
>Path=waissrc:/usr/support/wais/wais-source/test
>Type=7
>Host=+
>Port=+

>This resulted in the error message: "File does not exist."

I got bitten by this one too.  Under 1.01, the WAIS source file MUST be 
under the Gopher data directory (even with chroot off).  I run without chroot
and I symbolically linked my wais-sources directory into my Gopher directories.
Newsgroups: alt.gopher
Subject: Is there a FAQ?
From: bkreed@oread.cc.ukans.edu
Date: 24 Jul 92 18:01:24 CDT
Organization: University of Kansas Academic Computing Serces

]Is there a FAQ for this group?  If so could someone please post it or
mail it to me.  Thanx-- 


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
There are very few personal problems  |	Ghostrider@f120.n280.z1.fidonet.org
that cannot be solved by suitable     |      bkreed@oread.cc.ukans.ed
Aplications of plastic explosives.    |            EGARC/BKREED
   ---Anonymous                       |          Bryan Kennedy Reed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Newsgroups: alt.gopher
From: ccx009@cch.coventry.ac.uk (Adam Bentley)
Subject: Gopher for Windows?
Organization: Coventry University
Date: Mon, 27 Jul 1992 13:27:37 GMT


This is a simple enough question. Has anyone written a gopher client
for MS-Windows 3.0/1? I've heard that one may be available, which will
support additions like GIF displaying .......

Thoughts anyone?

(Please send replies via email, or via email and alt.gopher...)

thanks.
-- 
						_
					       /-\dam

FLESH: Adam Bentley (Fraggle), Systems/Networking, Coventry University. UK
Newsgroups: alt.gopher
From: everette@ncsuvm.cc.ncsu.edu (Everette Allen)
Subject: Which gopherholes support sound...
Organization: NCSU Computing Center
Date: Thu, 23 Jul 1992 14:15:30 GMT

I am interested in hearing sound with the gopher client on my mac. Is there
an index or list of holes that have sound resources available?  Time of day
restrictions, etc.  EVerette
Newsgroups: alt.gopher
From: ccgwt@trentu.ca (Grant Totten)
Subject: Problem compiling XGopher/Imake problem
Keywords: xgopher imake xmkmf problem
Reply-To: ccgwt@trentu.ca (Grant Totten)
Organization: Trent University
Date: Tue, 21 Jul 1992 15:42:52 GMT


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                     | 
Newsgroups: alt.gopher
From: sendall@dxpt01.cern.ch (Mike Sendall)
Subject: Re: What is "html"
Reply-To: sendall@dxcern.cern.ch
Organization: CERN (European Laboratory for Particle Physics)
Distribution: alt
Date: Tue, 21 Jul 1992 07:45:51 GMT


In article <8FEFD70756082C76@CC.UTAH.EDU>, JONZY@CC.UTAH.EDU (Jonzy) writes:
|>
|>I would appreciate any information on "html".  What is it?
|>Where, if any, is documentation for "html" available?
|>

html is the sgml-like hypertext markup system used by the WWW (WorldWide Web) project. The easiest way to find out more is to telnet to info.cern.ch which
connects you to WWW and then follow the hypertext links. If you have
any problem with this, let us know.


------------------------------------------------------------------------
                                                   | D.M.Sendall
Mike Sendall                                       | ECP Division
European Laboratory for Particle Physics           | CERN
                                                   | CH-1211 Geneva 23
sendall@dxcern.cern.ch  (also on EUNET/UUCP)       | Switzerland
sendall@cernvm.bitnet                              |
vxcern::sendall         (on HEP/SPAN DECNET)       | Tel +41 22 767 4968
                                                   | Fax +41 22 767 7155
------------------------------------------------------------------------
Newsgroups: alt.gopher