Complete.Org: Mailing Lists: Archives: gopher: January 2002:
[gopher] Bucktooth+
Home

[gopher] Bucktooth+

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Gopher-L <gopher@xxxxxxxxxxxx>
Subject: [gopher] Bucktooth+
From: Ralph Furmaniak <sugaku@xxxxxxxxxxxx>
Date: Mon, 28 Jan 2002 19:43:25 -0500
Reply-to: gopher@xxxxxxxxxxxx

Bucktooth now supports Gopher+.  This is the [unrated] release and
unoffical/unsupported until Cameron Kaiser can check it, and take care
of the install and documentation.   You can see it in action and
download it at gopher://dotdot.homeunix.org
gopher://sugaku.homeunix.org should also work since it points to the
exact same address, but for some reason doesn't on the gopher->web
gateway @ heatdeath.  I am behind a router/firewall so haven't been able
to check this connection.

I was meaning to give it a thorough lookover, but am running low on
time, so I'm just putting this out there if anyone wants to check it.
It works for me, will work for you, but I'm not making any promises.  To
my knowledge, it doesn't have any security problems or bugs, but if you
don't trust me, it can chroot just like the pros.

It is currently configured for xinetd, so you need it if you want to try
the server.  All of the configuration is currently in the buckd+ file
itself.

Let's see, I guess you want to know what changed.  First of all, there
is full gopher+ support (yay!).
It caches the directories (WWGD) (default 3 min), and attributes of
files on other servers (default 1 day).
You put in any extra attributes of "foo" in ".foo"
If you want to have multiple views of "foo", put all of the views in the
"foo.dir" directory.  If you still have a file named "foo" in the parent
directory then this is presented to the gopher0 clients.  Otherwise,
gopher0 clients are given a choice between the different views.  This
way, everyone's happy, and you can set up multiple views without
worrying about the poor gopher0 folks.
By default, long info lines are wrapped to 65 chars.
An itemtype of 'X' in the gophermap hides that element (WWGD), and if
you are lazy you can put an itemtype of ' ' and it will automagically
figure it out for you.
To force an item to be listed as gopher0, but a tab and a 0 after the
port in gophermap.

I guess that's pretty much it.  Making a gopher+ server is much more
difficult than a gopher0 server, umn's client is especially picky with
the outputs.  Sizes: buckd is 4271, buckd+ is 13118, and the diff is
16699.  There is little of the original code left.  Plus, the program is
no longer contained in a while loop that exits after running once.

Things that can still be done are: to have it support gopherd config
files, getting it to work on Windows, and something else which I forget
now, oh well, c'est la vie!

You may now worship me as your god.



[Prev in Thread] Current Thread [Next in Thread]