Other articles

  1. Moving to systemd

    I'm back from Sweden, and while I was away, ELCE was held. The nice people from Free Electrons luckily put up all the conference videos in webm format, so whoever missed it can catch up. One of the first videos I watched was Integrating systemd: Booting Userspace in Less Than 1 Second, held by Koen Kooi, who I remembered from the time I used Openembedded on Openmoko devices.

    Some know that I like to show off my neat little Thinkpad x200s for its boot time; so far under 5 seconds (from bootloader to X) using Gentoo, OpenRC, and Enlightenment. I wanted to try systemd for a while but never really was in the mood to do the actual work. The video inspired me to actually give it a try now.

    Installing systemd is incredibly straight-forward, just read the gentoo-wiki articles and make sure you have your "init scripts" (or .service files in systemd jargon) ready. Enough talk, just let me finish with this: I was utterly impressed how well systemd works and I'm looking forward to it replacing all other init systems currently out there (including OpenRC which I actually liked). But look for yourself:

    read more

  2. Pyneo for Gentoo

    Something I wanted to do for a while, but never actually got started: Get pyneo supported in gentoo. So I finally wrote some ebuilds, starting of course with pyneod and its dependencies gsm0710muxd as well as python-pyneo. More to follow soon.

    The packages are based on the 1.32 tag in pyneo's git and pretty much identical to upstream, with the exception of the initscripts. My ebuilds replace them by proper gentoo-style initscripts that work well in openrc.

    How to use it

    Using this overlay is easy. Make sure you have layman installed, using the git USE-flag, and set up, e.g. as described here. After that you just have to add this overlay using:

    layman -o "https://raw.githubusercontent.com/tg--/gentoo-pyneo/master/overlay.xml" \
    -f -a pyneo

    That's it!

    Check it out on gitorious if you like!


  3. Bluez and the Keyboard

    I recently bought a nice little bluetooth keyboard. Being bluetooth based and supporting the standard hid protocol, I didn't expect any trouble at all.

    But I was wrong.

    After charging the keyboard and putting it in pairing mode, I tried hidtool scan - but it didn't find it. I checked my other bluetooth devices, and they were found - but they also found the keyboard.

    Long story short: Turns out it was a bluez bug - thanks to Pacho Ramos for the hint.

    As all howtos and so on only cover some GUI frontends for Gnome and KDE, as well as the old (and deprecated) hidd, it wasn't that trivial to get the keyboard to work even after it was finally discovered by hcitool.

    jhe in #bluez-users on freenode gave me a brief description on how to do pairing without all the stuff mentioned above:

    1. Install bluez with USE="test-programs" set
    2. Set the device to pairing mode
    3. Use hcitool scan to get the device address
    4. Run simple-agent hci0 $(hid device address)
    5. Enter PIN on both sides, PC first, Keyboard second
    6. Run bluez-test-input connect $(hid device address)

    After that it works fine.

    Using a frontend might be more viable though, seems ...

    read more

Page 1 / 1