http://www.raspberrypi.org/faqs
I have BOINC & QCN running on a Raspberry Pi - it seems to run best with the BOINC for ARM running in a root account (for permissions to the USB sensors) as a higher priority process (this BOINC for ARM compiled has modifications to allow non-compute intensive tasks e.g. plan-class "nci" to run at a very high priority level). The BOINC & QCN are command-line only, ie no GUI BOINC Manager or OpenGL graphics.

I get an unfortunate but not horrible number of resets even when using the high priority, but it may turn out to be useful for earthquake monitoring (i.e. trigger monitoring but not 'round-the-clock' 24/7 monitoring due to the few resets per hour).

You can try by downloading and running BOINC (command-line client only e.g. no graphics/GUI):
BOINC for Raspberry Pi ARM "Wheezy" Debian Linux:

http://qcn.stanford.edu/sensor/download/boinc-armv6.zip

Or it may be easier to use a preconfigured SD Card image with boinc already setup so you just use "boinccmd" to attach to QCN as shown below:

1.2GB SD Card Image for Raspberry Pi (Debian Wheezy Linux, includes boinc installed & running as root)

http://qcn-upl.stanford.edu/carlc/web/qcn_boinc_raspi_8gb_sd_card.img.gz

gzip -d qcn_boinc_raspi_8gb_sd_card.img.gz

(expands to an 8GB image - so best to get an 8GB SD Card - Class 10 speed is best)

to burn sd card image, assuming your root SD card is at /dev/disk2:

sudo dd if=./qcn_boinc_raspi.img of=/dev/disk2 bs=1048576

Password for root account (& qcn account, where boinc is installed in ~/boinc) is 'qcnpi'

Note you need to unmount SD Card partition (but not eject SD card) in Disk Utility or:
sudo umount /dev/disk2s1

Otherwise you'll get "Disk Busy" messages

// my Raspberry Pi running on QCN to see the # of resets I encountered
http://qcn.stanford.edu/continual/show_host_detail.php?hostid=1034


to save your own SD card image:
sudo dd if=/dev/disk2 of=./qcn_boinc_raspberry_pi.img bs=1048576


To attach to QCN from commmand line:

sudo su

./boinccmd --project_attach http://qcn.stanford.edu/sensor ACCOUNT_KEY

where ACCOUNT_KEY is your BOINC QCN Account Key from here:

http://qcn.stanford.edu/sensor/home.php

also set your location on the page for this computer entry

http://qcn.stanford.edu/sensor/hosts_user.php

notes:
1) clock seems to be bad, but corrects with ntpdate as usual
2) onavi has the most trouble - probably usb troubles
3) still a lot of resets, made a custom boinc-arm that runs at high priority & root
4) need to run as root for phidgets and high priority
5) may be best to look into an accelerometer plug-in onto the RPi board
(i.e. bypass the USB interface which is the bottleneck)?

get root as "sudo su"

from /home/qcn/boinc run

./boinccmd to get various status updates or actions on BOINC & QCN e.g.

./boinccmd --get_messages

usage: boinccmd [--host hostname] [--passwd passwd] command

Commands:
--create_account URL email passwd name
--file_transfer URL filename op file transfer operation
op = retry | abort
--get_cc_status
--get_daily_xfer_history show network traffic history
--get_disk_usage show disk usage
--get_file_transfers show file transfers
--get_host_info
--get_message_count show largest message seqno
--get_messages [ seqno ] show messages > seqno
--get_notices [ seqno ] show notices > seqno
--get_project_config URL
--get_project_status show status of all attached projects
--get_proxy_settings
--get_simple_gui_info show status of projects and active tasks
--get_state show entire state
--get_tasks show tasks
--join_acct_mgr URL name passwd attach account manager
--lookup_account URL email passwd
--network_available retry deferred network communication
--project URL op project operation
op = reset | detach | update | suspend | resume | nomorework | allowmorework
--project_attach URL auth attach to project
--quit tell client to exit
--quit_acct_mgr quit current account manager
--read_cc_config
--read_global_prefs_override
--run_benchmarks
--set_debts URL1 std1 ltd1 [URL2 std2 ltd2 ...]
--set_gpu_mode mode duration set GPU run mode for given duration
mode = always | auto | never
--set_network_mode mode duration
--set_proxy_settings
--set_run_mode mode duration set run mode for given duration
mode = always | auto | never
--task url task_name op task operation
op = suspend | resume | abort
--version, -V show client version

It's the key to access the account - Full access
It's also called the Authenticator in the xml file: account_qcn_stanford.edu_sensor.xml, which is in your BOINC folder.

what sensor do you have? The phidget seems to need to be run as root as that's how the libusb implementation they use want it -- the ONavi may require checking permissions for the device as well.

I only had an 8GB SD card handy so the image is made from that. I have to run as root for the Phidget sensor as their libusb library requires that. Also it runs better as root as in the BOINC I made for ARM, I run QCN at highest priority otherwise you get a lot of "resets" as the USB hardware seems to be slow. The ONavi should be able to run in a BOINC user account but you have to fiddle with the permissions to allow the lower-priority-security.

if you run it as root then the boinc version I created will be able to increase the thread priority and lower the # of resets.

OK, the Pi seems to be a bit sluggish for QCN, I think due to their cheap USB hardware and has trouble at 50Hz - I had better luck with other devices like the Guru/ShivaPlug. I hope a future RPi will have a little bit better, or maybe we can design an accelerometer plug-in board for direct fast access (bypassing the USB bus), as something like the RPi would be great for getting a lot of cheap QCN stations out there!

in the boinc client I made for RaspPi it will bump up QCN app to "real time priority" - this has to be done on the BOINC side as it will force the default of "idle priority" (i.e. as normal BOINC client). I'm glad you have it working, I think this may be great for the future of QCN.

yeah, the Pi is setup for the JoyWarrior, ONavi, and Phidgets 1056 USB sensors. I think it would be best to have an accelerometer on a board that plugs in to the Pi ie bypassing their sluggish USB.