Another thing that broke in my Arch install was my /dev/dvd /dev/cdrom symlinks.

However, this was an intentional “development” decision. This was the reason and I think the Arch KISS principle was the justification.

Quite how removing something that provides seamlessly functionality without adequately publicising that you have made that change keeps anything simple is beyond me.

What would be simple is to typing up a News post and slapping it on the Arch Linux frontpage – how long does that take? Adding a message to a .install script is not enough.

Wait, I’ve just had an awesome idea…

Oh, by the way, the fix I used, in case you end up here looking for one is:

# /etc/rc.local: Local multi-user startup script.

symlinks=(cdrom cdrw dvd dvdrw)
for device in "${symlinks[@]}"; do
        [ ! -h /dev/$device ] && ln -s /dev/sr0 /dev/$device

Since I’ve missed 5 years of Linux advances I figured it would be better to get caught up before I started installing Arch on my Netbook.

I decided the best way to do this was just update my Arch desktop and fix whatever broke. Turns out it wasn’t all that much.

Muting with unexpected results

Sound died on my Arch desktop sometime ago. Since I have an onboard and separate SB card I thought maybe it was a driver conflict. I spent several evenings, already exhausted from work, tinkering with various things but after much googling and reading of the Arch Wiki ALSA page I was still clueless. Then, I cracked it.

This breakthough was achieved through poise, precision and audacity. Basically, I sat down one night and said “Right, I’m fixing the sound tonight.” Starting from scratch I opened the Arch Wiki ALSA page and read it from top to bottom, word for word, no skimming.

I very quickly spotted this:

Some cards need to have digital output muted/turned off in order to hear analog sound.
For the Soundblaster Audigy LS mute the IEC958 channel.

Weird. My previous investigations had reminded me of the make and model of my card and I’d also read about what all the various channels are for. It’s worth noting that at one point I was paranoid I had my speakers plugged into the wrong jack so I check all that out too.

Anyway, this sounded promising. I launched alsamixer, previously in which I had diligently unmuted ALL my channels, and looked for what might be a digital channel. There was one called PDIF. I tabbed over to it and pressed “m”.


I am not an elephant

I use mpd to play music. I like the simple interface and lack of super bloat. I like Sonata as a front end. I installed Rhythmbox recently and the dep list gave me the 🙁

Once sound was working again I tried to use mpd to play some songs. Nada.

This time, though, having learned from my previous mistake I went straight to the wiki and read carefully.

The stock Arch mpd.conf had been heavily modified since I set it up so I migrated my settings to the new file format while following the wiki. I quickly realised that at some point in the past I’d deleted the ALSA output section in favour of an http streaming section. Genius. I later realised I’d done this remotely via SSH from work to get some Firefox extension working or something. I have a very visual memory, which explains why I had no recollection of ever having touched it at home.

Last but certainly not least

This pissed me off. This is typical developers sticking to “rules” when it seems to suit them even if it contravenes reasonable expectation or logic.

I won’t tell the whole story but basically I wanted to mount partitions in Thunar. Permission to do this is controlled by udisks (I think) and managed thorough policykit now. Arch ships with great polkit defaults that most people won’t need to change.

However, the rule that allows any user to mount a partition requires the user to give a password. You may know that for polkit to ask you for that password you need something called a User Authentication Agent. There are two main ones: polkit-gnome and polkit-qt.

Obviously, the basic installs of gnome and kde depend on these packages respectively. Not so with XFCE! Oh, no, no! Even though it means that Arch’s perfectly sane polkit defaults are impossible to implement without it, the dependencies for Arch’s XFCE packages do not include a User Authentication Agent.

What’s worse is that you have an Arch Dev on the forums basically telling people they’re retarded whenever they can’t get this to work and smugly telling them to install polkit-gnome.

The Policykit package should depend on a User Authentication Agent. That’s a simple fact. However, because there is a choice of two and Arch would never be partisan, it depends on none.

There’s not even an .install script to warn you. Instead polkit-gnome is an optional dependency for Thunar…

I don’t spend loads of money on myself. I’m the sort of person that hates to spend money on something I later regret.

This worked out well recently when it allowed us to buy a house. Not out right. Just most of the deposit.

So, since it’s been a pretty full on six months I treated myself to an Asus eeePC 1015PX.

My main reasoning behind this was I spend about an hour on a train a day and a Netbook seemed a good way to maybe do something productive.

Needless to say I wiped Windows 7 off of it and installed Arch Linux.

At the moment it is set up just a basic XFCE desktop environment but I hope to switch to something like Awesome for true portability. Touchpads and trains don’t get on.

I’ve basically spent the last few weeks trying to get to grips with power management and drivers. Riveting, eh?

I’ve loved it.

You might have noticed some pictures of a hairy guy with a small baby boy on the blog recently. That’s me and that’s my son.

His arrival has been a life changing experience and, like all life changing experiences, people tell you it’s life changing till they are blue in the face but you never really realise how life changing it is until it happens to you.

Up until just before our boy was born I plowed about 80-90% of my life into MMOs. That started in about 2007 when I took a break from playing with Linux, which had been my main hobby from about 2003. At that point I was very active in the Arch Community and had just been accepted as a developer. Odd time to walk away!

Anyway, I barely touched my Linux installs in the intervening 5 years but my interest has been rekindled, my boxes have been pacman -Syu’d and a brand new netbook has been saved, in everyway, from Windows 7.

My return to the world of Linux has quickly proved to be all to familiar. By turns hugely productive and rewarding yet also face punchingly frustrating.

So, because Linux would literally be nothing without the Internet to support it, it’s incumbent upon me to share my experience in the hope of saving someone else an enormous ball ache.

Without further ado.

I don’t like the new Gnome either. I had been enjoying Gnome but after 3 was released I swapped back to Xfce.

However, one app which is inexplicably hardcoded to work with Nautilus is Dropbox.

I followed a quick guide here to get it working with Thunar but it kept giving me an error:

Thunar: Unknown option --no-desktop

Taking a look at the suggested wrapper script we see:

exec thunar $@

It’s passing thunar multiple options. So, a quick bit of trial and error gives us:

exec thunar $2