PIL jpeg support on 64 bit Precise

If you have problems with installing PIL, look at this site
In short:

sudo ln -s /usr/lib/`uname -i`-linux-gnu/libfreetype.so /usr/lib/
sudo ln -s /usr/lib/`uname -i`-linux-gnu/libjpeg.so /usr/lib/
sudo ln -s /usr/lib/`uname -i`-linux-gnu/libz.so /usr/lib/

My First Android App

Yesterday, I decided to keep up with the rest of the world in some ways, so I bought a Samsung Galaxy ACE smartphone. I know, it is not a really high-end stuff, according to the current state of the smartphone market. Anyhow, I think it is a great value for 85 pounds, with a pay as you go contract. I am really impressed by this phone, and I decided, to develop a hello world application. So, I first downloaded the Android SDK. As I extracted the tar.gz, the Readme file told me how to carry on with the installation. So I followed the instructions, first with the UI:

tools/android update sdk

With the UI, I selected to install:

• Android SDK Tools
• Android SDK Platform-tools
• For Android 2.3.3
• SDK Platform
• Samples for SDK

After the process finished, the log window had a warning:

Stopping ADB server failed (code -1).

I will ignore it for now. The whole stuff is consuming around 307 megs at the moment.

cd tools
./android list targets

And I created a project:

./android create project --target "android-10" --name HelloWorldApp \
--path ~/Documents/android/workspace/HelloWorldApp \
--activity MainActivity --package eu.lakat.example.helloworldapp

Let's go back to the "root":

cd ..

I created a small script, to include all the paths in one shot:

export PATH=$PATH:"$(pwd)/android-sdk-linux/tools/":"$(pwd)/android-sdk-linux/platform-tools/"

Changed the directory to the applications:

cd workspace/HelloWorldApp/

Compiled it to debug:

ant debug

And installed it on my device:

adb install bin/HelloWorldApp-debug.apk

Everything worked perfectly fine, I found the app in my device, and was able to run that easily. Cool!

Virtual device

android avd

Use th UI to create a new device, and simply execute:

adb install bin/HelloWorldApp-debug.apk

NFS installation

So I decided to put an NFS server to my DreamPlug. First, an easy step:

apt-get --no-install-recommends install nfs-kernel-server

Let's see what do I have:

root@plugged:~# lsmod | grep nfs

nfsd                  243695  11 
exportfs                3108  1 nfsd

So, next step is to export a directory. I would like to create a read-only export.

cat /etc/exports

/mnt/md2        192.168.0.2(ro,no_subtree_check)

TODO: Some security Okay, so let's restart the nfs server:

/etc/init.d/nfs-kernel-server stop
/etc/init.d/nfs-kernel-server start

Install the client on the other machine:

sudo apt-get --no-install-recommends install nfs-common

And mount the export:

sudo mount 192.168.0.4:/mnt/md2 /mnt/md2

It does not seem to perform very well. For example, from the client, through wifi:

time ls -la /mnt/md2/1/ > /dev/null

Gives

real 1m18.605s
user 0m0.560s
sys 0m2.632s

Whereas running the same stuff on the DreamPlug:

real 0m2.572s
user 0m1.650s
sys 0m0.920s

And that's fast. Let's try to dd some files.

dd if=/mnt/md2/1/ffc4f5bc7f6b78ac371f3ecebdd9701e4cb8c68f of=/dev/null

Gives:

577409024 bytes (577 MB) copied, 103.255 s, 5.6 MB/s

And what is the raw speed? On the server:

nc -l -p 4545 -q 1 < /mnt/md2/1/ffc4f5bc7f6b78ac371f3ecebdd9701e4cb8c68f

On the client:

nc 192.168.0.4 4545 | dd of=/dev/null

And the results:

577409024 bytes (577 MB) copied, 103.84 s, 5.6 MB/s

So nfs gives almost no overhead. (Please note, that the 1 sec was the waiting time added by the netcat server. That's negligable.) Let's see the same thing locally on the server:

dd if=/mnt/md2/1/ffc4f5bc7f6b78ac371f3ecebdd9701e4cb8c68f of=/dev/null

Result:

577409024 bytes (577 MB) copied, 19.4105 s, 29.7 MB/s

NFS over a gigabit connection (after umount-mount, to clear the cache):

577409024 bytes (577 MB) copied, 24.6491 s, 23.4 MB/s

Without NFS (nc way):

577409024 bytes (577 MB) copied, 20.9865 s, 27.5 MB/s

So yes, NFS has some overhead at these rates.