Well, it’s that time of the year again, next week I’ll be flying to my beloved Ibiza.

Being an Internet/IT junkie, I don’t exactly “disconnect”; actually I like to read / dig / test some new topics while on holidays (and while I’m not at the beach / clubbing / sunbathing). So every year I go through a particular “checklist” in order to be sure I can connect to the Internet no matter what, here’s the list as of now:

I came across an annoying behaviour while trying to connect to a remote KVM hypervisor from a FreeBSD GUI. virt-manager failed to connect to the server and showed the following error message:

In short, virt-manager tries to access to /usr/local/var/run/libvirt/libvirt-sock because it is compiled with a /usr/local PREFIX on FreeBSD. Of course they didn’t plan anything on a plain text configuration file. I figured out this has to be configured in GConf, for example using gconf-editor, simply replace:

I recently borrowed a Dell machine at work, model E4300, a nice little laptop whose graphical display is done by a much common Intel 4500MHD. While the card worked out of the box for a classical 2D display with a fresh FreeBSD 10.0 install, I noticed that DRM/DRI (in short, 3D) wasn’t available; I knew it was somewhat related to the new KMS/GEM infrastructure, so I began a few searches and found those useful resources:

A while ago, I had my ${DAYWORK} workstation running NetBSD, and honestly, it did pretty well. Things began to become more painful when there was no more DRI acceleration with the radeon driver, it then did an okay-ish job, but the overall desktop became somewhat laggy.

It was told someone was working on porting KMS/GEM, that was more than a year ago, and as of today, that work -and I guess it is not an easy one- isn’t mature enough to be used as a workstation, I need my desktop to run various tools, and not only terminal-based ones.

A while ago, I had my ${DAYWORK} workstation running NetBSD, and honestly, it did pretty well. Things began to become more painful when there was no more DRI acceleration with the radeon driver, it then did an okay-ish job, but the overall desktop became somewhat laggy.

It was told someone was working on porting KMS/GEM, that was more than a year ago, and as of today, that work -and I guess it is not an easy one- isn’t mature enough to be used as a workstation, I need my desktop to run various tools, and not only terminal-based ones.

Ok, je vous l’accorde je poste pas des masses. MAIS ! je n’écris pas moins. Et je le prouve.

J’écris depuis plusieurs années pour le vénérable GNU/Linux Magazine France, ces articles, je les propose sous licence Creative Commons BY-NC-ND, cela signifie que 4 mois après leur parution dans le magazine, moyennant une rémunération moins importante par article, ces derniers sont publiquement et gratuitement disponibles en ligne.

Comme je ne suis pas certain d’avoir exhaustivement listé les articles disponibles ici, voici les liens directs vers les articles récents, et n’hésitez pas à vous perdre dans les milliers d’autres contributions !

Comme je l’expliquais dans le post précédent, je suis passé chez SFR/neuf avec un forfait fibre. La box de l’opérateur, la neufbox donc, ne supportant pas de mode bridgé, quelques opérations sont nécessaires à une intégration cohérente dans votre réseau domestique.

Je me suis grandement inspiré de cette excellente documentation pour réaliser le bypass de la neufbox, cependant plusieurs éléments du tutoriel ne sont plus d’actualité. Je ne rentrerai donc pas dans le détail théorique puisque l’article de neufbox4.org est parfaitement explicite, mais focaliserai sur les méthodes à mettre en œuvre pour faire rentrer votre neufbox dans votre réseau local.

Il y a deux ans ½, je m’extasiais sur le “fibrage” de mon immeuble par Free. Naïf, je me disais à l’époque que l’Appel n’allait donc pas tarder, que le plus dur était fait, que bientôt oui bientôt, j’allais bénéficier des tuyaux de Free Infrastructure en utilisant la lumière. Naïf iMil, eternel naïf.

Régulièrement depuis cette date, j’appelle. Tous les deux ou trois mois. Et on me dit d’attendre. Que ça va plus tarder. Et j’attendais.

It’s been going on in my mind for a while, and I finally dove into Android development. As always when I put my hands on a new language / system, I had a basic need; this time I wanted to develop a simple init system that would resist my various ROMs flashing, i.e. a program that would not be located in the /system partition of the Android OS, but instead would be a package, an apk, that would read init scripts from the sdcard.

Considering latest Google Chrome’s bugs with Tweetdeck, which I use a lot, I decided to switch back (until next time) to Mozilla Firefox. That was anyway a move I wanted to do as Google is gaining too much knowledge about me…

While restoring my various logins and passwords on Firefox, I leaned about Firefox Sync, but most of all, about the ability to run my own Sync server.

While there’s a good official documentation on how to achieve this, I heard that ownCloud has a plugin for that. And as I wanted to give that software a serious try for a couple of months, that was the way to go.