Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My one-liner Linux Dropbox client

lpan.io

Post reply on HN
Print view View original

11–20 of 165 posts

Re: My one-liner Linux Dropbox client

#11

Post by lloeki »

binaryapparatus wrote: post #9
boulos wrote: post #7

I hadn't seen entr before! My first glance at your one-liner: find $ORG_DIR | entr -r rclone sync -v $ORG_DIR $REMOTE:org is that find will enumerate all your existing files, but starting a new one won't get picked up. It seems like entr is prepared though, and you should just pass in -d. In fact why use find at all, if you want to rsync the directory?

Huge additional plus, entr does not rely exclusively on inotify, it is also 'BSD kqueue wrapper. It is the only command line utility that I found that allows cross platform (linux/BSD) scripting with file system events. I have few scripts that rely on entr and I am always sure they are OS agnostic.

Then take a look at fswatch! (See sibling comment)

Re: My one-liner Linux Dropbox client

#13

Post by lloeki »

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4.

What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

Re: My one-liner Linux Dropbox client

#14

Post by dewey »

conanthe wrote: post #12

Dropbox is a no no for one simple reason - there is no end to end encryption. Unless I don't know something? I wouldn't want a disgruntled employee to fiddle with my files.

Just sync an encrypted image if your threat model includes disgruntled employees motivated enough to mess with your account.

Re: My one-liner Linux Dropbox client

#15

Post by cpach »

lloeki wrote: post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

I too was a bit surprised by that statement. But according to Dropbox, full disk encryption should work fine.

”If you received a notification on Linux and you are running ext4, it may be because you are also running ecryptfs. ecrypfts is not supported. However, we support full disk encryption systems, such as LUKS for Linux users.”

Source: https://www.dropboxforum.com/t5/Error-messages/Dropbox-clien...

Re: My one-liner Linux Dropbox client

#16

Post by petepete »

boulos wrote: post #7

I hadn't seen entr before! My first glance at your one-liner: find $ORG_DIR | entr -r rclone sync -v $ORG_DIR $REMOTE:org is that find will enumerate all your existing files, but starting a new one won't get picked up. It seems like entr is prepared though, and you should just pass in -d. In fact why use find at all, if you want to rsync the directory?

I love entr for running tests while I'm working, it's nice to have a tool that works reliably in any ecosystem.

Re: My one-liner Linux Dropbox client

#17

Post by amelius »

jfyne wrote: post #6

It looks like there might be a bug. What happens when you add a new file? A quick scan of the entr help text suggests you should be using the -d flag.

Also, doesn't entr invoke its command in parallel when there are multiple changes in quick succession? And wouldn't multiple parallel instances of rclone potentially mess up the backup?

(I didn't read any of the man pages)

Re: My one-liner Linux Dropbox client

#18

Post by lloeki »

cpach wrote: post #15
lloeki wrote: post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

I too was a bit surprised by that statement. But according to Dropbox, full disk encryption should work fine. ”If you received a notification on Linux and you are running ext4, it may be because you are also running ecryptfs. ecrypfts is not supported. However, we support full disk encryption systems, such as LUKS for Linux users.” Source: https://www.dropboxforum.com/t5/Error-messages/Dropbox-clien...

Oh, I can see why ecryptfs would be a pain to support, but I always considered it to be some kind of an epic-scale hack.

Re: My one-liner Linux Dropbox client

#19

Post by feb »

lloeki wrote: post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

That news hit HN top stories a few months ago: https://news.ycombinator.com/item?id=17732912
Post reply on HN