ShareFS

I had to detect yesterday that ShareFS is handling ImageFS files as files and not as directories. Would be great if this could be expanded (perhaps I made a mistake and this possibilty already exists but there seems no parameter to control this as with !MoonFish.

If typing *help share an odd parameter called -subdir is listed. But this parameter doesn’t seem to work. Can anyone tell me what this parameter means and in which context it is available?

Best Regards

Thomas Milius

I don’t quite understand. Do you mean ImageFS as in the filing system technique, or ImageFS as in the program that converts GIFs, TIFFs, etc to sprites? Let’s assume you’re serving files from machine A to machine B. You want SparkFS running on machine A to export the contents of a Zip to machine B, which thinks it’s just writing a normal filesystem? Are there many cases in which you can’t just run SparkFS on machine B? I can think of a few cases where you might want to do that (mount a bunch of NFS shares on machine A with Sunfish, then export their mountpoints to machines B-Z). I wonder if there would be race conditions or anything like that? Can’t think of anything, though you’d probably want to make sure accesses were serialised.

In my case I played around with !LinkFS to set up shared folders containing a complete user dependend collection of folders/applications etc. without the need to copy the files again and again.

With a Moonfish/Sunfish combination LinkFS worked nearly perfect (nearly because one file type was missing which lead to wrong file interpretation inside !Corpernicus).

However under ShareFS you are always obtaining the LinkFS file. I would prefer the ShareFS way.

The research also lead to this silly option which doesn’t seem to work.