Language Selection

English French German Italian Portuguese Spanish

My Kinda Gal: KateOS 2.1

Filed under
Linux
Reviews
-s

KateOS 2.1 was released on June 21 and you knew tuxmachines was gonna take a look. Originally based on Slackware, KateOS has evolved into it's own wonderful distribution. Full featured, ready to go out of the box, and with updateos, KateOS could very well replace your current distro of choice. By way of introduction, I quote the site: "Kate OS is a Polish lightweight distribution. It is a multitasking operating system, which brings all that is necessary for: programmers, webmasters, administrators and home users. The most important Kate OS features are high efficiency, safety, reliability and low system requirements." It didn't take long to realize that Kate was my kinda gal. I was in love.

Lead developer Damian Rakowski states, "The first version of our system was based on Slackware only because i wanted it to be compatible with a standard i like. Some commercial companies are thinking about Slackware so Kate can also use those programs." But not being completely satisified with the package selection in Slackware, the developers set out to "to give to the community a lightweight distribution on which user can watch films, listen to favourite music, play games and surf the Internet. In Kate OS we want to create an efficient and 'lightweight' work environment. This enviroment can replace KDE and Gnome environments. We choose the software that will allow the same possibilities but require less system power."

Most important features of the system:

  • low hardware requirements means Kate OS can be still used on i486 machines

  • integration with PAM system, providing a homogeneous authorization environment
  • packages are in TGZex format, easy to build, don't have any dependencies between the packages, ready to update
  • BSD type, every user can understand and adapt them to meet his own needs
  • easy construction helps to take care of security
  • preferred and constructive graphical environment XFCE, which gives comfortable work in graphical mode, and conserves computer resources
  • preferred library GTK+, used by almost all applications in graphical mode
  • limited amount of applications in CORE Kate OS, programs are integrated with themselves and
  • libraries package of applications/tools, programming libraries

  • multimedia applications gives the possibility to enjoy goods of modern audio/video file formats
  • noncommercial distribution, doesn't depend from any institution, always FREE

Sounds good, let's take a look. I downloaded the KateOS-2.1 isos from their main mirror and it came in as fast as my dsl could handle. There are two isos available and the second is highly recommended as it contains many popular and useful optional packages. I burnt them onto cd and booted. The Slackware-style installation walks one thru the install (I chose all groups and full without prompting) and initial configuration. I had it install lilo with the boot kernel, initrd image and associated files on a floppy and booted my new os.

As per usual, the first thing I did was mount my archive partition and attempt the nvidia graphic driver installation. They built with no problems, then I edited the xorg.conf and loaded the nvidia module. I made a user account and home directory, then copied my .bashrc from gentoo. Root logged out, user logged in, and su'd to root. Then I wanted to test KateOS' remote package management system, called updateos, by installing kde.

Updateos is KateOS' original package management system. It downloads packages, groups or updates from a remote mirror and installs them with a single command. In fact one can execute a dist-upgrade much like found in apt-get. Damian explains, "Another huge drawback of [Slackware] was the lack of software used for remote updating. For the administrator its a huge disadvantage. Of course there are slapt-get and swaret but their funcionality can't be compared with our updateos or apt. For updateos everyone can make his own repository placing every package in one directory and executing a simple script." Well, I didn't test that advanced feature, however I did execute "updateos --install-group kde". Within no time I was xinit /opt/kde/bin/startkde!

    

The install cds come with xfce and fluxbox, but like kde, gnome is available to updateos as a group as well. To stay within their goals of providing a desktop solution requiring little resources, xfce and fluxbox are installed if one chooses the xap and xfce group during install.

    

Minimum Requirements are:

  • i486

  • 24 MB RAM
  • 300 MB HD (For ROOT and SWAP)
  • VGA card
  • soundcard (optional)
  • CDROM (bootable), floppy

Although system and packages are built for the i486 architecture, I detected no noticeable slowdowns at all on my i686. Startup and operation are practically flawless and I found the system and applications stable as a block wall. I tested KateOS longer than most test systems I review. Over the course of several days, I went about my usual computing routine, so I feel very confident with that statement. Multimedia applications worked out of the box and again were very stable. Please note that I used the -vo x11 in order to get the playback to appear in the screenshot rather than a blue screen. Using xv, one can enjoy fullscreen features.

For the small development team, this project is a labor of love. They enjoy all "operating systems especially Linux. Everyday we invent something new and debate on new ideas," states Damian. Being Unix administrators by day, and KateOS developers by night, their success could be attributed "to that fact we are working instead of just sitting and talking about nothing." Wonderfully talented, yet humble and accessible, Damian says of his team, "Of course sometimes it's hard work but we have our priorities. We are always planning our movements. Everyday we invent something new and debate on new ideas. Chudy (Peter) always thinks how to speed up the system. As the leader of the team i'm the one who sets the tasks and deadlines for everybody. Thanks to that we can control our work and make it more efficient. We can't forget about Neitt and Rakhi because the users owe them those beautiful wallpapers and splashes. Those two are brilliant graphic [artists] and without them Kateos wouldn't be the thing that it is now."

In the area of support, the site has documentation, forums, and information on their irc channel. Users can contribute by way of paypal.

Now to the most important issue: why KateOS? Why was this chosen as the name? Damian answers, "The name of our system has its origins in our friend's name, who was always complaining about it. She thought it was too common as many people in our country has that name. That was the main reason we named our system like that ... it's simple, nice and everybody knows it."

As usual, Screenshots in the gallery.

More in Tux Machines

Scrivener Writing Software has a Linux Version

In some ways, Scrivener is the very embodiment of anti-Linux, philosophically. Scrivener is a writing program, used by authors. In Linux, one strings together well developed and intensely tested tools on data streams to produce a result. So, to author a complex project, create files and edit them in a simple text editor, using some markdown. Keep the files organized in the file system and use file names carefully chosen to keep them in order in their respective directories. when it comes time to make project-wide modifications, use grep and sed to process all of the files at once or selected files. Eventually, run the files through LaTeX to produce beautiful output. Then, put the final product in a directory where people can find it on Gopher.

Gopher? Anyway …

On the other hand, emacs is the ultimate linux program. Emacs is a text editor that is so powerful and has so many community-contributed “modes” (like add-ins) that it can be used as a word processor, an email client, a calendar, a PIM, a web browser, an operating system, to make coffee, or to stop that table with the short leg from rocking back and forth. So, in this sense, a piece of software that does everything is also linux, philosophically.

And so, Scrivener, despite what I said above, is in a way the very embodiment of Linux, philosophically.

I’ve been using Scrivener on a Mac for some time now, and a while back I tried it on Linux. Scrivener for the Mac is a commercial product you must pay money for, though it is not expensive, but the Linux version, being highly experimental and probably unsafe, is free. But then again, this is Linux. We eat unsafe experimental free software for breakfast. So much that we usually skip lunch. Because we’re still fixing breakfast. As it were.

Details with Screen Shots Here

Anyway, here’s what Scrivener does. It does everything. The full blown Mac version has more features than the Linux version, but both are feature rich. To me, the most important things are: A document is organised in “scenes” which can be willy nilly moved around in relation to each other in a linear or hierarchical system. The documents are recursive, so a document can hold other documents, and the default is to have only the text in the lower level document as part of the final product (though this is entirely optional). A document can be defined as a “folder” which is really just a document that has a file folder icon representing it to make you feel like it is a folder.

Associated with the project, and with each separate document, is a note taking area. So, you can jot notes project-wide as you work, like “Don’t forget to write the chapter where everyone dies at the end,” or you can write notes on a given document like “Is this where I should use the joke about the slushy in the bathroom at Target?” Each scene also has a number of attributes such as a “label” and a “status” and keywords. I think keywords may not be implemented in the Linux version yet.

Typically a project has one major folder that has all the actual writing distributed among scenes in it, and one or more additional folders in which you put stuff that is not in the product you are working on, but could be, or was but you pulled it out, or that includes research material.

You can work on one scene at a time. Scenes have meta-data and document notes.

The scenes, folders, and everything are all held together with a binder typically displayed on the left side of the Scrivener application window, showing the hierarchy. A number of templates come with the program to create pre-organized binder paradigms, or you can just create one from scratch. You can change the icons on the folders/scenes to remind you of what they are. When a scene is active in the central editing window, you can display an “inspector” on the right side, showing the card (I’ll get to that later) on top the meta data, and the document or project notes. In the Mac version you can create additional meta-data categories.

An individual scene can be displayed in the editing window. Or, scenes can be shown as a collection of scenes in what is known as “Scrivenings mode.” Scrivenings mode is more or less standard word processing mode where all the text is simply there to scroll through, though scene titles may or may not be shown (optional). A lot of people love the corkboard option. I remember when PZ Myers discovered Scrivener he raved about it. The corkboard is a corkboard (as you may have guessed) with 3 x 5 inch virtual index cards, one per scene, that you can move around and organize as though that was going to help you get your thoughts together. The corkboard has the scene title and some notes on what the scene is, which is yet another form of meta-data. I like the corkboard mode, but really, I don’t think it is the most useful features. Come for the corkboard, stay for the binder and the document and project notes!

Community chest: Storage firms need to pay open-source debts

Linux and *BSD have completely changed the storage market. They are the core of so many storage products, allowing startups and established vendors alike to bring new products to the market more rapidly than previously possible. Almost every vendor I talk to these days has built their system on top of these and then there are the number of vendors who are using Samba implementations for their NAS functionality. Sometimes they move on from Samba but almost all version 1 NAS boxen are built on top of it. Read more

Black Lab SDK 1.8 released

QT Creator - for QT 5 Gambas 3 - Visual Basic for Linux Ubuntu Quickly - Quick and dirty development tool for python emacs and Xemacs - Advanced Text Editor Anjuta and Glade - C++ RAD development tool for GTK Netbeans - Java development environment GNAT-GPS - IDE for the following programming languages. Ada, C, JavaScript, Pascal and Python Idle - IDE for Python Scite - Text Editor Read more

Did Red Hat’s CTO Walk – Or Was He Pushed?

He went on to say that some within Red Hat speculate that tensions between Stevens and Paul Cormier, Red Hat’s president of products and technologies, might be responsible, although there doesn’t appear to have been any current argument between the two. Cormier will take over Stevens’ duties until a replacement is found. Vaughan-Nichols also said that others at Red Hat had opined that Stevens might’ve left because he’d risen as high as he could within the company and with no new advancement opportunities open to him, he’d decided to move on. If this was the case, why did he leave so abruptly? Stevens had been at Red Hat for nearly ten years. If he was leaving merely because “I’ve done all I can here and it’s time to seek my fortune elsewhere,” we’d expect him to work out some kind of notice and stay on the job long enough for Red Hat to find a suitable replacement. Turning in a resignation that’s effective immediately is not the ideal way to walk out the door for the last time. It smells of burning bridges. Read more