From: Miklos S. <mi...@sz...> - 2008-04-21 12:08:35
|
> What's the big deal if some applications can't save on ftpfs and display > an error message when you hit the save button. FTP is not compatible > with all file access modes - why shouldn't we be honest about that fact. > > i just changed ftpfs to return ENOTSUP on open(O_RDWR) and tested some apps: > > Kate, KWrite, Gimp, Inkscape, Nautilus (copying, moving files), VIM, > NANO and Midnight Commander still work. I guess most KDE apps still work > - because KIO doesn't encourage random file access. > > Unfortunately GEdit, DIA and Openoffice don't work, but as soon as they > switch to a better abstraction layer (GIO), they probably would. > > I could live without GEdit on ftpfs (as there are lots of other > editors), but Openoffice would certainly be nice. > > > > > But hey, you can prove me wrong. I just thing that _that_ ftpfs is > > not the same ftpfs that provides the expected file semantics. > > > > So if you want to go this way, I'd suggest to at least optionally > > provide buffering so that people may enable it if they want, dispite > > it's problems. > > > > I agree, optionally enabling buffering should still be possible... > Perhaps with a warning message that people should be careful with big files. Any news about this issue? I was reminded in the Novell bugzilla #281052, that this is still not fixed. Norbert or Braga, do you have a new version of the patch I made originally (or something else fixing this)? Or is there a new curlftpfs release planned in the near future? Thanks, Miklos |