.' TO$;\
                          /  : TP._;
                         / _.;  :Tb|
                        /   /   ;j$j
                    _.-"       d$$$$
                  .' ..       d$$$$;
                 /  /P'      d$$$$P. |\
                /   "      .d$$$P' |\^"l
              .'           `T$P^"""""  :
          ._.'      _.'                ;
       `-.-".-'-' ._.       _.-"    .-"
     `.-" _____  ._              .-"
    -(.g$$$$$$$b.              .'
      ""^^T$$$P^)            .(:
        _/  -"  /.'         /:/;
     ._.'-'`-'  ")/         /;/;
  `-.-"..--""   " /         /  ;
 .-" ..--""        -'          :
 ..--""--.-"         (\      .-(\
   ..--""              `-\(\/;`
     _.                      :
                            ; freki 0.7 
21 is only half the truth ...
freki design changes
Another day, another bugfix and feature session. freki now has a better overview (articles). The old system was a little clumsy and screwed up when faced with strange situations. Therefor, the article overview now includes ALL articles ever written. ;)

This may seem stupid and not ideal, but for the time being, I am satisfied so far. Because of this changes, I allow myself to increase the version to 0.7. Have fun!
Back on ArchLinux
After some time of fiddling around with Slackware now, I decided to switch back to ArchLinux on my main machine. Partially, because at some point it ended being fun searching for dependencies on Slackware, and partially because I missed pacman. slackpkg did a really good job on Slackware, but could not resolve dependencies.

I am not 100% confident that this switch will be permanent. Since Slackware was my first distro to touch about 16 years ago, I learned to really love it. There is much nostalgia involved in this decision. I like the Slackware community, I like how Patrick Volkerding does things and I like the pure simplicity of it. But, as mentioned, then there is pacman ...

If someone ported pacman to Slackware (slackman ;) ?) I would be first in line to try it and switch back to Slack.
SlackwareARM + PiNOIR camera howto
I am on SlackwareARM on my Raspberry Pi 2 and have the PiNOIR camera connected to it. At first I thought it should be pretty easy to accomplish, but it turned out to be trickier than I thought.
At first, I couldn't find reliable information whatsoever, but after some more specific search terms I found a solution that worked.

All these steps are meant to be executed by root

Step 1 - download and install raspberry pi userland tools
cd /usr/src
git clone "https://github.com/raspberrypi/userland.git"
mkdir userland/build
cd userland/build
cmake ..
make install

Step 2 - apply permissions to devices
usermod -a -G video 
chmod 0660 /dev/vchiq
chgrp video /dev/vchiq
echo 'SUBSYSTEM=="vchiq",GROUP="video",MODE="0660"' > /etc/udev/rules.d/10-vchiq-permissions.rules

Step 3 - Modify library paths
echo "/opt/vc/lib" >> /etc/ld.so.conf

Step 4 - create a file called /etc/profile.d/videocore-paths.sh and edit it like this:

# For root users, ensure that /opt/vc/sbin is in the $PATH.
if [ "`id -u`" = "0" ]; then
echo $PATH | grep /opt/vc/sbin 1> /dev/null 2> /dev/null
if [ ! $? = 0 ]; then

# Add videocore utilities to system $PATH:

Step 5 - make it executable
chmod a+x /etc/profile.d/videocore-paths.sh

Step 6 - modify config.txt
echo "gpu_mem=128" >> /boot/config.txt
echo "start_file=start_x.elf" >> /boot/config.txt
echo "fixup_file=fixup_x.dat" >> /boot/config.txt
echo "disable_camera_led=1" >> /boot/config.txt

Please make sure that your config.txt has the new values in it and then reboot and enjoy :)
If everything worked, you can try:
raspistill -o test.jpg

to test if it really worked. If it tells you something about permissions, make sure your user is in the video group.