HDTenEightyP/NetNews huggingface dataset:
From: HOLTZMAN@SJUVM.BITNET ("Michael S. Holtzman")
Newsgroups: alt.gopher
Subject: CMS Server/PC Client Problem
Date: 21 Jul 92 19:09:36 GMT
Distribution: alt
Organization: St. John's University
Original-To: VM-Gopher Discussion List <vmgopher@PUCC.BITNET>,
        Gopher News List
 <gopher-news@boombox.micro.umn.edu>
X-Envelope-To: gopher-news@boombox.micro.umn.edu

Greetings. When I connect to my CMS Gopher server using the Minnesota
PC Client (Gopher II), I get a series of errors -- getDispStr Server
Returned Bad Type ID -- whenever I hit the enter key.  If I be-bop to
another server (like utah or minnesota) the problem seems to go away.
 
Is this a known problem? If so, is there a fix for it? Thanx in advance.
 
--------------------------------------------------------------------
Michael S. Holtzman      St. John's University    HOLTZMAN@SJUVM
(718) 990-1637           Perboyre Hall, Rm B14    MIKE000@SJUMUSIC
                         Jamaica, NY 11439
Newsgroups: alt.gopher
From: mathew <mathew@mantis.co.uk>
Newsgroups: alt.gopher,talk.bizarre,alt.tasteless
Subject: Re: Praying to Mecca in a Space Station
Date: Tue, 14 Jul 92 13:10:16 BST
Distribution: world
Organization: Mantis Consultants, Cambridge. UK.

ed@odin.unomaha.edu (Ed Stastny) writes:
> jle@locus.com (John Elghani/10000000) writes:
> >In article <1VXoNB12w165w@mantis.co.uk> mathew <mathew@mantis.co.uk> writes:
> >>khan@davidsys.com writes:
> >>>  When muslims start living in space stations,
> >>> they would still be able to pray towards Makkah.
> >>which rotates so as to get artificial gravity.  Fix a torch to the rim of a
> >>bicycle wheel with duct tape, spin the wheel, and watch where the torch bea
                       ^^^^^^^^^
> >>goes.
> >islam that says that you'd be incapable of praying if you were unable
> >to locate the direction of Mecca.  You can face in any direction
> >and pray then.  Therefore when in space or in different Galaxy,
> >or at the edge of the Uiverse (if any) a muslim can still face to
> 
> And why is this on GOPHER?

Did you miss the magic words?

We all know what to do with gophers and duct tape, don't we?


mathew
From: devet@wsinis01.info.win.tue.nl (Arjan de Vet)
Newsgroups: alt.gopher
Subject: Starting gopherd from crontab vs. command line problem
Keywords: gopher daemon, crontab, tty
Date: 30 Jul 92 07:47:35 GMT
Reply-To: devet@win.tue.nl (Arjan de Vet)
Organization: Eindhoven University of Technology, the Netherlands


I use the following script for starting gopherd:

#!/bin/sh
PATH=/usr/ucb:/bin:/usr/bin:/usr/exp/bin; export PATH
umask 022
# to avoid a core dump in /local/gopher start gopherd in /
cd /
# check whether another gopherd is already running!
ps aux > /tmp/$$
if (grep '^exp.*gopherd' /tmp/$$ >/dev/null)
then
  echo Gopher daemon is already running!
else
  echo Starting Gopher daemon
  gopherd -C -c -l /local/gopher/gopher.log &
fi
rm -f /tmp/$$
exit 0

I have to use this script and the -c option because I do not have root
privileges.

When I start this script from the commandline, each invocation of the daemon
gives one line in the logfile. When this script is executed from the
crontab, *each* invocation of the daemon also gives the following messages:

Not using chroot() - be careful
Data directory is /local/gopherdata
Port is 7000
Logging to File /local/gopher/gopher.log

I think this has something to do with stdin and stdout not being a
terminal. Does anybody know how to get rid of these messages? Thanks in
advance.

Arjan
From: TROTH@ricevm1.rice.edu (Rick Troth)
Newsgroups: alt.gopher
Subject: Re: CMS Server/PC Client Problem
Date: 28 Jul 92 19:41:44 GMT
Distribution: alt
Original-To: "Michael S. Holtzman" <HOLTZMAN%SJUVM.BITNET@ricevm1.rice.edu>,
        VM GOPHER discussion list <VMGOPHER%PUCC.BITNET@ricevm1.rice.edu>,
        gopher-news@boombox.micro.umn.edu

On Tue, 21 Jul 1992 15:09:36 EDT you said:
>Greetings. When I connect to my CMS Gopher server using the Minnesota
>PC Client (Gopher II), I get a series of errors -- getDispStr Server
>Returned Bad Type ID -- whenever I hit the enter key.

        I've never gotten this error  (using the MSU modified Gopher II).
But I *did* find that the client would  "just hang"  on the CMS server.
It's not now,  probably because I cleaned-up the appendage of the
CR/LF/dot/CR/LF sequence.

        Also,  I never mentioned to  gopher-news  that the Rice CMS
client and server  v2r3  is now available.   Get it from Brazos.IS.Rice.EDU
in the directory  /pub/vmcms/gopher23.

Rick Troth <TROTH@RICEVM1.RICE.EDU>, Rice University, I/S VM Systems Support
Newsgroups: alt.gopher
From: mtm@camis.Stanford.EDU (Mike Macgirvin)
Subject: Re: problems with gopherd under inetd
Organization: DSO, Stanford University
Date: 27 Jul 92 17:35:16 GMT

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:


	Under SunOS.4.1.1 and earlier (not sure about later, but I
would guess it's still that way) you can only have !5! maximum
arguments in inetd.conf for a process (not counting arg0). This
applies to many other OS's as well. Either you will have to scrunch
down your arguments by using defaults where possible (stick the option
letters together and use the hardwired directory and port), or you can
pick up "munetd" from your favorite archive source, which uses the
latest Berkeley inetd code, and also works with Sun's RPC services. It
allows 20 args per command. Don't use the Berkeley Net-2 inetd off the
shelf because it doesn't have the RPC hacks.


"mike" (Mike Macgirvin)         M_Macgirvin@MED.Stanford.EDU
Unix Server Administrator       SUMEX-AIM|CAMIS Computer Project
From: devet@wsinis01.info.win.tue.nl (Arjan de Vet)
Newsgroups: alt.gopher
Subject: Re: Is Less Really More?
Date: 22 Jul 92 20:45:31 GMT
Reply-To: devet@info.win.tue.nl
Followup-To: alt.gopher
Distribution: alt
Organization: Eindhoven University of Technology, the Netherlands

In article <9207221650.AA25931@boombox.micro.umn.edu>
BDESIMON@uga.cc.uga.edu (bert desimone) 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..).

From the less(1) manual page:

     -r   Causes "raw" control characters to be  displayed.   The
          default  is  to  display  control  characters using the
          caret notation; for example, a control-A (octal 001) is
          displayed  as "^A".  Warning: when the -r flag is used,
          less cannot keep track of the actual appearance of  the
          screen  (since  this depends on how the screen responds
          to each type  of  control  character).   Thus,  various
          display  problems  may result, such as long lines being
          split in the wrong place.

So do setenv LESS "-r" or from within less `-r'. This will display
highlighted characters (if your terminal has this possibility). The display
problems mentioned in the manual page are sometimes really annoying.

Arjan
From: gerland@ubvmsb.cc.buffalo.edu (Jim Gerland)
Newsgroups: alt.gopher
Subject: Re: VMS Client Help File
Keywords: gopher help
Date: 30 Jul 92 16:30:07 GMT
Reply-To: gerland@ubvmsb.cc.buffalo.edu
Organization: University at Buffalo


In article <1992Jul29.194306.13548@uvm.edu>, jmc@newton.emba.uvm.edu.uvm.edu (John
Connors) writes:
>If you someone could be so kind as to direct me to a help file suitable
>for the VMS gopher client?  Or mail it to me?   People type 'h' and 
>get a file not found error.  

Here's the file GOPHER.HELP that I think comes with the GOPHER for VMS
package and is pointed to by the logical GOPHERHELP :

--------begin gopher.help---------------------

     Keystroke  Action
     =========  ====================================================
     <RETURN>   Read current selection
     u or U     Go back one menu level
     s          Save current selection to a file
     q or Q     Quit and return to VMS
     O          Change program options
     ?          Display help file 

-------------end gopher.help-------------------

and here's the GOPHER.RNH file I quickly created for our local HELP
entry:

-----------begin gopher.rnh--------------------

.noflags
.lm 1
.rm 75
.i-1;1 gopher
.br
gopher is a VMS client that provides a way to access Internet available
information.
.br
.i-1;2 Setup
.br
To use gopher, you must first either type:
.bl
.i+5;SETUP gopher
.bl
at the VMS $ prompt, or put the following line in your LOGIN.COM file:
.bl
.i+5;$ SETUP gopher /QUIET
.br
.i-1;2 Usage
.br
You invoke gopher entering the command:
.bl
.i+5;gopher[ host.domain.net port]
.bl
If you the host and port, gopher will connect to the default gopher server.
.br
.i-1;2 Author
.br
Mark Van Overbeke
.br
Systems Software Programmer
.br
Behmler Hall, Room 10C
.br
E. 4th Street and College Ave.
.br
University of Minnesota, Morris
.br
Morris, MN   56267
.br
(612) 589-6378
.br
Mark@caa.mrs.umn.edu (VMS)
.br

-------------end gopher.rnh-----------------

Hope this helps.
Jim...
Newsgroups: alt.gopher
From: urle@rz.uni-karlsruhe.de (Uli Betzler (urle))
Subject: Re: Conversion Confusion!
Organization: University of Karlsruhe, Germany
Date: Wed, 22 Jul 1992 06:13:58 GMT

In article <1992Jul21.170142.26998@mercury.unt.edu>, billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager) writes:
|> 
|> 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.

We use Gopher with chroot and simulate via symlinks the full path of our
wais-indexes relative to the new root. This works very fine and leaves
security untouched.

urle

-- 
Ulrich Betzler                             smtp:   urle@rz.uni-karlsruhe.de
Universitaet Karlsruhe                     bitnet: rz83 at DKAUNI2
Rechenzentrum
Zirkel 2                                   X.500:  cn=Ulrich Betzler
7500 Karlsruhe 1                                   ou=Rechenzentrum
FRG                                                o=Uni-Karlsruhe
                                                   c=DE
phone: +49 721 608-4039                                       
Newsgroups: alt.gopher
From: sendall@dxpt01.cern.ch (Mike Sendall)
Subject: Re: index for all of gopherspace
Reply-To: sendall@dxcern.cern.ch
Organization: CERN (European Laboratory for Particle Physics)
Date: Tue, 28 Jul 1992 07:46:14 GMT


In article <1992Jul27.201122.17017@msuinfo.cl.msu.edu>, boone@convex.cl.msu.edu (Dennis Boone) writes:
|>
|>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.
|>
This only partly works out for WAIS. Unfortunately not all servers put
enough useful information in the description field of their WAIS source. 
So the Directory of Servers isn't always able to identify useful sources
in response to user queries. Still, it certainly helps, and with a bit more 
effort on the part of people setting up servers it could be better still.
Newsgroups: alt.gopher
From: mtm@camis.Stanford.EDU (Mike Macgirvin)
Subject: Re: Gopher and Hypertext links
Keywords: hypertext
Organization: DSO, Stanford University
Distribution: alt
Date: 23 Jul 92 17:00:49 GMT

rww@mugwump.cl.msu.edu (Richard W. Wiggins) writes:

>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?

	It's there, an HTML hyper client in the 1.01 gopher client
release. Only problem is, it doesn't quite work as advertised yet
(well, to be fair, it wasn't advertised.)

mike
Newsgroups: alt.gopher
From: emv@msen.com (Edward Vielmetti)
Newsgroups: alt.gopher
Subject: Announcing: A Tk browser to the World Wide Web 0.1 (ALPHA TEST)
Date: 27 Jul 1992 10:12:22 -0400
Organization: Msen, Inc. -- Ann Arbor, Michigan
Reply-To: joe@athena.mit.edu
NNTP-Posting-Host: nigel.msen.com
X-Newsreader: Tin 1.1 PL3

you may have seen this on one of the other groups which this was posted
on, but just in case it's here too.  --Ed

[ Article crossposted from comp.lang.tcl,alt.hypertext,comp.windows.x,comp.lang.sgml ]
[ Author was joe@athena.mit.edu ]

ANNOUNCING:
tkWWW 0.1 Alpha
by Joseph Wang (joe@athena.mit.edu)

A Tk interface to World Wide Web (ALPHA TEST)

WHAT IS IT?
-----------
World Wide Web (WWW) is a hypertext project which seeks to build a
world wide network of hypertext links.  There are several different
browsers for this system including a simple tty interface.

Tk is an interpreted toolkit which allows one to build X11 applications
quickly and easily.

tkWWW is a Tk interface to (WWW).

WHY ANOTHER WWW BROWSER?
------------------------
This Tk browser has two significant advantages.

1. Since it is written in a interpreted language, it is very easy to make
modifications and extensions to it.

2. More importantly, tkWWW uses the "Hyper" widget of the Tk toolkit.
This "Hyper" widget allows one to emmbed Tk applications in the
hypertext, allowing such things as graphics and animation. 

WHERE IS IT?
------------
export.lcs.mit.edu:/contrib/tkWWW-0.1.tar.Z

Copies have been uploaded to the WWW archive at info.cern.ch and the Tcl
archive at barkley.berkeley.edu.  They should be available shortly.


WHAT DO I NEED TO INSTALL IT?
-----------------------------
In order to install tkWWW you will need

   The code for the WWW line-mode browser. (anon ftp from info.cern.ch)
   Libraries for tk and tcl (I'm using tk2.1 and tcl6.3)

   A wish intepreter which contains the Hyper and XYGraph widgets

   A reasonable knowledge of UNIX and wish is needed as this is
   alpha test software.

To install this program, unpack the WWW line-mode browser source and 
cd to the directory $(top-dir)/WWW.  Unpack the tkWWW tar file. 

When you have got the thing running (or it fails to install), e-mail
me to let me know how it turned out.

WHAT'S THE CATCH?
-----------------
The catch is that this is very, very buggy software that was cobbled
together in three days of frantic hacking.  Use it at your own risk.

One of the non-obvious bugs is that if the browser exits abnormally it
will leave a dead process called "tkWWW" that will have to be killed
manually.

Comments, suggestions, and code modification are always appreciated.

ENJOY........
Date: Wed, 22 Jul 92 12:20:38 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: how to unsubscribe from gopher news
Newsgroups: alt.gopher
Distribution: alt

It seems like I send this message out about once a month. 
It appears to be time again...

If you want to unsubscribe from gopher-news, please send your request to 
gopher-news-request@boombox.micro.umn.edu rather than to the entire mailing
list. There are over 400 recipients of gopher news, and they probably don't 
really want to read your un-subscribe requests. 

So.. please send all your subscribe/unsubscribe request to 
       gopher-news-request@boombox.micro.umn.edu


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)
Date: Wed, 22 Jul 92 16:18:56 PDT
From: mmansell@nero.UVic.CA (Mike  Mansell)
Original-To: gopher-news@boombox.micro.umn.edu, news@nero.UVic.CA
Subject: RE:  Gopher and Hypertext links
Newsgroups: alt.gopher
Distribution: alt


	There is also a gopher client/server pair with linking capability
This is available from from me. The only client currently supporting this
is the Unix XClient, however the Unix curses client will be ready very soon.
Both the client and server will be uploaded to boombox in the near future
(when I get some time to organize things). Until then, if you want more
information, drop me some e-mail at mmansell@nero.UVic.CA

Here's an exerpt from some of our Gopher documentation:

I. Gopher

Gopher is a platform independent information handling and retrevial system.
Gopher is a server/client system.

I.I The server

The server resides on a networked computer and handles all requests
from any client on another computer. The server located at the
University of Victoria is based on the v1.01 release of the Unix server. An
enhancement has been made by David Manning (dmanning@nero.UVic.CA) to
provide graphics support (GIF is the only graphics protocal currently
implemented). 

There is a Mac-based server available. However, there are none currently
operating within the University of Victoria.

I.II The client

The client is a program that connects to the server and sends and receives
information based on user requests. There are currently clients available
for all major platforms, including Mac, IBM, NeXT, Sun/Unix and VMS. The
Sun/Unix client is available for a curses environment and an X window
environment. The Sun/Unix clients at the University are based on the
v1.01 release of the curses client and the v1.1 release of the X window
client. Several enhancements have been made by David Manning and
Michael Mansell (mmansell@nero.UVic.CA) to the X window client. These
enhancements provide graphics support (GIF only) and cross-referencing.
A completely new client is being written to interact with the multimedia
hypertext project currently in progress. This client is command-line
driven to provide a silent and automatic mechanism to access the gopher
databases.

Michael C. Mansell
mmansell@nero.UVic.CA
Faculty of Fine Arts
University of Victoria
Newsgroups: alt.gopher
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: Re: Executing other applications through gopher
Organization: Draper Laboratory
Date: Fri, 31 Jul 1992 13:07:00 GMT

In article <1992Jul30.190406.22304@msuinfo.cl.msu.edu>,
schafers@cps.msu.edu.cps.msu.edu (Steven R Schafer) writes:

>I was wondering if it is possible, and if so how would you do it, to run
>another application from gopher.  Let's say wais or www, maybe by using
>exec in a .link file or something similar.

From the man page for gopherd:

     Another neat thing you can do is to execute commands:

         Name=Execed command name
         Type={a type}
         Path=exec:"args":/scriptname
         Host=+
         Path=+

     This is usually used by other types of gateway scripts.  For
     instance, The first script might take a search and get a few
     hits.  It could then  generate  "exec"  scripts  that  would
     retrieve the actual document the hit referred to.

(end of man page extract)

Note that the args precede the shell script name.

Also, if the file in a directory being served by gopher is an
executable shell script, the gopher server will automatically
execute that shell script.  (Watch out for this "feature"!)
Unfortunately, it seems that gopherd currently checks this by
looking for "#!/bin/<shellutilityname>" instead of checking
the permissions of the file.

When a shell script is executed, the standard output from the
execution becomes the gopher data returned to the client.
(The standard error is also returned to the client, and it
tends to be mixed in with the standard output, which can be
a problem.)  If the menu entry is requesting a directory,
the script should write lines of the form

<type><name><tab><path><tab><host><tab><port>

so that the client will be able to interpret them as gopher
directory entries.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Date: Wed, 22 Jul 92 16:24:57 PDT
From: dmanning@nero.UVic.CA (David  Manning)
Original-To: gopher-news@boombox.micro.umn.edu
Subject: Re: Gopher and Hypertext links
Newsgroups: alt.gopher
Distribution: alt

Brad,

	We are using a simple set of modifications to "link" text files to
other text files, sound files, image files, etc... As this is still a fairly
serious hack we have not made it available to the public. 

	If you are interested, however, we can push a copy up to boombox. For that matter, if anyone is interested this could be done.



					Cheers,

					Dave Manning
From: gilbertd@sunflower.bio.indiana.edu (Don Gilbert)
Newsgroups: alt.gopher
Subject: Re: Gopher Type 6 ???
Date: 21 Jul 92 12:34:43 GMT
Article-I.D.: usenet.Brqo9v.5D6
Organization: Biology, Indiana University - Bloomington

Type 6 is not a new type, it was assigned for UU encoded files
a while back.  It seems to have been dropped from release 1.0,
but I missed noticing that.  The reason that uuencoded type
is in this patch, which I wrote, is that on my archive, there
are lots of encoded files, including binhex (mac) and uuencoded
(pc, unix, vms).  I generally do not know, nor does the server
computer know, what is inside these uuencoded files.  So it
is hard to assign them as text or binary.  However, uuencoded
files could be treated as text type, if no one else wants
to support type 6.   

-- Don
-- 
Don Gilbert                                     gilbert@bio.indiana.edu
biocomputing office, biology dept., indiana univ., bloomington, in 47405
Newsgroups: alt.gopher