Live data from Hacker News

Ending support for Dropbox syncing to drives with certain uncommon file systems

dropboxforum.com

411–420 of 429 posts

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#411

Earlier quoted context omitted.

Does it really gain steam? Last time I checked the CDDL license incompatibility with GPL made it impossible to ship ZFS with Linux, and as such, distros have separate packages not maintained by the core team (I'm thinking of Arch right now). For the record I would be very glad if I could seamlessy use ZFS, but from my perspective it looks like a lot of work that can break in unexpected places.

ZFS is owned by Oracle now. It's more or less suicidal to embed it into any Linux distribution.

LOL. I assume you're trolling. The official ZFS implementation has been Illumos for years now.

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#412

Earlier quoted context omitted.

ZFS is owned by Oracle now. It's more or less suicidal to embed it into any Linux distribution.

LOL. I assume you're trolling. The official ZFS implementation has been Illumos for years now.

There is no trolling whatsoever. ZFS was originally made by Sun and Sun was acquired by Oracle almost 10 years. ZFS is owned by Oracle and is a legal minefield.

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#413
post #409

Earlier quoted context omitted.

Airplanes are a common case where people have long stretches without connectivity, either due to not paying for wifi or any if the other reasons it might be unavailable or unusable. Being on a NYC subway train is an even more interesting case, because depending on the precise client setup there's often intermittent or bad connectivity but rarely a good sustained connection between stations. As in most of the world, s…

Offtopic but Africa is not a country.

Good point. I realized at the time that it wasn't quite right, but didn't figure out how to fix it. I should have written "those in Africa," or even "most of those in Africa."

Sorry for letting a rushed comment perpetuate the common Western stereotype of conflating all of Africa as if one single thing.

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#414
post #386

Earlier quoted context omitted.

Airplanes are a common case where people have long stretches without connectivity, either due to not paying for wifi or any if the other reasons it might be unavailable or unusable. Being on a NYC subway train is an even more interesting case, because depending on the precise client setup there's often intermittent or bad connectivity but rarely a good sustained connection between stations. As in most of the world, s…

Agreed, but these are planned events where you won't have connectivity, so you can copy the files to a local folder prior to the trip. I recognize that might not be as convenient as having the system perform a push to your machine to sync it. I think in those cases I'd probably just run rsync against the keybase folder.

Planned events in one sense, but routine daily life for those in NYC, or unplanned events in cases where airplanes unexpectedly lose WiFi. Among other examples.

You're describing useful workarounds for the status quo when one can foresee dealing with these situations occasionally. Those are certainly good to document.

But they're workarounds and not true solutions, especially not for frequent needs.

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#415

Earlier quoted context omitted.

LOL. I assume you're trolling. The official ZFS implementation has been Illumos for years now.

There is no trolling whatsoever. ZFS was originally made by Sun and Sun was acquired by Oracle almost 10 years. ZFS is owned by Oracle and is a legal minefield.

One can still dream: https://www.phoronix.com/scan.php?page=news_item&px=Oracle-Z...

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#416

Earlier quoted context omitted.

Does it really gain steam? Last time I checked the CDDL license incompatibility with GPL made it impossible to ship ZFS with Linux, and as such, distros have separate packages not maintained by the core team (I'm thinking of Arch right now). For the record I would be very glad if I could seamlessy use ZFS, but from my perspective it looks like a lot of work that can break in unexpected places.

NixOS has ZFS. I don't have long-term experience (switched to NixOS only two months ago or so), but the installation is pretty simple: (1) boot he installer CD, (2) add a line to your configuration to enable ZFS support, (3) switch to the new configuration. And then you are ready to install on ZFS root. Encrypted root also works. I used these instructions: https://nixos.wiki/wiki/NixOS_on_ZFS Ironically, I felt less…

ZFS is also fully supported in Ubuntu 16: https://wiki.ubuntu.com/Kernel/Reference/ZFS

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#417
post #407

Earlier quoted context omitted.

Ah, that. Yes, absolutely I'd love for a solution that fixes that. It would definitely need to work with large files though, which categorically precludes Git. The first point, I think, would be building a delta engine with case-specific code for the most common ubiquitous file formats, like docx, xlsx, psd, etc. Of course it wouldn't be able to be perfect with everything but it would certainly be better than eg just…

It think it does need branching and collaboration. There needs to be a way for Sally to contribute those edits, and they might not actually make it in to the final result. No doubt there would be a learning curve. I think that's OK. The target market here is serious users who already dedicate time to learning professional tools like Photoshop.

Oh no. Now you need full file format parsing so that you can resolve merge conflicts.

:(

That would take years to get anywhere with ._.

The diffing idea I suggested above is just manageable, a la macOS Preview, with hacks. Branching requires folding-back-in, and that's not just a case of "A or B", it's a case of "A, B and C conflict with D and E, while F G and H are okay," where I could then say "save B and E but drop F". If B is a layer, E is an imported asset and F is a custom filter... you get the picture. You need a reimplementation of Photoshop (halting problem).

:/

Sad that everyone hates GIMP.

But... hmm, this could get folded into Blender, and then make the rest of the industry jealous.......

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#418
post #300

Earlier quoted context omitted.

Let's not forget Fedora or EL users, XFS has been the default for some time now in both.

Only Fedora Server. Fedora Workstation, Cloud, Atomic, and all the spins, are using ext4 on LVM.

However, Fedora Workstation is strongly considering moving to XFS, as are several of the other editions.

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#419

Earlier quoted context omitted.

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.

What daemon is that?

https://github.com/abraunegg/onedrive (currently I package the original project by @skillion, but this fork is better maintained...)

Re: Ending support for Dropbox syncing to drives with certain uncommon file systems

#420
post #303

Earlier quoted context omitted.

OneDrive doesn't support dotfiles and thus can't sync Git repos.

Onedrive handles Git repos on Windows fine. It does balk sometimes if you feed it large repos, but most often it works fine.

This just sounds like a horrible scary idea. What happens if I change something in a repo on multiple machines - a OneDrive merge conflict inside .git sounds like a nightmare.
Post reply on HN