Back to basics with Kwort 4.3



I do not think I have ever installed the Kwort distribution before. It's one of those projects I think about trying when a new release comes out, but something else has always come along to steal away my attention. Last month, during a quiet period, I decided to download the latest release of Kwort, version 4.3, and give it a try.



According to the project's website, " Kwort is a modern and fast Linux distribution that combines powerful and useful applications in order to create a simple system for advanced users who find a strong and effective desktop. Kwort is based on CRUX, so it's robust, clean and easy to extend. "



The project's website had the following to say about Kwort 4.3: " As always we remain fast, stable, and simple and now we have grown up a little to include a lot of Linux firmwares available for tons of devices. As usual, everything has been built cleanly and from scratch. "



The distribution is available in a single edition and is designed to run on 64-bit x86 computers exclusively. The installation media is relatively small, just 470MB in size. Booting from the project's installation media brings up a text console where we are automatically signed in as the root user. Instructions for installing the distribution are displayed on the screen and we can cause these instructions to be shown again at any time in the future by running the "helpinstall" command or by pressing CTRL-D.



The installation instructions let us know that we will need to do a bit of manual work to get a fresh copy of Kwort up and running. At times the instructions are sparse and I recommend reading the on-line copy of the installation guide as it fills in some of the blanks. Kwort does not have a system installer and so we find ourselves using command line utilities to partition the hard drive, format disk partitions and mount the areas of the disk where we plan to install the distribution. We then run a command called "pkgsinstall" which copies the base operating system onto our waiting hard drive. We then need to manually edit our fstab file and the system's configuration file, rc.conf, to make sure it has our correct keyboard layout and time zone. Another command sets the root password. Next, we need to decide which boot loader to install (LILO or GRUB), along with supporting packages, and run commands to install the boot loader and configure it. Again, the installation steps are a bit vague here and I recommend visiting the on-line documentation to see examples of how best to proceed. Assuming we successfully get a boot loader installed we can then reboot the computer and begin exploring Kwort.



By default, we find ourselves navigating a text console interface. Kwort ships with the usual collection of command line tools, manual pages, a copy of the GNU Compiler Collection and version 4.1.13 of the Linux kernel. Kwort offers users the SysV init software and, at first glance, a very minimal experience. However, we can run the "startx" command from the text console to gain access to the Openbox window manager. Openbox is presented with a task switcher and system tray at the bottom of the screen. We can right-click on an empty region of the desktop to bring up an application menu.



Looking through the application menu we find a short list of programs. The Chrome web browser is included along with the Transmission bittorrent client and the Lftp simple FTP client. The Leafpad text editor is included along with a calculator, the Audacious audio player and MPlayer. Kwort includes multimedia codecs for playing our audio and video files. The GpicView image viewer is included along with the Midnight Commander file manager. What I found strange, and frustrating, was that several programs were listed in the application menu which were not installed and trying to run them would result in an error saying the file was not available. LibreOffice, the PCManFM file manager, the Openbox configuration application and the GTK configuration program are all listed in the menu, but do not exist on the system. Further complicating things, I could not find these applications in the distribution's software repositories, and I will come back to my experiences with Kwort's package manager shortly.



The default installation of Kwort is fairly minimal. The distribution used just 20MB of RAM when sitting idle at the text console and took up approximately 1.4GB of hard dive space. Later, I found running Kwort's default graphical environment, Openbox, caused the operating system to use just 45MB of RAM. I tried running Kwort on a physical desktop machine and in a VirtualBox virtual machine. Kwort worked fairly well on the desktop, though it was a touch slow to boot. In the virtual environment, the distribution would run smoothly, but would not take advantage of my display's full resolution. I wanted to install VirtualBox's guest modules to gain better integration, but Oracle's official modules could not recognize Kwort's environment and the distribution appears to not have any VirtualBox packages in its repositories. This left me with a somewhat restricted experience when running Kwort in a virtual machine. On the subject of hardware, at first when I started using Kwort I thought audio was not working. After a little poking around I discovered audio was, technically, working but the sound mixer available on the desktop was of limited use because the underlying ALSA mixer was turned down low. A trip to the command line allowed me to use alsamixer to raise the background volume and then fine-tune audio output using the desktop control.



Managing software on Kwort is accomplished using the distribution's kpkg command line package manager. At first I was a little confused by the utility because whatever command I passed it to (update, upgrade, install or search) would cause kpkg to immediately return without providing any output. With a little looking through the documentation, I realized there is a command for installing repositories and, until a repository is installed, kpkg does not do anything. The default repository file can be downloaded from the front page of the distribution's website. Once the package database has been downloaded and installed, we can fetch repository data. Then kpkg refused to work until I had manually created the directories under /var it would need to download and store package data.



At this point I found the repositories were fairly small. I did not get an exact package count, but I was unable to find much of anything in Kwort's repositories. I was unable to find LibreOffice, OpenOffice, VLC, desktop environments, AbiWord or a dozen other common packages. I did find a copy of the nmap security tool, but once it was installed nmap failed to run due to missing dependencies. Sadly, I was unable to even find a screen shot utility, which is why this review is so lacking in imagery.



Conclusions



At the end of 2015, I reviewed Arch Linux. At the time I commented that Arch's minimal and sometimes cryptic nature might not make it practical in many situations, but there are things I respect about Arch. Specifically, Arch keeps its users on the cutting edge of technology and, perhaps more importantly, the Arch Linux project has extensive, well written documentation.



Running Kwort was a little like running Arch Linux, but with older packages and virtually no documentation. An experienced user may be able to get Kwort installed by following the on-line guide, but beyond that point there does not appear to be much we can do with Kwort. I was able to get a graphical user interface running, edit text files, play multimedia files and browse the web. But there was no image editing, no screen shot tools, no productivity suite and not even a working graphical file manager. This made running Kwort a very limiting experience and the lack of integration with VirtualBox did not help matters.



My experience with the distribution was, at times, made more frustrating when I had to do things like drop to a command line to fix audio output or download the default software repository data. I'm not sure why repository data is treated as an add-on, it's not as though Kwort is desperately trying to save space since the project ships with the Chrome web browser.



I think my biggest frustration though, after having tried Kwort, is I suspect I am missing out on something, but simply do not know what because of the sparse documentation. There could be a great community repository of software or more useful tools or wonderful reasons for the design decisions made. However, I am not aware of them. For a distribution to be useful it needs, in my opinion, to either present its features in an easy to explore way (like Ubuntu) or it needs to have great documentation (like Arch Linux). Kwort, though it has merit in its lightweight nature, is not easy to explore and has very little documentation. Two factors I think will keep most users away from this minimal distribution. * * * * * Hardware used in this review



My physical test equipment for this review was a desktop HP Pavilon p6 Series with the following specifications: Processor: Dual-core 2.8GHz AMD A4-3420 APU

Storage: 500GB Hitachi hard drive

Memory: 6GB of RAM

Networking: Realtek RTL8111 wired network card

Display: AMD Radeon HD 6410D video card