Re: FCOOKIE_CACHE: serious problems with stale data

[sm001pe@unidui.uni-duisburg.de (Pereira Martins)]

> There is a serious problem with the cookie cache: if two different
> file names are used that the filesystem treats the same (because of
> truncation) the cache can contain stale data, resulting in incorrect
> file name.

[..]

> The cache now contains two entries with different names but the same
> cookie, which is already bad enough, but you can now open the file
> "short-name" via the name "long-file-foo-bar" although this file name
> does not exist! The cache information disagrees with the file system,
> which will certainly lead to total confusion!
> 
> Until this problem is fixed the file cookie cache should be disabled.
> 
> -- 
> Andreas Schwab                                      "And now for something
> schwab@ls5.informatik.uni-dortmund.de                completely different"

Well, how does this cookie cache works ?
This cache is a piece of memory ?!! But this truncation only happens
if you access GEMDOS partitions!
So we could perhaps use a Minix XFS partitions if a info file is created
or if this should happen in memory we could use a ramdisk like y-disk
(U:\tmp\Packdir). On a ramdisk long filenames should work ?! I'm not sure
and at the moment I can't test this because I'm writing this under X Windows
... :-)


An other idea is to change the default size of a filename to a longer
value. instead of 13 or 14 we could choose a higher value 62 or so ...
For this we would have to change some header files.
This value is defined by :

#define ... 14

in the header files.

As I don't have any sources on my X Windows account I can't mention this
exactly :-(

It was only an idea, perhaps it's useful :) 

With best regards, Filipe

P.S.: I'll search it at home on my TT and tomorrow or so I'll say the
exact places which should be modified.