Randall R Schulz wrote:
The application probably cannot seek(2) a fish: stream, so if it needs random access to the file, it probably won't work.
Also, I don't think this is a kernel-resident facility, so applications presumably have to use a particular library or libraries for file selection and access in order to get the intervention necessary to make the transparent fish protocol work.
But that's just a hunch / guess.
Hi Randall, that pretty much matches my own thoughts - the only "problem" is that acrobat reader works fine with fish:// objects. And that's a non-SUSE acrobat reader. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com