HDTenEightyP/NetNews huggingface dataset:
From: gilbertd@sunflower.bio.indiana.edu (Don Gilbert)
Subject: Re: GIF standard and textmarkup question
Organization: Biology, Indiana University - Bloomington
Date: Fri, 20 Nov 1992 16:58:42 GMT

The current gopher protocol does nominally support images
with its "I" image type.  However it doesn't deal with messy
details of *which* image type (perhaps gif by most common usage).
Nor does the current gopher protocol provide for multiple formats
for a given document, like rtf, postscript, text, etc.

But, the new, improved Gopher+ protocol does deal with these
issues.  You can pick up docs on this protocol via gopher to
gopher.micro.umn.edu.   

My perhaps imperfect understanding of Gopher+ is that a server
can provide multiple formats for a document by advertising
it as a text type '0' as per current gopher protocol, then
provide additional info to any smart gopher+ clients in a
+VIEWS field, which will enumerate the formats it can provide.
For images, the server advertises the 'I' type, then provides
further VIEWS information on just which image type(s) it
can provide.
 
The Gopher+ protocol document lists the following types:

Text, List (== folder),
Postscript, Gif, Pict, Pict2, Tiff

Also it says there will be a Gopher Registry which
lists all current registered types that servers and clients
may handle.  This looks to be an open ended list,
so you can add types you think are important.

I am planning to support RTF heavily thru my server and client.
This will provide fully formatted text, and maybe images, for
our scientific needs.

RTF (rich text format, originated by Microsoft) is already supported
by the common wordprocessors that many (most?) computer users use:
Microsoft Word (MS Windows, Mac), WordPerfect (MS WIndows, Mac, Unix),
WriteNow (Mac, NeXT, others?), and probably others.  As well there are
unix/c utilities for translating to/from RTF (troff/rtf, TeX?/rtf,
text/rtf).  See especially Paul DuBois' translators at 
ftp.primate.wisc.edu.

-- Don
-- 
Don Gilbert                                     gilbert@bio.indiana.edu
biocomputing office, biology dept., indiana univ., bloomington, in 47405
Newsgroups: comp.infosystems.gopher
From: silvert@cs.dal.ca (Bill Silvert)
Subject: Gophers by subject (was New gopher at Univ of Utah)
Reply-To: silvert@biome.bio.ns.ca (Bill Silvert)
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Date: Wed, 18 Nov 1992 13:57:59 GMT

In <1992Nov18.093748.19598@nic.funet.fi> harper@convex.csc.FI (Rob Harper) writes:

>Put in this link to you gopher and it might be of some help.

>Name=Geography and Oceanography
>Type=1
>Port=70
>Path=1/Subject Tree/Geography and Oceanography
>Host=sunic.sunet.se

>Here is what you get when you login as oceanic.

>                            Welcome to
>                          O C E A N I C
>                    The OCEAN Information Center

>                    Created and Maintained by

>                    The University of Delaware
>                    College of Marine Studies
>                        Lewes, Delaware

This actually generates two telnet connections to:

#
Name=Geographic Server
Type=8
Port=3000
Path=
Host=martini.eecs.umich.edu
#
Name=The Ocean Information Center
Type=8
Port=23
Path=OCEANIC
Host=delocn.udel.edu
#

which might be more efficient for NA users than gophering to Sweden.

Thanks for the tip.
-- 
William Silvert, Habitat Ecology Division, Bedford Inst. of Oceanography
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2.  Tel. (902)426-1577
InterNet Address: silvert@biome.bio.ns.ca
Newsgroups: comp.infosystems.gopher
From: john@math.nwu.edu (John Franks)
Subject: Re: GIF standard and textmarkup question
Reply-To: john@math.nwu.edu
Organization: Dept of Math, Northwestern Univ
Date: Fri, 20 Nov 1992 19:58:48 GMT

In article <By0xtu.C1z@usenet.ucs.indiana.edu>, gilbertd@sunflower.bio.indiana.edu (Don Gilbert) writes:
> The Gopher+ protocol document lists the following types:
> 
> Text, List (== folder),
> Postscript, Gif, Pict, Pict2, Tiff
> 
> Also it says there will be a Gopher Registry which
> lists all current registered types that servers and clients
> may handle.  This looks to be an open ended list,
> so you can add types you think are important.
> 
> Don Gilbert                                     gilbert@bio.indiana.edu
> biocomputing office, biology dept., indiana univ., bloomington, in 47405


I sure hope that DVI (the TeX device independent file format) gets on
the registered list.  There are a lot of documents out there in TeX and
there are pretty good dvi previewers for X, Mac and PC.  Also the
.dvi format doesn't have the security problems of Postscript.  I have
tried this format experimentally under gopher1.03 with xgopher 
(+ unauthorized patch) and with the Don Gilbert's Mac client.  It works
fine.

-- 

John Franks 	Dept of Math. Northwestern University
		john@math.nwu.edu

Newsgroups: comp.infosystems.gopher
From: ian@apex.ucs.sfu.ca (Ian Reddy)
Subject: GREPTYPE in the gopherd code
Keywords: grep
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Wed, 18 Nov 1992 04:49:41 GMT

Looking through the UNIX gopher1.03 code I found an index type called
"GREPTYPE". I haven't been able to configure this successfully. Does  
anyone know how to make the GREPTYPE work?

Also, how does one configure a script of type 7 that will return plain
text rather than another menu level?

--
  Ian Reddy, Senior Systems Consultant  E-mail:    Ian_Reddy@sfu.ca
  Academic Computing Services, AD1021              ian@sfu.ca
  Simon Fraser University               Telephone: (604) 291-3936
  Burnaby, B.C. Canada V5A 1S6          Fax:       (604) 291-4242
Newsgroups: comp.infosystems.gopher
From: ewilts@galaxy.gov.bc.ca (Ed Wilts)
Newsgroups: comp.infosystems.gopher
Subject: Re: Xgopher port for VMS ?
Date: 17 Nov 92 12:04:35 -0800
Reply-To: EWILTS@GALAXY.GOV.BC.CA
Organization: BC Systems Corporation

In article <4250@sicsun.epfl.ch>, marmillod@elpp1.epfl.ch (Philippe Marmillod EPFL - CRPP 1015 Lausanne CH) writes:
> 
>   Has anyone else already gotten xgopher (or an equivalent) working under
>  VMS that could email me diffs or point me towards an ftp site ??

David Jones from Ohio State University has already ported xgopher for UCX.  By
including one of the UCX header files, I got it to work under MultiNet as well. 
Unfortunately, I can't remember the site I pulled the sources from...  If you
need them, and are running UCX, let me know and I can e-mail you the sources. 
I can't distribute the UCX include file for MultiNet sites so please don't ask.

-- 

Ed Wilts, BC Systems Corp., 4000 Seymour Place, Victoria, B.C., Canada, V8X 4S8
EWilts@Galaxy.Gov.BC.CA     Office:  (604) 389-3430    Fax: (604) 389-3412
Newsgroups: comp.infosystems.gopher
From: daniel@vcp1.vcp.monash.edu.au
Subject: How to find new gopher databases.
Organization: 
Date: Thu, 19 Nov 1992 08:47:01 GMT


Someone mentioned the difficulty of finding new gopher servers
and databases.

Perhaps the solution would be to do what think.com did with
WAIS.  Someone (umn.edu?) maintains a master databasse of
gopher indexes with their contents keyworded.  This could be
a wais style index, searchable by a wais interface on a gopher
client.

The master index could be shadowed and updated weekly, or nightly
or whatever, in the same way that plaza.aarnet.edu.au maintains
a shadow of think.com's directory-of-sources for wais.

The success of this would rely on databases which are gopherable
being 'published' i.e. their whereabouts being made known to the world,
just as wais-sources


                       are published by being registered with
think.com.

As was pointed out, the number of databases discoverable by gopher
is quickly going to exceed a human's ability to look for them. 
A keyword index a la wais is going to be necessary sometime.

Danny

Newsgroups: comp.infosystems.gopher
From: dan@engr.latech.edu (Daniel Len Schales)
Subject: Re: Help with execing shell scripts
Organization: Louisiana Tech University
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 16 Nov 1992 14:46:53 GMT

Mark Whidby (zlsiimw@mcchpc.mcc.ac.uk) wrote:
: In article <1992Nov12.193642.12411@engr.latech.edu>, dan@engr.latech.edu (Daniel
: Len Schales) writes:
: <stuff deleted>
: |> Name=misc
: |> Type=1
: |> Port=70
: |> Path=exec:-g misc:/bin/gonntp
: |> Host=aurora.latech.edu
: <stuff deleted>
: |> 
: |> The main thing is to make sure everything is in the gopherdir,
: |> you may want to try running gopherd non-chroot() to test things
: |> out. But it does work, I have dozens and dozens of shell links
: |> in my gopherspace.
: 
: Well I've started playing with gonntp today - it's fun. But I'm running
: with -c (don't tell anybody!!). However, I find that I need to put gonntp
: in the bin directory in the gopherhome. I haven't got anything else there
: (perl for example). Anybody understand this? (I'm running the beta 1.1
: version BTW).
: -- 
: _____________________________________________________________
: Mark Whidby, Distributed Systems, Manchester Computing Centre


Having never run non-chroot() I'd never noticed this, but apparantly
gopherd prepends the gopher-home directory to the path if you
are running non-chroot(). See special.c in the gopherd source.

Danny
Date: Mon, 23 Nov 92 12:08:45 EST
From: BBABCOC@american.edu (Barbara Babcock)
Organization: The American University
Subject: CMS Gopher
Original-To: gopher-news@boombox.micro.umn.edu
Newsgroups: comp.infosystems.gopher
Distribution: comp

Hello.

Is anyone else out there using CMS Gopher?  The "Find a String" doesn't seem to
work.  I am also wondering if it is possible to find out the computer on which
the information resides in CMS Gopher.  So far I haven't been able to do that
either.  If anyone can help me, please do.  Thank you very much.

Sincerely,
Barbara Babcock
E-Mail Address:  bbabcoc@american.edu
The American University, Washington D.C.
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: execing shell scripts
Organization: University of Minnesota, Minneapolis
Date: Tue, 17 Nov 1992 06:49:39 GMT

In <1992Nov16.181914.29310@trentu.ca> ccksb@trentu.ca (Ken Brown) writes:

>I can see how to set up the link file to run a script from gopher.  What
>I gather is that in the gopher data directory there must exist
>directories which contain the script/programs desired.  If this is so
>and I want to run a csh script called `testme' and chroot is used (the
>default) then testme and csh must reside in the gopher tree.  If the
>gopher data directory is /usr/local/gopherdata and the script starts
>#!/bin/csh then I take it the gopher tree must appear like so;

>/usr/local/gopherdata
>	|
>	bin

>and in /usr/local/gopherdata/bin we must have csh and the script testme.

>If this is so, how do I stop bin from being seen by clients as a
>directory entry in the top level?  After all, /usr/local/gopherdata
>contains other entries I wish to display but I don't wnat to display the
>bin dir.

bin is one of those magic directories that automatically get ignored
by the unix server.  Try it, you'll like it.
--
 | 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: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: unix gopherd -s and -l don't work togeather
Organization: University of Minnesota, Minneapolis
Date: Tue, 17 Nov 1992 07:02:58 GMT

In <BxtyKC.B39@uxa.ecn.bgu.edu> xcea@uxa.ecn.bgu.edu (Chad Adams) writes:

>I am tring to use the following in inetd.conf on SunOS 4.1.2 and it does
>not work:  (line split up to into 80 column chunks to put in article)

>gopher stream tcp nowait root /usr/local/etc/gopherd gopherd -I
>-s/home/uxa/xgopher/public_access -l/home/uxa/xgopher/log/public -uxgopher
>/home/uxa/xgopher/gopher-public 70

>It can't access the main menu.  If I take out the -s or the -l it works.
>We need to use both -s and -l.

>We are useing the gopherd from gopher1.03.

SunOS is really braindamaged in that it only allows four real
parameters to an inetd.conf entry.  You can do one of two things:

remove paramaters (not possible in your case..)

Or make a shellscript "wrapper"

#!/bin/sh
gopherd -l moo -s goo -I -c etc etc 70

Then you execute the wrapper instead of the actual program..
--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | Gophermaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
Newsgroups: comp.infosystems.gopher
Subject: Problems with ftp on HP gopher
Date: 19 Nov 92 15:43:30 GMT
Reply-To: M.Whidby@mcc.ac.uk
Organization: Manchester Computing Centre

I am running a gopher server on an HP machine and can't do any ftp
transfers. I have a link file containing the following:

Name=Imperial College ftp
Type=1
Path=ftp:src.doc.ic.ac.uk@/
Port=+
Host=+

This seems to be more or less correct because when I run the server with
debugging on I see this:

The full query was src.doc.ic.ac.uk@/
At this point host: src.doc.ic.ac.uk   thing: /
220 puffin.doc.ic.ac.uk FTP server (Version 6.68 Fri Aug 21 23:39:26 BST 1992)
r
eady.
331 Guest login ok, send e-mail address as password.
230 Guest login ok, access restrictions apply.
Cleaning up /tmp/gftp11012

The client just says 'Nothing available'. No directory listing or anything.
What am I doing wrong? The server is the 1.1 beta version. Could it be a
peculiarity of HP-UX?
-- 
_____________________________________________________________
Mark Whidby, Distributed Systems, Manchester Computing Centre
Date: Wed, 18 Nov 92 12:02:09 PST
From: kdb@ece.ucsb.edu (Kevin D. Barron)
Original-To: foster@cs.unr.edu
Subject: Re: veronica
Original-Cc: gopher-news@boombox.micro.umn.edu
Newsgroups: comp.infosystems.gopher
Distribution: comp

Steve,
 I'm hoping that today's announcement re. veronica was not what you
 meant when you said:

>
>Yes, I am working on writeup.  will post soon.
>

What I had in mind was something detailing the setup and administration of
veronica.  I can't commit at this point, but I would be interested in finding
out how much disk space you are currently using and how much is projected 
once a "distributed" veronica is arranged (a la Archie).

Here's my two cents worth:  we need to distribute the indexing task not simply
over numerous hosts (to spread the load) but also by establishing authoritative
sites for specific subjects.  It occurs to me as I write this that perhaps the
most efficient means to accomplish this would be to have a two-tiered system:
1. top-level veronicas act as subject indexers (taking you to the authoritative
   site).
2. the second tier also has veronica which takes you to specific resources
   (or breaks it down into finer detail)

- as I write this, Bill Silvert's msg came in suggesting practically the same
thing! (so I'll cc to the list)

What I mean by "authoritative site" is simply a site which is willing to provide
links and preferably veronica-searches of similar-subject sites.  This is 
similar to what Bill called "master gophers" - however, I think we need master
gophers to point to the authoritative gophers (eg how do you find all the BIO
gophers).

Hopefully we can find a way to filter out local-only information (a gopher+ 
attribute?).

Kevin
From: kaufman@macc.wisc.edu (Peter Kaufman)
Newsgroups: comp.infosystems.gopher
Subject: Applying Vulcan Mind-Meld on a Gopher...
Date: 17 Nov 92 15:47:23 GMT
Organization: Madison Academic Computing Center - Univ. WI
X-Useragent: Nuntius v1.1b1

Greetings,

On our campus we have six 'production' gopher servers and several 
others in the works by various departments on campus using NeXTs and 
Sun workstations. In order to avoid reinventing the wheel, I plan to 
offer a workshop on setting up a gopher server. As I've begun this 
endeavor of teaching the "Gopher Mindset," I've come to the 
realization that the best way to set up a server is counterintuitive 
to the seemingly simplistic nature of the system.

A first start would be simply creating a subdirectory tree structure 
containing files of similar nature, where subdirectory names describe 
the contents within. Then, run the server, publishing the root level 
of the structure. This method has several inadequacies.

Assumptions:
1) In order to create special chars (such as in "I/O") in filenames or 
extra long filenames, one needs either a .links or .caps file.
2) To specify the order in which the files are listed in a directory, 
one needs to specify the Numb=x in the .links file. The default now 
appears to be alphabetical by filename.
3) Assumptions 1) & 2) require the files be hidden. This same control 
applies to subdirectory names as well and hence those are also hidden.

Thus, we have a subdirectory structure with hidden files with the 
.links file portraying the view for the client. Is this good?

I've heard that the tape/disk backup utility, tar,  can fail on long 
paths and filenames (not to mention they are a pain to deal with in 
general).

So, since .links are actually pointing to where the data file is 
anyway with the Path= stmt, why not simply point back to the root to a 
short (hidden) subdir name with short data file names. In this case 
there would be some algorithm determining the filename (eg. 
NEWSYYMMDD. for a newsletter on that date), with likely an associated 
data file specifying the mapping between long text titles for 
documents and the abbreviated names.

Hence, the Gopher Mindset I would recommend is to create the 
subdirectory structure, load it with .link files and put all the data 
files off the root.

Comments or suggestions?

Peter


____________________________________________________________________
Peter Kaufman        Univ. of WI - Madison Academic Computing Center
608/262-8623         1210 West Dayton St.  Madison, WI  53706
Kaufman@MACC.Wisc.Edu   Kaufman@Wiscmacc   70302.3410@Compuserve.Com
____________________________________________________________________
From: mckay@mcmail.cis.mcmaster.ca (Muriel McKay)
Newsgroups: comp.infosystems.gopher
Subject: Using mail to provide gopher data
Date: 18 Nov 92 19:50:39 GMT
Reply-To: Muriel McKay <mckay@mcmail.cis.mcmaster.ca>
Distribution: comp
Original-Cc: gopher-news@boombox.micro.umn.edu


I remember reading a while ago that it was possible to send mail to a
Gopher server and have it display as a menu item . I don't remember how it
was done. Does anyone have instructions and has anyone tried it with
listserv's?

Any information gratefully received. 

===============================================================================
Muriel McKay,
Consultant, Office Systems Support.
CIS.  ABB132 ext 7090
McMaster University , Hamilton, Ontario, Cananda.
Newsgroups: comp.infosystems.gopher
From: Tony Euser <euser@emr.ca>
Subject: Date and time stamps
X-Xxmessage-Id: <A732B4692E012C0B@maceuser.emr.ca>
X-Xxdate: Fri, 20 Nov 92 20:27:37 GMT
Organization: Energy, Mines & Resources-Canada
X-Useragent: Nuntius v1.1.1d12
Date: Fri, 20 Nov 1992 20:27:29 GMT

Having tried both GopherApp and TurboGopher, it seems that none of the
servers post date and time stamps, even though GopherApp does have a
check box to enable sensing it (if it's there).
Is this a feature enabled at the server end?  It would sure save time
when gopher hunting in version territory.   Fetch or any of the FTP apps
report these stamps so why not gopher.
From: cshotton@oac.hsc.uth.tmc.edu (Chuck Shotton)
Newsgroups: comp.infosystems.gopher
Subject: Gopher's built-in WAIS search bug?
Date: 16 Nov 1992 21:27:12 GMT
Followup-To: comp.infosystems.gopher
Organization: Academic Computing

I've run across a problem using gopher's built-in support for
"understanding" WAIS .src files. We have several WAIS sources available
through gopher. Until recently, access to these sources was through the old
Gopher->WAIS gateway. When gopher 1.03 came along with built-in WAIS
support for .src files in a gopher dir, we switched over. 

It now appears that gopherd really munges the data when it returns it to
the gopher client. Titles of entries in a WAIS source which used to be
simple one or 2 word titles (on the first line of a document indexed as
"para") now consist of all the text in a particular WAIS search result
that'll fit on one line in the gopher client's list. 

For example, a WAIS query that would normally return the following info
(using the gopher->WAIS gateway):

Index word(s) to search for: SPAM

1. SPAM - A meat product

<select 1>

SPAM - A meat product
SPAM is one of the modern wonders of the world.
It comes in two colors.....

gopherd 1.03 returns the same info in the following form:

Index word(s) to search for: SPAM

1. SPAM - A meat product SPAM is one of the modern wonders of the world. It
com

<select 1>

SPAM - A meat product SPAM is one of the modern wonders of the world. It
comes in two colors.....

In other words, it appears as if all carraige control info is totally
ignored. When the same data is accessed via the old WAIS gateway, all
clients seem to work just fine but every widely available client chokes
when the built-in .src support of gopherd is used.

This must be a known "feature" of gopherd 1.03's support for .src files. Is
there a work-around or patch to fix the problem?

--_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Chuck Shotton                      |    
Ass't Director, Academic Computing |       "This space for rent."
UT Health Science Center Houston   |  
cshotton@oac.hsc.uth.tmc.edu       |         
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Date: Wed, 18 Nov 92 15:15:55 CST
From: elenwall@chemdept.chem.uoknor.edu ("Eric Enwall" )
Original-To: gopher-news@boombox.micro.umn.edu
Subject: Re: Veronica:  an Archie for Gopher
Newsgroups: comp.infosystems.gopher
Distribution: comp

In agreement with Bill Silvert, Veronica is a step forward, but of course will 
need refinement. My example, a search on ERIC (obviously interested in access to
the ERIC database) one gets a large number of hits which I believe are in fact
hits on 'pointers' to the same WAIS search engine (site?). How this can be 
filtered I can't propose, but it seriously limits the present utility of 
Veronica. Filtering of duplicate pointers to 'other gophers' should be 
relatively easy to do.

Eric Enwall
                                       snail mail
internet  Eric-Enwall@uoknor.edu       Department of Chemistry and Biochemistry
bitnet    enwall@uokucsvx              University of Oklahoma
                                       Norman, OK  73019-0370

Newsgroups: comp.infosystems.gopher
From: zbig@wariat.org (Zbigniew J. Tyrlik)
Subject: gopher 1.03 client on Sys V (ISC 3.0)
Organization: Akademia Pana Kleksa, Public Access Uni* Site
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 16 Nov 1992 01:56:55 GMT


Hi folks, 

We are trying to compile gopher client for ISC 3.0 - SYSV. 
So far, heck lot of undefined symbols. If someone has compiled
client under ISC, I would love to hear from you....


_zjt
-- 
********************************************************************
Zbigniew J. Tyrlik       DoD# 0759   VF700C '84      zbig@wariat.org
IBM PC SIG Sysop - Cleveland Free-Net    aa609@cleveland.freenet.edu
APK	       Public Access UNI* Cleveland,          (216)-481-9436
Feeds, shell, FTP & telnet access        Uniboard distribution point 
********************************************************************
Newsgroups: comp.infosystems.gopher