The packages we build for deb.tpo are compiled for various Debian and Ubuntu architectures. These currently are amd64, i386 (x86-64 and x86), and two arm ports: armel and armhf.
Arm CPUs come in different versions, and newer versions generally have more features. The arm ports of Debian differ in what kind of CPU they need as a minimum. In ...
Linostar's answer is on the right track, but missed the Tor version you specified. You should update to at least the 0.2.5.x series for Tor to try and detect out of memory situations and handle them smartly. I'd suggest upgrading to either 0.2.5.x or even 0.2.6.x if you don't mind an alpha to se what happens.
The error message says:
Alternatively, to build without manpages, use the --disable-asciidoc
argument when calling configure.
When you use debuild you can't just enter configure --disable-asciidoc. You'll have to edit the file debian/rules. On line 22 of the file there is a section which deals with configure options:
I feel a little silly about this but I found an answer. I'm not sure how it differed from my approach. This is taken from https://gk2.sk/running-ssh-on-a-raspberry-pi-as-a-hidden-service-with-tor/
chmod 700 $SERVICE_DIR
chown debian-tor.debian-tor $SERVICE_DIR
Checked with the following as per How to ...
No problem! Doing it myself regulary! You need a gcc and g++ and the next libraries, compiled in the order of listing here :
Zlib. You need it to compile OpenSSL with compression support
OpenSSL. Take a stable source if you're not PRO with source building
Libevent. Take a 2.0 current version and go on
In configure I strongly recommend you to install in a ...
Thanks for running a relay. (:
Clients choose which relays to use based on their consensus weight. The consensus weight is assigned by the directory authorities after measuring the throughput for your relay.
There are a number of things that can impact the speed at which your relay can be used, including the CPU speed, CPU architecture, the network ...
It may or may not be an attack, but my personal opinion is that Tor isn't guessing the right values for some parameters like MaxMemInQueues (like it was setting them too high, then too low later). Try setting the 2 parameters MaxOnionQueueDelay and MaxMemInQueues yourself and see if the performacnce becomes more stable. It may help also to limit the bandwith ...
Although the answer has been accepted, I have some sort of update:
While everything "weasel" said is true, we now have the Raspberry 2,
that works perfectly as it features an ARMv7 CPU.
In other words: Go ahead and add the Debian armhf repo of
the Tor project and it will result in an up-to-date setup that's
working like a charm (as long as you use a ...
I found a complete tutorial for Raspbian with prebuilt binaries for the latest version. Also, full instructions for building from source are provided.
You can catch them here: http://unsuspectingbit.com/tutorial-private-anonymizing-proxy-raspberry-pi-tor-based/
[on Saturday11April2015 Seems to be a dead link: If anyone has a more current link or if the new ...
For those looking for binary downloads, see https://github.com/gordon-morehouse/cipollini/tree/master/raspbian_packages with the appropriate caveat emptor about installing binary software from a dude you don't know (me) on the Internet.
I don't have deterministic builds going for Raspbian packages yet, so these are hand-built straight from the source ...