Using Valgrind for profiling olsrd
Valgrind is a powerful tool for performance and correctness analysis of code. This page discusses how to set your development environment up, such that you can profile a running olsr daemon and later analyze its recordings using a graphical frontend called Kcachegrind.
- Read more
- 8338 reads
slides from the 24C3
Submitted by aaron on Sat, 01/05/2008 - 20:02.I presented our OLSR-NG work at the CCC congress in Berlin around new year.
Here you can find the slides of my lightning talk.
- 2718 reads
Mercurial Changelog RSS Feed
Submitted by hannes on Sat, 01/05/2008 - 01:54.You can pull the RSS feed of the olsrd Mercurial Changelog for getting notified on all important changes in the sf.net root repository.
- 2012 reads
Tip of tree for non-Mercurial Users
Submitted by hannes on Fri, 01/04/2008 - 17:45.If you do not want to work with Mercurial you can download alternatively the "tip-of-tree" archives.
http://olsrd.sourceforge.net/hg/olsrd/archive/tip.tar.bz2
http://olsrd.sourceforge.net/hg/olsrd/archive/tip.tar.gz
http://olsrd.sourceforge.net/hg/olsrd/archive/tip.zip
- 1807 reads
olsrd switches to Mercurial SCM
Submitted by hannes on Sun, 12/23/2007 - 22:58.We are proud to announce that the CVS repository at sourceforge.net has been fully converted to Mercurial SCM All of the CVS repository 1406 Changesets including the full history and changes have been retained to Mercurial. Mercurial is a modern distributed Source Control Management system. The current maintainers think that Mercurial will not only make our life of merging trees easier, furthermore a distributed SCM resembles much more the spirit of olsrd, which is a distributed, independent system as well.
- 1671 reads
GIT
ATTENTION: as of 2009/11/15 we switched our repository to GIT
the repository migration we mentioned some days ago is complete. You will find
a web-viewer of the new repository at
The main change is that both development and stable are just two branches in
the same repository, that will make it easier for us to port patches from one
tree to the other one.
You can clone a copy of the repository locally and get a working copy of the
stable branch with the command:
or:
git clone git://olsr.org/olsrd.git -b stable
git clone http://olsr.org/git/olsrd.git -b stable
To get the development branch, just leave out the "-b stable" part
(development is done in "master" Branch").
We will post a few "short introduction to git" soon, but you might find this
link useful: http://git-scm.com/documentation
- Read more
- 15198 reads
