Received: with ECARTIS (v1.0.0; list gopher); Wed, 23 Aug 2006 18:34:16 -0500 (CDT) Received: from netblock-66-159-214-137.dslextreme.com ([66.159.214.137] helo=floodgap.com ident=elvis) by glockenspiel.complete.org with esmtp (Exim 4.50) id 1GG2Eh-0004mp-1o for gopher@complete.org; Wed, 23 Aug 2006 18:34:16 -0500 Received: (from spectre@localhost) by floodgap.com (6.6.6.666.1/2006.04.11) id k7NNYtqi011628 for gopher@complete.org; Wed, 23 Aug 2006 16:34:55 -0700 From: Cameron Kaiser <spectre@floodgap.com> Message-Id: <200608232334.k7NNYtqi011628@floodgap.com> Subject: [gopher] Re: Gopherspace archive In-Reply-To: <44ECE066.7040001@sdf.lonestar.org> from Benn Newman at "Aug 23, 6 06:10:30 pm" To: gopher@complete.org Date: Wed, 23 Aug 2006 16:34:55 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Spam-Status: No (score 0.2): AWL=0.117, FORGED_RCVD_HELO=0.05 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Wed, 23 Aug 2006 18:34:16 -0500 X-archive-position: 1370 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: spectre@floodgap.com Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher > If you would read the paper > (We interrupt this e-mail for an MLA-ish citation! > Lesk, M. E., "Some Applications of Inverted Indexes on the UNIX System." > Murray Hill, New Jersey: A really long time ago > We now return to our e-mail) > you would find out that there is a maximum number of keys per file/entry > (or it is supposed to to anyway, documentation not meeting reality adds > spice to life (or something like that)). How would that apply, though? If you're only indexing by file*name*, that's one thing, but if you were doing a full-text index, then your number of keys is determined by the contents of the files, not the number of files themselves. Unless I'm not understanding what you would allow to be searchable, which is possible. :) -- --------------------------------- personal: http://www.armory.com/~spectre/ --- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com -- Drive defensively ... buy a tank. ------------------------------------------