Our Blog

Updated 25 Feburary 2014

_Getting the thrift code operational to a stable state via the cglib generated output, is proving to be too time-intensive. Freezing the c_glib code for now, and moving ahead with c++ as the preferred language of choice. There are multiple advantages here, not just direc...

Continue Reading...

As I look to embark on a trip to the sands of Phuket, Thailand in the next 3 hours, I'm pleased to announce that code to implement sandboxing is now up in it's own branch in the git repo. The basic design of this sandbox code has been documented in the blog Building the eBrainPool Linux Container -...

Continue Reading...

The previous two posts on building the eBrainPool Linux Container have outlined the following strategies and problems associated with them : Design 1. Bridging the network interface on host Design 2. Unique network bridge for container Both the above strategies have the deficiency that they requ...

Continue Reading...

This is a Followup Post to eBrainPool Messaging System. What follows is my current understanding of how thrift works. I am still not competely sure that I have it right, and as I learn, I will append / change this post accordingly.

IDL file: we define the protocol in this form, thrift has it own...

Continue Reading...

Getting back to what is the kind of communication happening between two eBrainPool clients. When they discover each other, and know the route to connect to each other, how do they exchange information?

Background Reading: Our Earlier post, Workflow Sketch, how it fits together (the exact workflo...

Continue Reading...

Hello everyone.....yes we haven't been able to ask someone to RTFM so far since hmm well there has been no manual ;).....well all of that is a step closer to being changed thankfully :)

As of last night I've completed documenting the code in the current master. I've formatted the code documentatio...

Continue Reading...

Having put in code to handle Avahi discovery in what has now been labeled as the 0.3 release, I have been focusing on having an integrated libssh based server.

Aris over the libssh team had helped debug a pretty nasty bug wherein forwarded X clients would fail with error messages such as bad packe...

Continue Reading...

Well guys thought I'd put up a quick note.

Thought I'd close this year with a 0.3.0 release of eBrainPool. Code now put up on git.

This release is quite a milestone since it follows what the community has been advising us and moves away from the olsrd binding we had for discovery via our custom...

Continue Reading...

  • A BIG sigh of relief *

As we had reported here, we came to the realization that the eBrainPool client needed to be ported away from Nbtk/Clutter which is now depracated and the devel libraries are no longer available on Debian testing onwards.

The eBrainPool client was built on Nbtk/Clutter...

Continue Reading...

You know what the die-hards say "command line is the only way".. Ashamedly, I will have to admit that it is one of my favourite fall-backs too. There is however nothing wrong with making our lives a little simpler.

With all the effort going on behind the scenes, with libssh integration etc.. and n...

Continue Reading...

Well guys, I thought that while I work with the libssh guys and we figure out what is causing the strange behaviour I have been seeing with my ssh server, I'll go through the eBrainPool client code and see where we need to strengthen it - fix any potential memory leaks, run it through Valgrind, that...

Continue Reading...

New Launcher Code

14, Mar Erle Pereira

One of our issues (one of many, i.e.) was the fact that we kinda scrounged on the earlier code with regards to how the application is launched. How did we get the list of applications? Simple, from the usual location in our debian systems.. '/usr/share/applications'...

Nothing directly wrong there...

Continue Reading...