Is google building a worldwide wifi network?

Yesterday after upgrading my phone from Android 4.0 to 4.2, I noticed that my wifi password were automatically restored from Google backup.
Call me n00b, but I hadn’t read that G save it!!!!

The thinking sequence was:

  • Google scanning for wifis meanwhile building Gmaps
  • Google saving TONS of wifi passwords coming from android
  • Google have access to 50%/60%/70% of the whole world wifis!

I suppose I’m not the 1st on thinking about that but… it makes me shudder man…

The inexpensive Video-Phone project

Happy new year!!!
After my adventures trying to build Android from source, I want to explain the reason for that.
As I live very far from my fathers and they’re elder, I’ve been thinking for a long time how to have a easy way to make videoconf with them and share photos… The usual things you know?
The main problem was that they’ve never used a PC and the newest gadget they have is a Nokia X2

Continue reading “The inexpensive Video-Phone project”

My adventures with Android (I)

The history:

Recently I bough a “Ainol tornados” for testing purposes, and that was the cheapest one (~60€ shipping included!)
When it arrives to me, I tried to install openvpn (is basic for my project) but nothing on the “tun.ko” repo works for me :-(, the “magic string” which makes match a module with the kernel does not match and I tried all the avalaible rom except 4.0.4.
The problem was the insmod itself, not the tun.ko installer.
So I decided to build my own version of the android :-)

Here begins the adventure itself…
I downloaded the source code directly from Ainol forums… That HUGE package contains EVERYTHING for building (android-sdk, android-ndk, crosscompilers in multiple versions, emulator files… ETC), so don’t care about that if you’ll donwnload it.
Starting from the AOSP project wiki, I set up the build environment with java6, make 3.81.
So: Continue reading “My adventures with Android (I)”

Explicando un tunel ssh

Que mejor manera de explicar un tunel ssh que con un dibujito?
(Me he dejado las puppets en casa)

A veces parece increíble que a un ingeniero diplomado le cueste entender el concepto de “cerca”, “lejos” y “saltar a través” que supone un tunel.

Personalmente siempre me ha gustado la explicación con ascii art:

+----------+<--port 22-->+----------+<--port 80-->o-----------+
|SSH Client|-------------|ssh_server|-------------| host |
+----------+ +----------+ o-----------+
localhost:8888 computer www.linuxhorizon.ro:80

En el que basta con explicar que “www.linuxhorizon.ro:80” no es accesible desde “SSH Client” y mediante el tunel ssh a través de “ssh_server” QUE SÍ TIENE ACCESO, te traes el puerto :80 a tu ordenador en el puerto 8888.
Todo esto con una linea tan simple como:

SSH Client$ ssh -L 8888:www.linuxhorizon.ro:80 ssh_server

Os dejo el maravilloso dibujo con el que puede ser que me haya entendido “mi” usuario ;-)

Parallel rsync’ing a huge directory tree

Some days ago I was on the chance to transfer a huge directory.

Huge means ~50TB with +10million files and a deep of only 6 folders under the parent one.
As I must do that kind of transfer more than 10 times with the same amount of folders… I decided to implement some kind of parallel function which launch parallel rsync’s at a given deep of my choose.

The ressult was that “pure bash” little script (the only dependency is “screen”)… You’ll notice that the main function “sync_this()” will run alone in your script only changing 2 or 3 variables ;-)
Continue reading “Parallel rsync’ing a huge directory tree”

UUID’s, pupets, redhat y ¿¿ubuntu??

Supongo que a cualquier linuxero le hacen mucha gracia los UUID’s, sobre todo cuando después de particionar el disco duro planchado por un sistema de imaging (pupet) te cambian los UUID’s sin tú darte cuenta…
Y claro, arranca tu el sistema después si quieres ¬¬
Asi que nada, arrancando con la shell mínima (init=/bin/sh) a cambiar todas las entradas del fstab por algo que todos entendemos, es decir /dev/sda* y pa’lante.

Lo curioso de todo esto es cuando intetas hacer un “init 6” y el redhat modificado de turno te responde con esto:
Ubuntu en redhat?

Problem redhat? ;-)