Posted by: Administrator
on November 22, 2005 05:47 AM
Filesystem drivers, on any level, need to support a full range of file operations: open-close, read-write, seek-tell-stat, (maybe) mmap. Further, these operations should all work on the same inode (device:inumber).
NFS does all this. So does Samba.
fish:// in KDE and ssh:// in Nautilus do not. They simply transfer the file to a local mount point for the application, then transfer it back on program exit. This is all fine and good if you stick to the framework's file operations, but they fall apart when the framework is not available. Worse, even if you save often, if the desktop environment crashes due to a bug or power failure, all your work will be lost when the modified local copy fails to go back to the original location.
Learn about Linux
Download Linux
Get Linux help
it's more than open-edit-save-close
Posted by: Administrator on November 22, 2005 05:47 AMNFS does all this. So does Samba.
fish:// in KDE and ssh:// in Nautilus do not. They simply transfer the file to a local mount point for the application, then transfer it back on program exit. This is all fine and good if you stick to the framework's file operations, but they fall apart when the framework is not available. Worse, even if you save often, if the desktop environment crashes due to a bug or power failure, all your work will be lost when the modified local copy fails to go back to the original location.
#