Received: with ECARTIS (v1.0.0; list gopher); Wed, 07 Aug 2002 01:49:35 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "*.myrealbox.com", Issuer "Thawte Server CA" (not verified)) by gesundheit.complete.org (Postfix) with ESMTP id 61EAA62E39 for ; Wed, 7 Aug 2002 01:49:34 -0500 (EST) Received: from myrealbox.com aangel@smtp-send.myrealbox.com [24.171.111.62] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.11 $ on Novell NetWare via secured & encrypted transport (TLS); Wed, 07 Aug 2002 00:49:34 -0600 Message-ID: <3D50C2CC.50007@myrealbox.com> Date: Wed, 07 Aug 2002 01:48:44 -0500 From: "Aaron J. Angel" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020710 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gopher@complete.org Subject: [gopher] Re: Process question References: <20020806135709.A6583@pongonova.net> X-Enigmail-Version: 0.49.5.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 660 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: aangel@myrealbox.com Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher Mmm...this is a bit late, actually, but here it is. > Since I'm opting to use a gophermap file (in each dir), I'll need to > keep it updated with new additions. > > Is my understanding correct? If not, I'd appreciate some pointers as > to how you go about keeping your gopher server healthy and well-fed. Yes, that's correct; if you use gophermap in directories, you have to add everything you want to be seen on the menu. An alternative, if you just want a description for files, is to use metafiles (by creating a file with the same name and appending .abstract) to hold the descriptions. This will still show anything that doesn't have an abstract, but will give you an opportunity to provide one if you like. For example, in the gopher directory you have: .abstract - Text about the contents of the directory itself my-life-story.txt - Contains your life story my-life-story.txt.abstract - Contains a line of text: X's Life Story some-other-file.ext - something else The menu will look like: (contents of .abstract) (link) my-life-story X's Life Story (link) some-other-file.ext You can't, however, modify the name shown of the links this way. Another method you could use is a .cap file, which is from UMN Gopherd, and allows you to rename only certain files, but still shows all of them, regardless of their being mentioned in the .cap file. Something like this works nicely. Create a directory called .cap/, and have files under it with the same name as the file in the parent directory: .abstract my-life-story.txt .cap/ - Directory .cap/my-life-story.txt - Contains the following: Name = X's Life Story some-other-file.ext And this is the menu: (contents of .abstract) X's Life Story some-other-file.ext It seems that .caps files do not work with .abstracts for the same file, so beware. Also, you can read the gopherd manual page (if you have it; else, you can look somewhere on the web, there is plenty of information), for other options you can use in .cap files to modify thinks like Gopher types, placement on the menu, etc. Of course, the use of .cap/ and gophermap fails with one taking precedence. Hope this helps. -Aaron