Open GoogleCodeExporter opened 9 years ago
I'm having a similar problem. I have a networked file system mounted via ftpfs,
and
it doesn't show up in the backup list either.
It would probably be helpful to allow people to just choose any folder
available to
them that has the proper permissions instead of restricting the list down, but
thats
just a suggestion.
Original comment by ben.foote@gmail.com
on 28 Mar 2010 at 3:20
It isn't the file system that matters (FAT, EXT, etc.). For local disks the only
qualifier is that Flyback has write permissions at the root of the mount. So if
you
have a USB disk mounted at /media/usbdrive, but you only have write permission
at
/media/usbdrive/myaccount/, Flyback will ignore it.
For network mapped drives, you have to make a connection with GVFS, and you
MUST be
part of the FUSE group in order for an entry to be created in ~/.gvfs. Same
rules
apply as above, you'll need write access to the root of the networked mount.
Once all
that is satisfied, Flyback will allow backups.
This information should be written up a little better and put in to a FAQ, it
would
eliminate a lot of headaches.
It would be much easier for Debian based used to have Flyback read Nautilus
connections.
Original comment by specopsa...@gmail.com
on 6 May 2010 at 3:29
Tried right now, mounted a SSH share using gnome, cannot see it in flyback.
says no backup target available... it would be great.
Original comment by lorenzo....@gmail.com
on 11 Jun 2010 at 8:46
Original issue reported on code.google.com by
alexanderfaucher@gmail.com
on 13 Mar 2010 at 3:17