Kahel OS – A Review Without Booting

There are becoming more and more distros that are based on Arch Linux, with some so heavily “based” that they actually use Arch packages. This is fun for me as it means that I can now break multiple distros in one go, bringing “Allan broke it” to a whole new level.

One such distro is Kahel OS. Breaking through the market-speak on their website, it basically claims to be a newbies distro that has all the features a guru expects. It comes in Server, Desktop and Light Editions. I decided to try the Desktop Edition using the installer released on 2009-12-25. I installed using QEMU as I do not have a spare partition at the moment.

The install CD boots to a horrific orange screen [01]. After selecting the “install” option, you are greeted with bunch of kernel bootup text [02], followed by an Arch style boot process [03]. No graphical boot for this distro, so newbie friendly is a bit dicey already. Once booted, you are presented with a screen explaining why Kahel OS is good [04]. I suppose that was in case all that boot text was scaring us away.

Then we are actually installing. The installer is what I call ascii-graphical [05], although reverts you to text based screens as needed [06] (from that screenshot, you might notice that the answers are not necessarily intuitive…). Partitioning is done in cfdisk [07], followed by reselecting what type of filesystem you really want [08]. I decided for a single partition taking up the whole 4GB image I created and selected Btrfs for something new and given support for new filesystems is one of Kahel’s claimed features. I found it a bit strange that there was no warning about this filesystem still being experimental, but after some searching I found one hidden away on another TTY [09].

The “Install Packages” step goes straight to output from pacman [10], so there is no option to customize your install. The default install uses 3GB of space [11]. The package list is certainly interesting…. it installs the entire base, base-devel, xorg, xorg-video-drivers, gnome and gnome-extra groups. These are supplemented with a variety of other software including banshee, brasero, gnote, firefox, go-openoffice, xsane, and lots of fonts. I do not understand the use of gnote over Tomboy given mono is already installed for banshee. The SVN version of gtkpacman is installed for graphical package management. Other software choices are plain strange, such as libgpod, which is not required by anything else and is fairly useless on its own.

Finally, the installer takes you through some basic setup [12]. This distinguishes three types of users; root, administrators and normal. An “administrator” appears to have been given permissions to perform a variety of tasks via policy-kit.

Once you are done, you can reboot into your nice preconfigured desktop… but I could not. Those of you paying attention earlier would have noticed that I choose to have a single partition using btrfs. Of course, grub can not boot from that so that is a fail on my behalf. But a newbie friendly distro should have stopped me from doing that.

So, here is what I found different form Arch Linux without actually booting the system. There are a couple of extra repos enabled in pacman.conf. The listed Kahel OS repo does not exist yet. I did find a link to another Kahel repo, but it was empty. As a non-working repo breaks gtkpacman, package management is broken out of the box. Also the archlinuxfr repo is present but disabled, probably just so you can easily install yaourt.

Several packages are novel to Kahel OS. These are mainly for automatic configuration of the desktop and fonts as well as providing nice icons. The developers need to learn about makepkg.conf as they have not set their PACKAGER variable. Also, something strange is happening to their kahel-desktop-base-configurations package. It has 22 files, but “pacman -Qk” show that 11 of them are missing from the system so some installer magic has occurred. Not a great use of package management…

Overall, I am not sure what this distribution hopes to achieve. It seems that that it wants to provide a fully functional desktop after install and maybe it achieved that (I can not comment). But the installer is far from what is considered user-friendly, to the point that I do not think someone could achieve an install using it and not be able to do so with the Arch installer. Looking at screenshots on their home page, I can not see a major improvement graphically from a standard GNOME install. From all their “release announcements”, I am not sure that they know what they are trying to achieve either.

As an aside, of the 704 packages installed by Kahel OS, I built 80 (11%). So there is a lot of scope for me to cause breakage for unsuspecting Kahel OS users!

Screenshot index:

[01] – Bootscreen with lots of orange.
[02] – Boot text
[03] – Familiar boot-up from Arch
[04] – Market-speak
[05] – Ascii-graphical installer
[06] – Configuring timezone
[07] – Partitioning disk
[08] – Selecting filesystem type
[09] – Hidden Btrfs warning
[10] – Installing packages
[11] – 3Gb installed
[12] – Set-up

8 thoughts on “Kahel OS – A Review Without Booting

  1. Why even bother with Kahel OS? it’s lacking in so many area, just get Chakra in which the devs are also part of KDE.

    • Because I very much dislike Qt and KDE. That and I am not switching distro any time soon, so this was just out of interest.

  2. An easy to use distribution (read: easy for one who does not use computers very often and does not want to) should definitely have a graphical installer and be installable just in a few steps. I think Ubuntu does a good job with their installer.

  3. “This is fun for me as it means that I can now break multiple distros in one go, bringing β€œAllan broke it” to a whole new level.”

    This made my day πŸ˜›

    on topic: overall it doesn’t look too bad. Though firstly, the installation isn’t exactly newbie friendly, as the text based installer can be confusing for the inexperienced.

    Their choice of the colour (orange) is very bad (for the eyes).

    also looking at their screenshots (transparency), if they have compiz enabled by default, it could be a problem for older hardware (especially the ones with intel adapters).

    Though one positive thing out of this is that instead of being another distro based on ubuntu (we have millions of those), it is trying to be different.

  4. It would be much better if they declared that their installation cd’s are still in alpha/beta stage, like Chakra does :-/

  5. hm.. IMHO this review is rather unfair to KahelOS as Kahel OS has just been around for barely 3 – 5 months..

    but i agree with Flamelab…things would have gone much better if there was a alpha/beta stage..

  6. fplolz is right… it’s unfair to judge KahelOS on its early stages. But these comments may/will actually be good since this will help the KahelOS team to further improve on it.

    I think the team did not put in alpha/beta stages for the simple reason that it is a rolling release (where I think versioning is useless). The latest version is actually better than it was before Dec 25. That alone shows that the KahelOS team keeps on improving their OS. πŸ˜€

  7. Although your claim is valid, I love to see you really break those 80 packages for a month or longer and prove to the whole world you’re a god πŸ™‚

    Kidding aside, Sir Allan.. I believe you are a good person and also an innovator. What you’ve written doesn’t quite fit the character an influential character such as yourself is. It came to you that these people, the KahelOS team, are arrogant and self-righteous, where in fact they’re not if you’d just let the chance to know them better.

    But you focusing on that what you believe you abhor and want to correct, you’re slowly becoming it. Wouldn’t it be better to focus instead on the common values?

    You are an influence to a lot of people, particularly the younger generations. Please be responsible on that power, as all power corrupts. Respect begets respects.

    Open up a ‘good’ dialogue, I’m sure the team will listen to you. These are respectful people we’re talking about.