dropbox installer

TeknoJnky wrote:
does this addon automatically install the latest dropbox linux release, or only a particular version?

Currently it downloads a particular release of DropBox

TeknoJnky wrote:
does the dropbox linux release update itself, or is it required to pay for another 'dropbox installer' ?

The automatic update feature is broken at this time. WhoCares? is looking into a fix for this. For now the update files that dropbox automatically downloads are deleted.

You would have to pay for an update. See http://www.readynasxtras.com/about (page appears to be down at the moment but shouldn't be for too long).

However if you know what you're doing you could extract the contents of the add-on modify the install script (i.e. the line where the dropbox tar archive is downloaded from dropbox.com via wget) to download the latest version of DropBox and install the add-on over the top of itself. No guarantees this would work (though in most cases it should), but you'd be missing any bug fixes or other improvements WhoCares? makes to the add-on.

This is my favourite community add-on at the moment.

thanks, I'll wait until the auto-update is working.

FWIW, the current version of the addon is v1.2.49-rnx86-0.2.25, which is newer than the one indicated in the "intel" addon forum.

I'm just posting to follow-up and ask whether anyone else has noticed that applying a new version of RAIDiator (upgrade or downgrade) results in Dropbox not starting at all. I've had to uninstall and reinstall the addon each time I apply a new firmware image to the NAS. Annoying at best, to be quite honest. I'm curious whether others are seeing this behavior.

I haven't seen this happening yet. The thing is: the dropbox add-on doesn't require anything special from the ReadyNAS firmware. So the only thing that I can imagine preventing it from starting up properly after a firmware up- or downgrade is that the the /etc/default/services file gets overwritten or mangled somehow. Because this is the central point from which Frontview determines what services/add-ons to start (or not to start). If after an up- or downgrade the Dropbox entries in this file aren't there anymore, the service won't start. That said I already did some firmware updates on the ReadyNAS where my Dropbox is running and it continued to work just fine. So I'd be really interested in why it doesn't work for you. I will do some local testing but in case you find out more details in the meantime, it would be nice if you could share them.

-Stefan

Well, I've had a look through the startup scripts and config and I do definitely see a problem, but unsure of the cause. One this is true... up- or downgrading the firmware will not itself cause the issue. Rather, simply /restarting the NAS/ will cause it.

The init.d script expects the file /c/.dropbox-dist/run_dropbox.sh to exist, and it doesn't. Strangely, it does exist in two different /c/.dropbox-dist-old-* directories, but not in the current one. Very odd. Wonder why... But whatever is happening during install obviously doesn't run the normal startup sequence, or it would fail. So instead it just lurks waiting for a restart to happen.

That is odd. I see the run_dropbox.sh file in my installation of the add-on and it's still there after a reboot.

A re-install of the add-on will remove the /c/.dropbox-dist directory and redownload it.

mdgm wrote:
That is odd. I see the run_dropbox.sh file in my installation of the add-on and it's still there after a reboot. A re-install of the add-on will remove the /c/.dropbox-dist directory and redownload it.

Actually, an uninstall causes that folder to be renamed /c/.dropbox-dist-old(something). Upon installing, /c/.dropbox-dist is created but still lacks the script.

Actually the remove.sh script like the install.sh script removes the /c/.dropbox-dist directory. It must be dropbox itself that creates the old directories.

Well the install.sh script adds the run_parts.sh script to the /c/.dropbox-dist folder during installation. You can copy the file from /c/.dropbox-dist-old to /c/.dropbox-dist. The current version of the script was modified early November 2011.

mdgm wrote:

Actually the remove.sh script like the install.sh script removes the /c/.dropbox-dist directory. It must be dropbox itself that creates the old directories. Well the install.sh script adds the run_parts.sh script to the /c/.dropbox-dist folder during installation. You can copy the file from /c/.dropbox-dist-old to /c/.dropbox-dist. The current version of the script was modified early November 2011.

All I can tell you is that I'm getting inconsistent behavior with respect to this and your read of the script. What I do wind up seeing is the following:

drwxr-xr-x  4 admin    admin    4096 2012-02-13 18:16 .dropbox-dist
drwxr-xr-x  4 yang     users    4096 2012-01-18 11:01 .dropbox-dist-old-d5xe2o
drwxr-xr-x  4 admin    admin    4096 2012-02-13 16:15 .dropbox-dist-old-F2a6H6
drwxr-xr-x  4 admin    admin    4096 2012-02-13 13:12 .dropbox-dist-old-GLc4LV

I have had to cleanup many older "dist-old" folders in the past, and have no idea why it would even leave these sitting around. The .dropbox-dist above also didn't have a run_dropbox.sh in it until I copied one from one old "dist-old" folders, after comparing them and finding them identical. I've no idea why it's doing this... I'm just reporting the behavior.

During install, the addon reports itself as:

Name:  	DropBox  	
Version:  1.2.49-rnx86-0.2.25 	 
Date:  	Wed Jan 11 15:23:30 2012 	 
Size:  	70 KB

What I'm saying is that I can't see anything in the install.sh or remove.sh script that creates those additional folders so they must be created by dropbox binary itself.

I was referring to the date of the creation of the run_parts.sh script not the add-on itself. Though some files in the add-on are from 2011, some aren't.

When the Dropbox add-on is installed /tmp/rnxpkg/run* is moved to /c/.dropbox-dist. That is in the folder WhoCares? chose to temporarily place some files any files beginning with "run' will be moved to the /c.dropbox-dist directory. For whatever reason on your installation this file has been removed somehow. I can see no reason for why this would have happened. It is rather odd.

The ownership of /c/.dropbox-dist-old-d5xe2o looks rather odd. It should be owned by the admin user.

Can you do a

ls -la /c/.dropbox-dist

and check to make sure that all the files in that directory have owner and group both set to admin?