Earlier quoted context omitted.
Would you kindly provide recommendations? I'm looking for a sync service which can run on windows AND linux (which is why onedrive and google drive are out)...and i'm willing to pay a fair monthly fee.
rsync.net seems to get mentioned around here every now and again. I haven't used them though personally, so not sure of good/bad/etc. Unlike what their name (rsync) suggests, they do seem to support Windows clients and aren't *nix only: https://www.rsync.net/resources/howto/windows.html
Ending support for Dropbox syncing to drives with certain uncommon file systems
161–170 of 429 posts
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#162Earlier quoted context omitted.
Just use syncthing. It works better, is open source, and runs on everything.
Doesn't that require you to play sysadmin running your own servers?
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#163I basically only use Dropbox because it is supported on Linux. Also its syncing technology is sooo much better than Google Drive you would think Drive was built by interns. However, they are taking their sweet time with newer features like Smart Sync. It's disappointing because I'm paying for these features and yet they're not supported on one of the platforms my whole company uses. All in all I really hope Dropbox d…
There's a decent open source sync daemon for OneDrive on Linux - I'm the packager who looks after it on Fedora. With the odd exception when APIs change it just works.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#164Earlier quoted context omitted.
But where would you sync to? Dropbox also keeps a copy of your files which makes it attractive without the need to set up configure your home nas. Although it's arguably a more intelligent decission to share private files not with a company like dropbox.
> But where would you sync to? You sync across your devices (or anything where you can run a standalone binary). Phone, PC, server, whatever. It's pretty good and very stable when your packager doesn't fuck up the service file ( https://svnweb.freebsd.org/ports/head/net/syncthing/files/sy... ). > without the need to set up configure your home nas That's only needed if you need access to your files from the outside wo…
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#165Earlier quoted context omitted.
None. You run it on your machines and they will sync among themselves. No need for any cloud backend. Some people with Synology or QNAP run an instance on their NAS.
But I (and I suspect quite a few other people) want a cloud backend to cover both the disaster-recovery cases and syncing while outside my LAN.
2) you can run your own off-site instance, that can be hosted with your favourite cloud provider.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#166Excluding XFS is an odd choice as it's very common in the server world. I'm assuming encryptfs-ext4 has some attribute issue that prevents them for doing efficient deltas. That aside, what's the use case for encryptfs at all? Isn't it strictly worse than LUKS on the underlying volume or a volume file mounted via loopback?
I would hold my horses on xfs being unsupported claim. They explicitly said any modern file system with xattr is supported. XFS does fit that description. OP has drawn his own conclusions from the Dropbox reply.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#167Move to where? How do I get it to work on Ubuntu again?
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#168Earlier quoted context omitted.
Just use syncthing. It works better, is open source, and runs on everything.
I guess you could say it runs of everything unless you use one of the two most popular operating systems in the world: Android and iOS.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#169This sounds fine to me. Ya'll are making sound like they're refuseing to sync because the FS is encryped. The file systems mentioned are really old. You can use newer FS's that are encrypted. They need to support extended attributes for obvious reasons.
ext4: October 2008 btrfs: March 2009 ecryptfs: May 2016 xfs: 2002 Which one of these are old?