Language Selection

English French German Italian Portuguese Spanish

Review: Chakra 2013.02 "Benz"

Filed under
Linux

It's been a while since I looked at Chakra, so I was thinking now might be a good time to do that. Plus, KDE 4.10 just came out with a whole bunch of new features and fixes, so I wanted to check that out too. So this is the subject of today's review.

I've tried Chakra a number of times before. It was originally derived from Arch, but since a couple years ago it has been developed in a fully independent manner. It uses a "semi-rolling" release model, in which applications like Mozilla Firefox and other front-end features like KDE are updated on a rolling basis, while core system components are held to be more stable.

I tried this (64-bit version, as there is no 32-bit edition anymore) on a live USB system made through the "dd" command; due to Chakra now using the GFXBoot tool for booting, neither MultiSystem nor UnetBootin worked, and I didn't have any other data on this USB drive, so I was OK with using that tool. This review almost didn't happen because right after the boot menu, the message "invalid or corrupt kernel image" would come up.

rest here




More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more