Everything is a Freaking DNS problem

For those who wonder why my blogging is so low these days (apart from today) .. I`m actually writing more Lines of Code than Blog Entries the last couple of weeks:)

And when I`m not writing code I`m reading :) Either proofreading an upcoming book on Zabbix or reading some of the other books Packt sent me.

Next to that I`m busy preparing my T-Dose presentation

Oh and did I mention a 40 something questions questionnaire about some merger ?

Dear MySQL and Drupal , Plone and other Open Source folks, you might want to be interrested in giving a talk at T-Dose 2009 ,

Jean Paul pinged me with the following mail :

Maybe it escaped your attention that the Call For Papers for T-DOSE 2009 is already out. It has been announced on 12th of June 2009. Below you will find the original announcement.

Call for Papers and Projects
Fri, 06/12/2009 - 13:57 — jpsaman

T­-DOSE is a free and yearly event held in The Netherlands to promote use and development of Open Source Software. During this event Open Source projects, developers and visitors can exchange ideas and knowledge. It is held at the Fontys University of Applied Science on 3 and 4 October 2009.

Speakers can send ideas and abstracts to the organisation at abstracts _AT_ t-dose.org. The e­mail should contain a short biography of the speaker and description of the talk. All talks will be held in English and last ~50 minutes. The deadline for abstracts ends on 31st of August 2009.

At the event location there is room for Open Source market. Stands and rooms are free of charge. Applications for stands are handled in order.
More information is here; http://www.t-dose.org/t-dose/files/t-dose-2009.pdf

I hope to see you all at this years T-DOSE.

Kind greetings,

Jean-Paul Saman

T-DOSE Foundation
www.t-dose.org

So the cat is out of the bag,

As of today Inuits is rebranding to Pinuits,
The press release is here

We've had good feedback on the new name so far. Different people told me the name matched better to what we are doing . Actually my wife thinks our new name is much better as at least the Pin in Pinuits refers to our favourite Tux again ..

Finding an appropriate name for an Open Source consultancy company, with focus on Linux, Open Source Monitoring, MySQL, Open Source Virtualization , Large Scale Deployments , High Availability and Drupal, isn't easy .. you want to show both community involvement and professionality. And find a domain that's still available.

Grab your calendars and mark the following dates :

• T-Dose 2009 will be held on 3 and 4 october in Eindhoven again.

  Last year we had a nice Drupal track, some great MySQL talks and , a great unplanned Cloud talk , and different other interesting talks, so this year promises also to be very interesting.
  (PS. Drupal Themers.. you might want to propose a new theme for the T-Dose site, who knows you'll even win something)

• For the first time , 2009 will be the year that Belgium will have it's own Security Conference, BruCon has just announced Christofer Hoff as a KeyNote speaker , BruCon will take place on 18 and 19 september... obviously in Brussels ;)
• While we mention VirtSec I obviously should plug my own upcoming VirtSec talk at the LSec Secure Virtualization seminar on next Friday 13th

Last Wednesday after the LSec event with Bruce Schneier and the R ans S from RSA , we already had a mini AdHoc GeekDinner in Leuven, one that pretty would have matched Philips requirements for having it called Geek dinner

Philip has been ranting this week about different events titled "Geek" not attrackting real geeks. that know hex and binary is but merely atrackting the Startup/Web crowd, now there's nothing wrong with both crowds, and I happen to be part of both but it can cause strange situations
Geekdinner.beTom K arranged a nice deal with De Troubadour so foodwise it promises to be great.

And with the list currently showing a variety of
Linux and BSD geeks, (both on Kernel and System Level it seems) the Apache geeks , some Ruby geeks, some Legal geeks, some Java geeks, etc that part should be covered ..

So I`m pretty sure that the majority of Geeks at the upcoming Geekdinner will realize there are only 10 kind of people

Still missing however from that list are the Drupal and PHP folks, the Django crowd, some Distribution geeks, some Gnome Geeks and some KDE geeks. Heck you all know I`m talking about you .. so go and subscribe here

I hope we aren't scaring away too much folks with this really Open Source oriented GeekDinner :)

PS. And yes I think it's time for Elise to organise a Real Belgian Girl Geek Dinner :)

Unless you are doing it wrong.

And sadly I`m seeing more and more people doing it wrong.
To a lot of people Open Source means that they have a piece of software that does almost what they want and which they can modify to their best wishes and use internally.

So they fork locally,, they don't redistribute their code , but they aren't contributing their changes back upstream, chances are these changes wouldn't be accepted upstream anyhow as they are really customizing the code for their specific cases. At first sight this doesn't look so bad , at second sight ..

When weeks or months later the upstream project releases an urgent security fix, the local fork has deviated soo much that it can't upgrade anymore and stays with an insecure version.
Often it's worse.. a feature that could have been accepted upstream has been implemented slightly different in the local fork, the result being that newer features depending on the first one also can't be integrated anymore

Some projects are prepared for local contributions, they have a modular framework that allows you to build on top of the project while not having to touch the core of a project, Drupal and openQRM are great examples of those, but not all projects are that smart. Needless to say that when you have such a modular framework you really shouldn't be modifying the core part of the platform, unless you are fixing a real bug.

But the general rule of thumb is that when you fix bugs, make sure they are inserted upstream , or implement new features.

Now sometimes there is no easy way to get your code accepted upstream, in which case you should announce clearly that you want to contribute but you are blocked and publish the patches somewhere else ...

Don't let the community work for you, but work with the community !

Larry, I`m glad you asked ..

With the risk of receiving a flood of comments pointing me to already existing tools here's my go at what I as a sysadmin of often large deployments am looking for in Drupalland .

You suggest LDAP and syslog integration .. guess we already have that don't we ?

But what I haven't found yet ..
An rpm/deb repository of Drupal modules So we can do an apt-get install drupal-package , yes I know about Drush, but I want the files on my system to be in a package and clearly identified, it helps me keeping my system uncluttered.

apt-get update drupal-package , or yum install drupal-package would be a luxury, same for themes btw.

It would be lovely if the postinstalls of those package also trigger a database upgrade if needed.

Which brings me to the next issue. If I have a multisite setup and I update a module in sites/all/modules, I usually have to go trough each and every site hosted there to update the databases. No really something I like to do for 10+ euh 3+ sites.

Also think big, don't waste your time on desktop apps or guis .since as long as you only have 1 site to manage point an click is fine, for you , Think in terms of what if you have 10 sites, 100 sites, or more .. do you really want to do that kind of administration via a browser or gui ? Some wise man once said If your computer can't install it the installer is broken. A script should or automation tool should be able to interact with the sites, not a human operating a mouse ;) It's not just the RSI , but also the fact that to err is human, and if the computer fails a script you can patch it :)

If you read this blog, you should probably sign the petition !

After reviewing the Zenoss book , Packt asked me if I would be interested in reviewing one of their fresh Drupal books, they first suggested a book on Theming but but I opted for the MultiMedia by Aaron Winborn one as Theming really isn't my cup of tee

It took me a while to get the book finished , mostly because of other priorities that kept popping up and being ill for the first week of the year .. but I finally managed

The Drupal Multimedia book , gives a good overview of both Images, Audio and Video and dares to think beyond current MultiMedia. With a zillion possible modules to choose from when starting to build a Drupal site it is often difficult too find the best module for a task, different modules have similar functionalities and features. Aaron saves you the trouble of figuring out which modules are suited best for what task by discussing. For each media type he discusses which module fits best. However , sometimes he opted to discuss a Drupal 5 module that wasn't ported yet to Drupal 6, so you might have to seek for alternatives depending on your Drupal version.

For one of my sites I used the Flickr module that now seems to be outdated, the book pointed me to the Embedded Media Module , so the book was well worth the time spent with it and I`ll have all of my Drupal Hacking friends read it, as it will save them time figuring out which modules to use.

Next up , the Learning Nagios book , but guess I won't be starting to read it before Fosdem .. :)

As I don't really use twitter apart to microblog but rather as an Instatn Messaging tool (why those people don't use IRC or Jabber remains a mistery to me wheel.reinvent :( )

I figured I could abuse it to announce posts on my blog, lots of people seem to be doing this so there had to be an easy way to auto publish them ..

The wonderful Drupal community seemed to have the same idea and therefore created the Twitter Module

A big fat warning however when you start using it.
The default values the module proposes for a tweet is :

New post: !title (!url)

Which results in something tinyurl doesn't really translate well..
(As you can see in this tweet)

So remove the brackets , or have some broken links to deal with :)