Code

Working with openSUSE's Kernel Source

This is more for my own self reference as I go through fits and starts of having to touch the kernel and end up forgetting WTF I need to do, but it may come in handy for others; especially if people want to enable new hardware etc. As we all know openSUSE follows the mainline kernel source pretty closely. We have as few patches as possible, but sometimes those patches build up as time goes on (think backporting etc.

Counting down to the new Geeko with some robotic help

As many know, I have a few Android devices, and I know a lot of other openSUSE fans out there also have robot powered devices. I decided the other day to try something during my lunch break – create a widget to show how many days left till 11.4′s release. Yeah I know it isn’t an earth shattering application, but I’m not a code monkey, so any working code I generate is a serious plus for me ;-)

Bugging Bugs - A Call For Help

Personally I find that in Linux or any OS for that matter, keeping track of and dealing with bugs can be a real PITA. This may be in part that I’m not a power user of the services available (they don’t make it obvious how to fully utilise their service); also there are so many different types of bug trackers out there – bugzilla, trac, mantis, etc; it is also down to so many different projects use their own tracker; one advantage is that code/project hosting sites have their own – SourceForge, Gna!

Story telling your Gitorious exploits

Suffice it to say, I’m actually enjoying my Storytlr install – maybe enjoy isn’t the right word but you get my drift, don’t you? Well I was determined to loose my coding virginity, and Storytlr’s plugin system seemed to be the safest way to do so. I chose to base my plugin on an existing plugin, and my two options were creating a Blip.tv plugin (based on the Vimeo plugin) or a Gitorious plugin based on the Github plugin).