Since most distributions of Linux are constantly evolving and releasing new versions, we try and keep our clients to work with the latest releases as well. We currently (November 2011) support SpiderOak on the following distros:
The builders for each distro is on a standalone platform, so supporting earlier releases is possible if the builder platform can meet the dependencies. If you get dependency errors when installing, it is because one of these components in the system are too old. (A common one is glibc.)
This list was last updated on 4-Nov-2011.
This FAQ has been replaced by How do I install SpiderOak on a headless Linux server.
When you install any SpiderOak package on Ubuntu or Debian, it will automatically create a file /etc/apt/sources.list.d/spideroak.com.sources.list with the APT source line appropriate for the platform.
However, if you'd like to add this file manually to install SpiderOak, it should look like this:
Ubuntu Hardy Heron (8.04) or newer:
deb http://apt.spideroak.com/ubuntu-spideroak-hardy/ release restricted
deb http://apt.spideroak.com/debian/ stable non-free
All of the repositories are signed with this public key:
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.9 (GNU/Linux) mQGiBFI8CLwRBADhxvZTnHzXUQi82NoErstMPYV2WZk6e9oHXB+xWC/G+bjQU+KE pwKAbBrIw/DsffN7H92s6A5pWaoEYsOHbb8vr5U3WFn7K6LnKZyAE89Myu1mfZya sciDXxIw8VWVbdrhU5rlTfEY5dyjLN01dODcHguTR44fJKabI0ZUIIi3YwCg1Em3 zVHLB0pJfrz5qt0kHiC3C18D/AjTAA3mtsDnd3ibUBYef56bXPknEAqz8VpeAgTO Ydw6AaKCZpMLLgpeipUIsVc5r9CsqzQGKUDbAk829fqDa9Bj1gNboJbS2GzENdEC BwfoKh6Il7lWuSF/PbFu93H4jMArOpEKoN5XOL3fFQkwwMPBmw1T1EPmCDPfJltL tUAXA/9EqHid3w8rVpgNnYPaHYuaE4Nxfj8IVFMy1/1+m8gb5ff6YWkwBHLRlZ0r UyJ8w/CjoNgEpExqhcTsQMYN0/Y9kbiLKqKaODbM+aNuwiRfWLB7fJgGJVCBAPGI FtlK1KSuzkRlkEF58q+kps0mRPo9o54XY2W1ODiZgvYLXjzi3bQsU3BpZGVyT2Fr IEFwdCBSZXBvc2l0b3J5IDxhcHRAc3BpZGVyb2FrLmNvbT6IZgQTEQIAJgUCUjwI vAIbAwUJBaOagAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEKb/Iv8IwV3QUQQA oJ7Z2ki8Cw4rYkLrIhUuit79JoMfAJ97/V8P+yU9fT3olG7Kg0lCKDErHrkCDQRS PAi8EAgA4cGg3vQ7uQgLVne77MEamxZjgezeWq+AR0yzyRKuLIZrO7T9kw4DEJXX pu+TqQCzVFrgEVl5pCUoqpusTyHtUZJWlzycjRm7mF6J14ajvWY9YA7dQfuMcaw/ 1uvAwfyG9mu87aFE9yQtKAgQEdJ08xdPNWmIYz932z5wVQdj1pf9F8h8iCZGIOXS vtJHNqnyk7SeeMkImZJ9Ds+zh5Q7TOWHgBFSaVoNW2H1v6iWJPiN5s6sz6vGG1wZ D8Xye2PGaj2dCJdhoqvqurHUfRtug7TRFabm/uQPp9ePQ5Fr3636qaMryg6Y1Hxa 8jil6x9I8xYEYetPc2VQ5aO+3eEhNwADBQf9GYnAkOUw+LbexebGYQTAHVVqDuh5 ZHqnGHYS/NIUVVcD6PkqODcKixUIlzG0+PkKBm2XDiiGm9K1PtSagoBk3wo3dUxS sCYsKBwL43ii2nTvL4bsWgnsVRBgNalTIWOhthYH8m4OjsDGr4BIhNaCxuhmlouy nrrNhDz1A6x1Kr+kGwTlzr0gjHQVGNRDaKO3RoDG6lXMA/F8OamKWYlBPPtv+VNq t4J90Wnzzlku731RlrwdP4sz810FPfBEwtCPXwwDvcdXZyuUcQmOPqlCAOsHhIwy UOaGN1pwZI00n/smIvr+1k7dN1kglMofoRKNASPT0+MOOK9RV+1jm8JiG4hPBBgR AgAPBQJSPAi8AhsMBQkFo5qAAAoJEKb/Iv8IwV3QN0kAn3h8XCpk3PmIj1NGY+dx 3vIUrV9zAJ9BSLSazlJ1TOOdWhVCIMsgpudXLA== =yUaH -----END PGP PUBLIC KEY BLOCK-----
We currently provide .deb packages for Debian GNU/Linux and Ubuntu, in 32 and 64 bit. We expect to eventually produce packages for all major Linux distributions.
We have received numerous reports of users installing SpiderOak across a
variety of Linux distributions beyond those officially supported, using tools
dpkg --unpack, etc.
SpiderOak is designed as a fault tolerant application, and we regard it as a mission critical product. This means that we must take a rather more comprehensive approach to testing and QA than most software packages.
For each Linux distribution we add support for, there is an additional overhead of ensuring the compatibility of those packages with each new released version of that distribution. There is also the overhead of additional clients to the automated simulation and testing environment (see below.) So, it will take some time.
Command line operation is available on all operating systems: Windows, Mac OS X, and Linux.
Running SpiderOak with
--help should give you the general
The most common uses of SpiderOak from the command line are
--headless to run SpiderOak without any graphical user interface,
--batchmode which will run without any graphical interface,
and exit SpiderOak as soon as all uploads are complete. You can also modify
your backup selection through the
Paths to the executable:
On Mac OS X: /Applications/SpiderOak.app/Contents/MacOS/SpiderOak
On Ubuntu: /usr/bin/SpiderOak
On Windows: C:\Program Files\SpiderOak\SpiderOak.exe
This is a full list of command line options:
Usage: SpiderOak basic command line usage:
Options: --version show program's version number and exit -h, --help show this help message and exit -v, --verbose be verbose
Operational Modes and Commands: --backup=TARGET ad hoc operation: backup whatever exists at TARGET in the filesystem and exit (ignores existing backup selection.) --headless run in headless mode (without the graphical interface) --batchmode like headless, but will exit when all available work is done --scan-only scan the filesystem for changes and report a summary --scan-and-build-only scan the filesystem, and build all possible file system changes as shelved upload transactions, and exit without uploading them
Information Commands: --userinfo, --user-info Show user and device info --space Show space usage information by category and by device --tree Show the hierarchy of stored backup folders --tree-changelog Show a log of how the hierarchy of stored backup folders has changed over time --journal-changelog=folder_or_journal Show the changelog of a given folder --shelved-x, --print-shelved-x Show information about each shelved upload transaction
Backup Selection Manipulation Commands: --selection, --print-selection Show a list of selected and excluded backup items --reset-selection Reset selection (but preserve excluded files) --exclude-file=EXCLUDE_FILE Exclude the given file from the selection --exclude-dir=EXCLUDE_DIR Exclude the given directory from the selection --include-dir=INCLUDE_DIR Include the given directory in the selection --force Do in/exclusion even if the path doesn't exist
Maintenance Commands: --vacuum Vacuum SpiderOak's local database (rebuilds indexs and reclaims space) --rebuild-reference-database rebuild the SpiderOak reference database (can take awhile)
Dangerous/Support Commands: Caution: Do not use these commands unless advised by SpiderOak support. They can damage your installation if used improperly.
--empty-garbage-bin purge all deleted items on the current device --destroy-shelved-x destroy each shelved upload transaction (not intended for general use -- this will damage your break your account if not used correctly) --apply-subscription-xact apply all transactions previously received from remote devices -- (not intended for general use -- this normally happens automatically)
We recommend that you install SpiderOak through your distribution's package manager. If this isn't possible, you can use this method to install SpiderOak to your home directory. These instructions assume a basic familiarity with command-line use and text editing.
bob@machine:~$ mkdir SpiderOak bob@machine:~$ cd SpiderOak bob@machine:~/SpiderOak$ pwd /home/bob/SpiderOak
For Debian-based distributions (Debian, Ubuntu):
bob@machine:~/SpiderOak$ dpkg-deb -x ~/spideroak_9700_amd64.deb ./
For RedHat-based distributions (Fedora, SuSE, RHEL, CentOS):
bob@machine:~/SpiderOak$ rpm2cpio ~/SpiderOak-9700-1.x86_64.rpm | cpio -vid
And for Slackware:
bob@machine:~/SpiderOak$ tar xfz ~/spideroak-9700.tgz
bob@machine:~/SpiderOak$ mv usr/bin/SpiderOak ./
#!/bin/sh SPIDEROAK_ROOT=/home/bob/SpiderOak LD_LIBRARY_PATH="$SPIDEROAK_ROOT/opt/SpiderOak/lib:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH QT_PLUGIN_PATH= ; export QT_PLUGIN_PATH SpiderOak_EXEC_SCRIPT=$(cd `dirname $0` ; pwd)/SpiderOak export SpiderOak_EXEC_SCRIPT exec "$SPIDEROAK_ROOT/opt/SpiderOak/lib/SpiderOak" "$@"
Now, simply run the startup script (/home/bob/SpiderOak/SpiderOak in this example) to launch SpiderOak. IF YOU ARE RUNNING HEADLESS OR BATCHMODE BE SURE TO USE THE --BATCHMODE OR --HEADLESS OPTIONS OR YOU WILL NOT GO TO SPACE TODAY.
SpiderOak does not follow symbolic links when doing a backup scan. The reason for this is that there are too many possible ways to create a recursive backup loop using symbolic links and it leads to a number of very weird potential problems. Those often include a great deal of confusion at restore time, confusion regarding usage reporting ("Why is SpiderOak using 2.8 GB to backup this small folder??") and so on.
In SpiderOak releases prior to 2.0, there was a bug in the user interface that did not correctly show symlinks as being unselectable. That is fixed in versions 2.0 and newer.
Starting with Ubuntu 11.04 (Natty Narwhal), the default desktop environment is Unity. The default policy of Unity is to limit the number of applications that can put an icon in the system tray. While the program will still be accessible from the task bar if minimized through the window minimize function, the window close handler presents the option to minimize the application, making it disappear from the task bar, and no way to bring it back up. Furthermore, even if the task is accessible from the task bar, the added functionality only available in the system tray isn't available.
As a workaround, you can add SpiderOak to the system tray whitelist. To do so, from a terminal, give the following command:
gsettings get com.canonical.Unity.Panel systray-whitelist
This will give you a list of currently set keys, if any. You will need to add SpiderOak to that list of keys. If there are no keys, type:
gsettings set com.canonical.Unity.Panel systray-whitelist "['SpiderOak']"
If you have some already, add them to the list, like so:
gsettings set com.canonical.Unity.Panel systray-whitelist "['JavaEmbeddedFrame', 'Mumble', 'Wine', 'Skype', 'hp-systray', 'scp-dbus-service', 'SpiderOak']"
After restarting Unity (by logging out, or restarting the computer) SpiderOak will then put the icon in the system tray. This has been tested on Ubuntu 11.04 and 11.10. A future release of SpiderOak will properly address this at install time. For more information on how to get other applications to work in the system tray of Unity, check out the Ubuntu Genius blog at http://ubuntugenius.wordpress.com/2011/06/25/ubuntu-11-04-fix-show-all-iconsindicators-in-unity-panels-notification-area/.