(188) previous ~ index ~ next
To: James Allan <allan@freya.cs.umass.edu>
From: Jonathan Fiscus <jonathan.fiscus@nist.gov>
Subject: Re: Release of October Dry Run index files
Date: Wed, 22 Sep 1999 09:14:59 -0400
James,
The problems you're having are not unique, but I think most people have
worked around the problem with different version of tar.
There must be a better solution, so if you don't mind being a guinea
let's try this. There are two modified versions of the tar files that
use a flat directory structure, (the tracking index files that were in
sub directories are now in the root directory.) The URLs are
ftp://jaguar.ncs.nist.gov/tdt3/oct_dryrun/indexes_octdr_tdtrel3.1_BBNRec_v3_flat.tar.Z
ftp://jaguar.ncs.nist.gov/tdt3/oct_dryrun/indexes_octdr_tdtrel3.1_DragonRec_v3_flat.tar.Z
Let me know if this works, and then I'll use it from now on...
Jon
James Allan wrote:
>
> In attempting to use the index files provided by Jon, we've run into a
> problem that I'm wondering if others are having, too. It appears that
> the names of files are too long for our system. For example, one of
> the tracking file ends up with this name:
>
> indexes_octdr_tdtrel3.1_BBNRec_v3/trk_SRC=nwt+bnasr_TRAIN:SL=mul,CL=nat_TEST:SL=mul,CL=nat/trk_SRC=nwt+bnasr_TRAIN:SL=mul,CL=nat_TEST:SL=mul,CL=nat_TOPIC=20001.ndx
>
> That's 164 characters, and it doesn't even include the base part of
> the pathname for the directory that we're putting these things in.
>
> Near as I can tell, our system is configured not to allow filenames
> longer than 128 characters. At least, it appears to be choking at
> that point.
>
> This sort of silliness is not my area of expertise, and I'd prefer not
> to spend the time to track this down. Can anyone offer some advice?
> I'm not sure why this problem didn't crop up in June.
>
> -- james
--
Jonathan Fiscus
National Inst. of Stds. and Tech.
100 Bureau Dr. Stop 8940
Gaithersburg, MD 20899-8940
Phone: (301) 975-3182
Email: jonathan.fiscus@nist.gov
(188) previous ~ index ~ next
Last updated Wed Sep 22 10:26:05 1999