HDTenEightyP/NetNews huggingface dataset:
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: FTP Gateway - Help Please
Organization: University of Minnesota, Minneapolis
Distribution: comp
Date: Fri, 2 Oct 1992 02:41:42 GMT

In <9210012245.AA01108@sdacs.UCSD.EDU> chris@sdacs.ucsd.edu (Chris Frymann) writes:

>A group I have been working with has been experimenting with Gopher and trying
>to
>understand Gopher access to FTP archives.

>We have looked at some examples of FTP links, such as:

>Name=Interest Group Lists
>Type=1
>Port=70
>Path=ftp:ftp.nisc.sri.com@netinfo/
>Host=ashpool.micro.umn.edu

>but have not been able to figure out what the final entry ("Host") is doing. 

The Host= line specifies the gateway host.  In this case it can be any
unix gopherd 1.0x and above.  The ftp host is stuffed in the path
component, as is the ftp directory.

If you want, set the Host= line to Host=+ to use the current hostname.

>We found the notes in the "ftp.c" source code which refer to "g2fd" but then we
>lose the trail and can't seem to figure out where to pick it up.
>Can anyone explain what's going on, in particular, what service is being 
>provided by a host such as ashpool and how we could install it on our own local
>system?

The ftp gateway code is in all Unix gopher servers.  Just change the
host to your own unix gopherd host...
--
 | 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: comp.infosystems.gopher
From: toriver@flipper.pvv.unit.no (Tor Iver Wilhelmsen)
Subject: Re: Funny escape sequences in documents from WAIS-sources
Organization: ProgramVareVerkstedet - UNIT
Date: Thu, 1 Oct 92 12:41:08 GMT

In article <1992Oct1.080418.22720@lth.se> anders@dit.lth.se (Anders Ardo) writes:
>Hello,
>  I have a problem when accessing some WAIS-sources through Gopher or
>swais.
>When I try to view a document I get a garbled screen. It turns out
>that the document contains a lot of different escape sequences, for
>example many words are bracketed by ESC( and ESC). These escape
>sequences cause the mess I get. This holds for several different
>sources for example usenet-cookbook.src and bible.src.
>Using xwais to look at the same document at the same sources works
>like a charm, no problems whatsoever.
>
>What is happening? Can I fix this locally?
>

The problem is that the pager you are using does not pass escape sequences
through, but "quotes" them. The wais-server sends vt100 escape sequences
to turn on/off emphasis (inverse text, underlining, I'm not sure - I get
it as inverse text in an x-term) around the search term in the text. To
fix this, you could set the PAGER variable to 'less -srf', or equivalent
(pass all data raw to the terminal, treat as binary file).


>       Anders
>
> Anders Ardo                       Tel: int+46 46 107522
> Dept. of Computer Engineering     fax: int+46 46 104714
> University of Lund, P.O. Box 118  Internet: anders@dit.lth.se
> S-221 00  Lund, Sweden
>                

- Tor Iver
-- 
"I'm a Derek, and Dereks don't run!" - Derek in 'Bad Taste'
toriver@pvv.unit.no
Standard disclaimer should apply to this, I guess...
"Reality is a poor escapism for people who cannot handle roleplaying" - Me
Newsgroups: comp.infosystems.gopher
From: schoultz@admin.kth.se (Rickard Schoultz)
Subject: Re: GOPHERD AND WAIS INDEXES
Organization: Royal Institute of Technology, Sweden
Distribution: comp
Date: Sat, 3 Oct 1992 10:20:06 GMT

prw@albert.mannlib.cornell.edu writes:
>I am tring to get GOPHERD to work with WAIS indexes. I have compiled it
>with the WAIS libraries and gopherd does not work with WAIS indexes.  I can
>setup an index server (gindexd) and it works fine.  Could someone please
>send me a detailed list of instructions on how to get gopherd 1.03 to work
>with WAIS indexes with out an index server.  I feel that my problem may be
>with a .Link, .cap, or some such file, that is not setup correctly.

I had the same problem, but when I tried to run gopherd in non chroot-mode
(in inetd:  /usr/local/etc/gopherd gopherd -I -c /gopherdir 70) it worked.
If you are concerned about security, you can also build the index while
chroot'ed: 
  /usr/etc/chroot $Gopherdir /bin/waisindex -r /directory-to-be-indexed/

Note that waisindex, in this example, must exist on $Gopherdir/bin/waisindex,
and /directory-to-be-indexed real path is $Gopherdir/directory-to-be-indexed.

/Rickard
-- 
Rickard Schoultz			Internet: schoultz@admin.kth.se
KTH - TS/Data				+46-8-790 90 88   (voice)
S-100 44 Stockholm (SWEDEN)	    	+46-8-10 25 10    (fax)
Newsgroups: comp.infosystems.gopher
From: rob@dragon.acadiau.ca (Rob Hutten)
Subject: Problem with gopher running scripts
Organization: Acadia University
Date: Tue, 29 Sep 1992 18:43:09 GMT

First off, thanks to those who replied to my problem re: running scripts
from gopher.  All of you suggested using the -c option, yet I am
still having problems.

I have gopher's data directory set up as dragon:/usr/local/lib/gopher
(~gopher).  All the text files in ~gopher work are visible to the
client as they should be.  My scripts, however, show up in the listings
but will not execute.

I've kickstarted the server on dragon:
	gopherd -c -u gopher /usr/local/lib/gopher

In ~gopher I have a directory called "Test Scripts".  A null file called
"Test Script" is present, and "Test Scripts/.cap/Test Script" contains:

Name=Un Scripto Testo
Numb=1
Type=0
Path=exec::/usr/local/lib/gopher/.lib/testscript
Host=dragon
Port=70

/usr/local/lib/gopher/.lib/testscript contains:

#!/bin/tcsh
echo testing
ls
# end testscript


Now, if my understanding is correct, selecting "Un Scripto Testo" from the 
"Test Scripts" menu should execute /usr/local/lib/gopher/.lib/testscript.
Instead, I get this:

0Server error: '/usr/local/lib/gopher/.lib/testscript' does not exist!!         error.host      1

 
My understanding of gopherd's -c option was that the server would be able
to access files all over the machine.  Why can't it see testscript?

I've tried running gopherd with root ownership but it made no difference.

I've also tried running gopherd without the -c option and creating
~gopher/bin which contained a link to tcsh.  No luck there, either.

Can anyone see any glaring oversights on my part?  Sorry for running to
the net with all my problems, but I'm running out of ideas...

-Rob
-- 
Rob Hutten, Unix guy  
Acadia University Computer Centre, Wolfville, NS.
rob@dragon.acadiau.ca OR rob.hutten@acadiau.ca
Standard disclaimers apply.  
Xref: sparky comp.infosystems.gopher:601 comp.infosystems.wais:518
From: ccoprmm@prism.gatech.EDU (Michael Mealling)
Newsgroups: comp.infosystems.gopher,comp.infosystems.wais
Subject: WAIS and Gopher working together on a PC with windows...
Date: 2 Oct 92 19:03:18 GMT
Followup-To: poster
Organization: Georgia Institute of Technology

In the 5 minutes that I used WAIS and Gopher on a PC with Windows 3.0
I found out that in order to get them to work I have to run two seperate
packet drivers (WAIS needing Lan Workplace for Dos). Has anyone
found a way around this and what is the easiest way to have both working
together on the same machine?

(And DOS folx ask me why I use Unix....)


-- 
------------------------------------------------------------------------------
Michael Mealling                     ! Hypermedia WWW, WAIS, and gopher will be
Georgia Institute of Technology      ! here soon via MIME. Your view of the 
Internet: michael@fantasy.gatech.edu ! internet is about to change completely!
Original-To: gopher-news@boombox.micro.umn.edu
Subject: gopher-to-ftp
Date: Fri, 02 Oct 92 08:57:51 +0100
From: Utermann@Uni-Augsburg.DE (Ralf Utermann)
Newsgroups: comp.infosystems.gopher
Distribution: comp


Mark P. McCahill writes:

>The ashpool machine is running a gopher to ftp gateway which translates gopher 
>requests into an ftp session. The Path is used by the gateway process on 

What is the best way to have my own gopher server running this gateway?
In the gopher1.03 distribution there is a file gopherd/ftp.c which claims, it 
has to be compiled with "make g2fd", but this is not in the Makefile.
How di I compile it (just cc does not do it) ?

	Ralf Utermann
_______________________________________________________________________________
	University of Augsburg (Germany)
	Institut of Physics - Theoretical Physics I
	Memmingerstr.6
	W-8900 Augsburg  	Tel.: 0821/5977-235 Fax: 5977-225
	e-mail: utermann@Uni-Augsburg.DE
From: bartont@next2.msci.memst.edu (Tom Barton)
Newsgroups: comp.infosystems.gopher
Subject: Launching gopherd from NeXT rc.local
Date: 6 Oct 92 14:46:11 GMT
Organization: Mathematical Sciences, Memphis State University

I have gopherd (v1.01) being launched in /etc/rc.local on a NeXT (v2.1). It
loads but isn't able to serve up the gopher directory tree. Restarting it
from the command line gets things going, but doesn't solve the problem of
auto-start upon reboot. gopherd was compiled with the SERVERDATA variable in
Makefile.config set correctly, and as a voodoo sacrifice I've also included
the gopher root in the startup command used in rc.local (see below). I've
seen this question asked here once before but I didn't notice any replies.
Here's how it is started in rc.local:

if [ -f /usr/local/etc/gopherd ]; then
	/usr/local/etc/gopherd -c -u bartont -l /usr/adm/gopherd.log \
		/home/bartont/gopher1.01/exp 70
	(echo -n ' gopherd') > /dev/console
fi

Much obliged for any wisdom you may have to offer.

-- 
Tom Barton			       Internet: bartont@hermes.msci.memst.edu
Dept of Math Sciences	                 Bitnet: bartont@memstvx1
Memphis State University	       
Xref: sparky comp.infosystems.gopher:545 ch.network:72 comp.os.ms-windows.apps:3219
From: sysop@sicsoft.epfl.ch (Zufferey Ch. S.F.I.T CH1015 Lausanne)
Newsgroups: comp.infosystems.gopher,ch.network,comp.os.ms-windows.apps
Subject: Gopher for Windows 3.1 (ZGopher 0.0.16)
Keywords: Gopher, ZGopher
Date: 29 Sep 92 11:08:59 GMT
Reply-To: zufferey@sic.epfl.ch
Followup-To: comp.infosystems.gopher
Organization: Swiss Federal Institute of Technology, Lausanne, CH

MS Windows Gopher reader for Windows 3.1...


- on "ftp.cica.indiana.edu" in pub/pc/win3/uploads, "zgopher0.exe"...
- written in MS Visual Basic
- Alpha release 
- feel free to tune the available sources



-- 
|	  Christian Zufferey
|	  PC Support, Central Computing Service
|	  Swiss Federal Institute of Technology
|	  EPFL, Ecublens, CH-1015 Lausanne
|                                        ___   ___   _   ___     | |
|    Tel: +41-21.693.22.11              /__   /_    /    /     |     |
|    Fax: +41-21.693.22.20             ___/  /     /    /        | |
| E-mail: zufferey@sic.epfl.ch
Newsgroups: comp.infosystems.gopher
From: boone@convex.cl.msu.edu (Dennis Boone)
Subject: Item Ordering
Keywords: weight order Numb=
Organization: Michigan State University, East Lansing
Date: Mon, 28 Sep 92 21:12:32 GMT

I'd like to see the item-ordering scheme move from absolute slot numbers to
a weighting system.  I have several directories in which I'd like to be able
to force things to the BOTTOM.  I can't do that right now.

Anyone else want something like this?

Dennis
--
 == If you choose not to decide, you still have made a choice. ==
From: emv@msen.com (Edward Vielmetti)
Newsgroups: comp.infosystems.gopher
Subject: Re: Funny escape sequences in documents from WAIS-sources
Date: 1 Oct 1992 13:33:36 -0400
Organization: Msen, Inc. -- Ann Arbor, Michigan
NNTP-Posting-Host: nigel.msen.com
X-Newsreader: TIN [version 1.1 PL6]


the 'funny escape codes' are boldface markers, and they are inserted by
the client *not* the server.  If you don't like them hack them out of the
client.  (Or fix your pager to display them right.)   I'd argue that the
boldfacing should be taken out when the file is saved or mailed, too, that
would be a little bit of extra work to undo the 'damage'.

  Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
        Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 4562
         There's something wrong with the idea that 'information'
                is a commodity like a desk or a chair.


Newsgroups: comp.infosystems.gopher
From: fredb@calvin.edu (Fred Bremmer)
Subject: GopherShare
Followup-To: comp.infosystems.gopher
Organization: Calvin College Computer Center
Date: Tue, 6 Oct 1992 19:02:52 GMT

In article <YNWQBRVG@cc.swarthmore.edu>, hirai@cc.swarthmore.edu (Eiji
Hirai) wrote:
> 
> Andrew Gilmartin <Andrew_Gilmartin@Brown.Edu> writes:
> > Associating a Gopher type with a Macintosh application is the
> > way to go. The ultimate Gopher client would be an external file
> > system linking a Gopher server to the Macintosh
> > desktop--GopherShare.
> 
> Hmm, that would be very neat.  However, if I understand you correctly, this
> would involve writing GopherShare extensions into the MacOS, which seems to
> entail a problem that's synonomous to implementing a read-only NFS on top
> the MacOS.

The Mac OS already has the extensions that support read-only remote
filesystems, it's called AppleShare (hence Andrew's derivation,
GopherShare).  There is a free software package for unix machines, called
CAP, which presents a unix filesystem as an AppleShare fileserver.  I've
been wondering how difficult it would be to modify CAP to look at
gopherspace instead of the disk.

If it worked, you could drag gopher text documents and HQX files to your
hard drive and play with them locally.  Reading large remote text files
might require making a temporary local copy to allow text editors to seek
back and forth through the "disk".  Get Info would probably show you the
link information, like "=" does in the curses client.  

Prompting for WAIS keywords might be a bit more difficult, since the finder
doesn't have a built-in method for taking input before opening a folder. 
Maybe WAIS sources could launch the WAIStation application.  CSO phonebooks
might launch a special Phonebook App that knows how to negotiate with
remote servers via MacTCP.  I bet sound files could be made to behave
exactly like System 7 sound files.  The Finder's View by Size and View by
Date might not work, but the other View options should work fine.  

It's definitely an interesting idea.  Does anybody else have thoughts on
how this might work?
--
 Fred Bremmer    |     Internet: fredb@calvin.edu
 Calvin College  |.._. ._. . _..  _... ._. . __ __ . ._.
 Grand Rapids,   |      Phone:   (616) 957-6144
 MI USA   49546  |      Fax:     (616) 957-8551
Date: Tue, 6 Oct 92 08:22:55 CDT
From: mpm@boombox.micro.umn.edu ("Mark P. McCahill" )
Reply-To: "Mark P. McCahill"  <mpm@boombox.micro.umn.edu>
Original-To: gopher-news@boombox.micro.umn.edu
Subject: cloned gopher server at the University of Minnesota
Newsgroups: comp.infosystems.gopher
Distribution: comp

We have cloned the top-level gopher server for the University of Minnesota;
there are now two (redundant) gopher servers named
        gopher.tc.umn.edu      port 70
        gopher2.tc.umn.edu     port 70

The reason for doing this is to increase the reliabilty of our gopher service.
Having two servers makes it possible for us to take one server down without
affecting service. Also, two servers make it possible for us to spread the
load between the servers andso to continue to use small/inexpensive server 
hardware. Of course, to really take advantge of the redundant servers, client 
software must be clever enough to first try one server, then (if necessary) try 
the other. You can expect to see clever gopher clients that support this feature
in the near future.


Mark P. McCahill      
                                                                
University of Minnesota                      Computer & Information Services
room 125 Shepherd Labs                             mpm@boombox.micro.umn.edu    
100 Union Street SE                                     612 625 1300 (voice)    
Mpls., MN 55455                                           612 625 6817 (fax)

Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: BUG in gopher1.03 ? (printf's in DEBUG mode)
Keywords: gopher bug inetd debug
Organization: University of Minnesota, Minneapolis
Date: Fri, 2 Oct 1992 01:29:03 GMT

In <1992Sep22.152957.4590@tigger.jvnc.net> aggarwal@tigger.jvnc.net (Vikas Aggarwal) writes:

>When running the gopherd daemon frmo inetd with the -D flag (for debug),
>the server does not return anything (this is under v1.03).

This is with the Inetd option only.

>Removing the DEBUG option fixes the server.

>I think its because of the 'printf()' statements in the gopherd code-
>when running from under inetd, stdout is actually closed, so unless
>the code messes with the file descriptor table and points the stdout
>to the LOGFILE or something, the printf()'s are not valid...

stdout is connected to the client.  The debug stuff should be coming
at the client.  The client won't like it...

>Or is it something else that I am missing. I was expecting the DEBUG
>messages to show up in the LOGFILE, but unless the 'printf()' statements
>under the DEBUG options are changed to 'fprintf(...)', I don't think
>that's going to happen.

>Is there a tricky/easy way to reopen and reallocate stdin to the LOGFile?
>I did try something, but it didn't work the way it should.

You can't move the stdout to the logfile without changing everything
to fprintf.  remember stdout is attached to the client process when
using inetd.  Try running it by hand...

gopherd -IDc /home/gopher-data
.....



--
 | 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: comp.infosystems.gopher
From: tiktin@idiotix.cs.uoregon.edu (David Mark Tiktin)
Subject: Re: Problem with gopher running scripts
Reply-To: tiktin@cs.uoregon.edu
Organization: University of Oregon
Date: 30 Sep 92 08:48:56


>In ~gopher I have a directory called "Test Scripts".  A null file called
>"Test Script" is present, and "Test Scripts/.cap/Test Script" contains:
>
>Name=Un Scripto Testo
>Numb=1
>Type=0
>Path=exec::/usr/local/lib/gopher/.lib/testscript
>Host=dragon
>Port=70

The problem is that you're giving the full path to the script file.  The
gopher server assumes that any path name is relative to its home directory, 
in your case /usr/local/lib/gopher.  So your PATH entry should be:

Path=exec::/.lib/testscript

BTW, if the server was allowed to follow absolute path names, there'd be no
stopping it from wandering all over your file system, execing whatever it
wanted!  Not the behavior we want from the server.


David Tiktin
--
tiktin@cs.uoregon.edu
From: lindner@mudhoney (Paul Lindner)
Newsgroups: comp.infosystems.gopher
Subject: Gopher Weather Service moving..
Date: 2 Oct 92 03:45:30 GMT
Reply-To: lindner@boombox.micro.umn.edu
Distribution: comp
Original-To: gopher-news@boombox.micro.umn.edu (Gopher News Mailing List)
X-Mailer: ELM [version 2.3 PL11]

Here Ye! Here Ye!  

All people that have links pointed at mermaid.micro.umn.edu's Weather
directory should move them immediately.

The weather Updates are now being done to the machine
ashpool.micro.umn.edu

A sample link:

Name=Weather
Path=1/Weather
Host=ashpool.micro.umn.edu
Port=70
Type=1

In a few days I'll be appending a notice to the old weather
forecasts/current conditions on mermaid.  So switch your links before
your users notice the message :-)

The reason behind this is that mermaid is supposed to be used for
classroom/instructional computing, not gopher serving..

Ahhh politics..

-- 
 | 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: comp.infosystems.gopher
From: lengge@chx400.switch.ch (Thomas Lenggenhager)
Subject: Re: Gopher for Windows 3.1 (ZGopher 0.0.16)
Keywords: Gopher, ZGopher
Organization: Swiss Academic and Research Network SWITCH
Date: Wed, 30 Sep 1992 06:44:20 GMT

it is also available a bit nearer, on the mirror of the Windows archive on
	nic.switch.ch
in the directory mirror/win3/uploads

-rw-rw-r--  112612 Sep 28 15:36 zgopher0.exe
-rw-rw-r--     558 Sep 28 15:36 zgopher0.txt

Thomas

In article <1992Sep29.120859@sicsoft.epfl.ch> zufferey@sic.epfl.ch writes:
>MS Windows Gopher reader for Windows 3.1...
>
>- on "ftp.cica.indiana.edu" in pub/pc/win3/uploads, "zgopher0.exe"...
>- written in MS Visual Basic
>- Alpha release 
>- feel free to tune the available sources
>
>|	  Christian Zufferey
>|	  PC Support, Central Computing Service
>|	  Swiss Federal Institute of Technology
>|	  EPFL, Ecublens, CH-1015 Lausanne
>|                                        ___   ___   _   ___     | |
>|    Tel: +41-21.693.22.11              /__   /_    /    /     |     |
>|    Fax: +41-21.693.22.20             ___/  /     /    /        | |
>| E-mail: zufferey@sic.epfl.ch
-- 
===============================================================================
               SWITCH - The Swiss Academic and Research Network
   Thomas Lenggenhager, SWITCH, Limmatquai 138, CH-8001 Zurich, Switzerland
   INET: lenggenhager@switch.ch | Tel: +41 1 261 8178 | Fax: +41 1 261 8133
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: Problems with gopher running my scripts
Organization: University of Minnesota, Minneapolis
Date: Fri, 2 Oct 1992 01:36:43 GMT

In <1992Sep23.191837.27043@dragon.acadiau.ca> rob@dragon.acadiau.ca (Rob Hutten) writes:

>Hi.  Sorry if this has been discussed before, but I'm new to
>this gopher stuff...

>I've successfully build the client and server software on our Sun 670MP
>running SunOS 4.1.2.  Directories and text files show up as they should
>with the client software, but my script files are ignored.  F'rinstance,
>if I have this file in ~gopher:

>----begin file
>#!/bin/tcsh -f

>echo Hiya folks
>----end file

Make sure that you're running the server with the -c option.... *or*
make sure that $GOPHERHOME/bin/tcsh exists

--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | Gophermaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
Date: Thu, 1 Oct 92 15:45:03 PDT
From: chris@sdacs.ucsd.edu (Chris Frymann)
Original-To: gopher-news@boombox.micro.umn.edu
Subject: FTP Gateway - Help Please
Newsgroups: comp.infosystems.gopher
Distribution: comp

A group I have been working with has been experimenting with Gopher and trying
to
understand Gopher access to FTP archives.

We have looked at some examples of FTP links, such as:

Name=Interest Group Lists
Type=1
Port=70
Path=ftp:ftp.nisc.sri.com@netinfo/
Host=ashpool.micro.umn.edu

but have not been able to figure out what the final entry ("Host") is doing. 
 
We found the notes in the "ftp.c" source code which refer to "g2fd" but then we
lose the trail and can't seem to figure out where to pick it up.
Can anyone explain what's going on, in particular, what service is being 
provided by a host such as ashpool and how we could install it on our own local
system?

   Thanks,
      Chris Frymann