Message-ID: <3C671600.F5C64FAF@sympatico.ca>
Date: Sun, 10 Feb 2002 19:53:20 -0500
From: Ralph Furmaniak <sugaku@sympatico.ca>
MIME-Version: 1.0
To: gopher@complete.org
Subject: [gopher] Re: Creating new Gopherholes?
References: <000c01c1b268$72b51ee0$15d7fea9@cc.umanitoba.ca>
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


There is also the bucktooth server, which I recently extended.  It is written in
perl and so should work in windows, but currently you would need a port of inetd.  I
can fix things up so that it does not require this, if anyone is interested.  Does
anyone here know how to work with windows services, or would putting it in autoexec
suffice?

The format for setting up a gopherhole (first time I heard this word) is different
here.  You can see it at the example on my gopher at (gopher:// or http://)
sugaku.homeunix.org
Basically to put in a line of text, just put in a line of text (without any tabs).
To put in a link to a file, start with its item character (or a space for the server
to figure it out, if you don't know this) followed directly by the title, a tab, the
path/filename.
For a link to a file on another gopher, do it just like the last one, then put in
tab server tab port.

You can see it best just by looking at the gophermap file on my example gopher.

That's the basics.  Later you can also put in searches, forms, multiple file types
and languages for a single link . . .

    Ralph Furmaniak