Ok: I had a thought the other day on an FTP fs, similar to NFS and the
/proc system. Essentally: All it would be is a directory structure.
I.E. /ftp/dotted.ip.of.host/structure
This would be held in files: probably gzipped ls -lR
if you read a file, it would attempt to connect, and fetch the file
(into a definable size cache) I.E. you could
cd /ftp/ftp.cc.gatech.edu/pub/Linux/kernel
ls
(provides most recent ls of the directory)
cat README
fetches README from the correct dir into buffer, and then cat's it.
Connect-on-demand is supported (lynx, ncftp, etc) so that wouldn't be
too hard to do. For administratiors: Since, while browsing directory
listings, they arn't actually CONNECTED to the site, only to fetch a
file, how much would this reduce load?
Anyway, I havn't more then started looking into this project,
(mostly looking for a skeleton fs device to pick apart)
but I would be glad to try my hand at it if people
thought it was a good idea.
chaos@dynamic.ip.don't.reply Guess what? I really _DO_ speak for
Dan Merillat / Harik A'ttar my system. And if you share my opinions,
in00621@pegasus.cc.ucf.edu you should seek professional help.