Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: nf2 <nf2-Sw4bTnvIGWzcouN9Qx/iuQ <at> public.gmane.org>
Subject: FUSE and lseek()
Newsgroups: gmane.comp.file-systems.fuse.devel
Date: Friday 16th November 2007 14:41:32 UTC (over 10 years ago)
AFAIK fuse doesn't forward lseek() calls to the filesystems. Therefore 
it's not possible to let lseek fail with ESPIPE if the filesystem can't 
handle seeks. Perhaps letting lseek fail would be more informative for 
an application, than letting the next read() or write() fail.

Because FUSE always expects to be able to write to arbitrary locations 
in a file, it seems to be pretty hard to implement filesystems like FTP. 
For instance curlftpfs caches the whole file in memory before writing 
it, which causes trouble with big files.

regards,
Norbert


||

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
 
CD: 4ms