I’ve now got CrunchBang installed on my main desktop machine and I’ve been using it for a day, Maybe it’s a short length of time to review a distribution but I feel with my past experiences with numerous distros will help me get to grips with a new one quite quickly. Some of you may know, after being a Ubuntu user for well over a year I decided to move back to Debian and became quite critical of Ubuntu for its rash decisions regarding design and key choices. My dislike is not centred purely on Ubuntu, I remember one time where I had a near fit at using a OpenSUSE KDE 4.0 Live CD as I couldn’t switch off the default sound scheme, but that’s for another post. Back to the review…

CrunchBang Linux promotes itself as a lightweight version of Ubuntu, unlike Xubuntu‘s XFCE desktop they’ve decided on using OpenBox and a few key programs from other desktop environments, like Thunar and Lxpanel.

My previous experience of the *box window managers have been with Blackbox during the very early days, when Enlightenment was all the rage and most distros used FVWM95, so checking out Openbox will hopefully be a refreshing blast to the past. My main concern was compatability, a lot of applications out there depend on certain features of the desktop environment. I left all my expectations at the door and decided to grab the Live CD and have a 10-15 minute play to see if everything works as expected and that it actually works on my slightly quirky setup.

The Live CD / Installation media is mirrored on a few sites, as it’s only a “baby” distro it’s not been picked up by the mainstream mirrors, thankfully, a few people in the community had offered some space up to the project and finding a local, fast mirror isn’t that difficult. As with all Ubuntu style Live CDs, it was a simple case of burning the ISO to a disc and rebooting the machine. I’m not sure if this is a feature of all new Ubuntu discs now, but the ISOLINUX menu had a option to check the installation media for errors, this would save you quite a bit of time if you suspect dodgy media.

The boot was quick, quicker than I expected. Usually with Ubuntu CDs I pop the disc into the drive the slip off to make a cup of tea and head back in time to get the last second or so of the desktop booting. This wasn’t the case with CrunchBang, after returning from a delightful brew making trip I noticed that the desktop was loaded and the default conky panel on the right side informed me that it’s been booted for about 5 minutes. So, boot speed, even from the CD it’s nice and quick.

To a user who has been brought up on the GNOME or KDE environments the initial desktop may take a second to sink in, by default it comes with a minimal panel and system information pane on the right side of the screen and nothing more, no desktop icons or fluffy applications menu, just a basic desktop. Right clicking anywhere on the desktop brings up the system menu and the list of applications. The default install gives you a nice range of applications, some you’ll never use, others are dire essentials.The default includes a few keynote applications:

• Firefox 3.0.4
• Pidgin 2.5.2
• Rhythmbox 0.11.3
• Skype 2.0
• Gwibber 0.7.2
• GIMP 2.6

A few more are available, and a full list can be found on the CrunchBang wiki. Needless to say I was impressed, not only had they selected reasonable defaults but as the distribution is based off Intrepid it had the latest and greatest versions available. Skype is a interesting nugget in my opinion, possibly being the only QT application in the default installation. I do understand that lots of people use Skype for VOIP, but maybe they should consider including another application like Ekiga.

So, I have my desktop running as a Live CD, time to see how it fayred in real world usage. I can happly say, after a good hour or so usage I didn’t feel restricted by the choice of desktop environment, Openbox is low key but quick and powerful. I decided after just a few hours usage to commit to this distro, ditching my current Debian Lenny install.

The installation of CrunchBang was nothing really spectacular, It’s a standard Ubiquity installer which does it’s job very quickly. A few quick selections and the dreaded disc paritioner screens and you on your way. Installation took about 10 minutes on my machine and felt a little quicker than previous Ubuntu installs, but I put this down to a little bias on my part. Rebooting the machine brought up a standard GRUB menu and I happly noticed that it detected my existing Windows installation and put the relative entry in. Again, the boot was quick and my machine boots to the desktop in under a minute.

So, here comes the negatives. A few minor issues have bugged me since i’ve started using CrunchBang, but nothing show stopping. So to save time I’ll just put them down as bullet points:

• xcompmgr seems to have a “dicky-fit” after a few hours use, making all window focus go out of the window. Disable/enable of Compositing fixes that.
• Tray Icons are hit and miss to what actual colour they use for their background. In my case with the “Fawn” gtk theme you get either a brown or beige background, which looks a little messy. Not really a distribution problem but still annoying.
• Restarting Conky seems to paint over the entire desktop for no reason, causing the Windows-esq issue when you have to use an existing window to get the desktop to repaint.
• By default, the xserver won’t detect 1280×1024. Simple fix of modifying the Xorg configuration but initial boot of the Live CD can be annoying with a mishmash resolution.

As I said, the negatives are MINOR. Really, really minor. CrunchBang was designed as a “2nd – 3rd” distribution for users, so it targets the section that are more than happy to have a twiddle with the system configuration and the thought of text only configuration doesn’t phase them. If you fall into this category and you’re looking for a lightweight desktop distribution then i’d suggest you grab a copy of CrunchBang and give it a whirl.

My first step was to get it working on Windows, I plugged in the modem on my old Windows PC and followed the numerous (and strange) online prompts to setup the software. After a lot of beeping, detecting new hardware and other jiggery pokery, I was presented with the Three Modem Manager application. The modem manager is a simple too that enables you to run the “dialup” connection through the modem. I whipped open the setup manual which informed me that no other setup was required bar setting up the software. So I clicked “Connect”…

… and it failed?

According to the tool I had to check my settings to see if they’re correct. This is a fresh setup of the tool, why would I need to check the settings when Three’s own guide mentions theres no setup needed. After 10-15 minutes poking around in the settings menu I finally threw in the towel. Sod it, I wanted to run this thing on Linux anyway so why am I putting myself through the pain?

Linux is, well, the way it was supposed to happen. I plugged in the stick and straight away I had numerous devices available, the “CD-ROM drive” for the drivers, the MicroSD reader, and the “tty” ports for the actual GSM modem. At this time I could of gone the route of setting up Gnome PPP and related tools to dialout to the provider and start using my new fancy net connection, but I’d heard that Network Manager 0.7 had the features to use 3G/GPRS built in without any extra settings. I decided to investigate the new version of Network Manager.

After much digging around on the ‘tubes, I finally found a Debian repository containing a build of the lastest Network Manager SVN. A little apt pinning and installation later I had the new version of the tool install. I browsed the existing menu and found a new option: “Auto connection to 3G/GPRS” , I selected the option and it connected.

I have to have a little moment to reflect here, “Mobile Broadband” is a new fad at the moment for most telecoms providers worldwide, so you would expect the Linux software support to be a little sketchy and buggy, but as it turns out the Linux method is alot simplier and easier to use. I’m not sure if I was missing anything obvious in Windows, but isn’t this stuff just supposed to work?

So, signed on to 3G I decided to give it a run for it’s money. I’m running these tests at 1:08am so it maybe a little bias, as I doubt many people would be actually using the APs at this time. I seem to be getting a variable speed of about 1-2mbps, and 150kbps upstream, not bad at all for a mobile provider. The documentation mentions that you should expect up to 2.5mbps, not the 7.2mbps advertised on some sites, all in all Three do a good job of pre-warning you that the speed on the box is not always what you get.

So far I’m happy with it, I’ve had a few minor issues with the stick not registering on the network but I’m not sure if this was down to my settings or just a small outage. I’ll post a guide in the next few days on configuring Debian up for Network Manager 0.7 and setting it up to work with the E160G.