> This sounds like a losing proposition for NFS and UFS, too, since it's
> likely to hose your buffer cache. It seems to me that the right thing
> to do is not to open the file until the user clicks on it (or
> whatever). I think this would also make the GUI a lot more reponsive.
> when reading large directories.
Nevertheless, I can envision certain situations where I know
I will not refer the file again, and hence don't want it cached.
Usenet falls into that category. I very rarely read the same
article twice in the same session. If the usenet spool areas were in
AFS, then when I've finished reading news, the cache would be full of
information I don't expect to reference again in the near future.
It would be nice if you could mark some directories/files
with a "do-not-cache" attribute, to prevent the cache from getting
filled with unwanted stuff.
-Shiva
-=-
ITS Systems Programmer.
