Slax 5.1.4 - Your Pocket OS

Slax recently released version 5.1.4 of their amazing "pocket os" and since it had been almost a year since our last look, we thought we'd better find out what 5.1.4 was like. Much like its predecessor, it has a whole lot chocked into a small kde-based download. At 192 mb, is it worth the download?


Slax's homepage says it better than I would. To quote them,

"SLAX is fast and beautiful Linux operating system which fits on small (3.14") CD-ROM disc. It runs directly from the CD (or USB) without installing. The Live CD described here is based on the Slackware Linux distribution and uses Unification File System (also known as unionfs), allowing read-only filesystem to behave as a writable one, saving all changes to memory.

Imagine the ability to boot your favorite Linux distribution whether you are at home, at school, or at work. Imagine walking on the street and carrying the only thing you needed in life - the 8cm compact disk with your Live Linux CD. Wouldn't you want to experience such a feeling? Smiling "

Well, "the only thing you need in life" might be a bit of an exaggeration, but perhaps it might be the only thing one needs in computing. It's a complete os featuring all the basic requirements: surfing, emailing, instant messaging, connectivity, office, image viewing and file manipulation all sitting on the wonderful performing base of Slackware Linux. Slax comes with a 2.6.16 kernel, xorg 6.9.0 and a light version of KDE 3.5.2. In other words, it's an updated small portable version of Slackware.

Booting slax is as easy as popping in the cd and rebooting your computer. The default configuration worked great here, but there are many "cheat codes" available and found by depressing F1 at the boot screen. Booting progresses with the output displayed in the bottom portion of the screen while a nice image of a shamrock dresses it up at the top. At the end of this process, one is taken to a login screen. Instructions for logging in and gui startup are displayed as well as instructions for some basic configuration. Startx starts the gui at 1024x768 with vesa drivers and xconf will start an autodetection of your graphics system for perhaps enhanced display and performance. Also noteworthy from this same screen is the command for "slax-install." The screen states that at this time it "still doesn't work," but it alludes to future capability.

        

The gui starts with a customized kde splash and consists of xorg 6.9.0 and KDE 3.5.2. The slax version is quite scaled down as evidenced by the size of the iso, but it doesn't seem so by looking at the apps. As stated, there are apps for office work, connectivity and commuications, and even image viewing. There are tools for system configuration and monitoring as well as file manipulation and multimedia use. I think their choices in slimming down the kde desktop seem quite intuitive. The desktop itself is attractive featuring a customized wallpaper and panel. In the panel one can find quick launchers for konqueror, kopete, kmplayer, and juk. In the systray sits a connection monitor, locale selector, kmix applet, and krandrtray. Desktop icons are Home and System.

        

The games list consists of kbounce, kbattleship and patience. The graphics menu contains kuickshow, kpdf, and kolourpaint. Your office choices are kpresenter, kspread, kword, and kontact.

        

Multimedia applications include kaudiocreator, K3B, KMpalyer, juk, and KsCD. For the internet and communications are konqueror, remote desktop setup and browsers, Kppp, KWiFiManager, Akregator, Kmail, and Kopete. Some utilities you might find useful are kpager, kdeprintfax, Kate, Font viewer, Kcalc, kjots and knotes. Also included are some system configuration and monitoring tools.

        

        

There are also many modules available for download and installation from the slax site. Also on the site is a nice looking forum for discussions on all things Slax. In fact, the whole site is rather great looking, complete, and easy to navigate. It's always a nice touch and professional when a developer goes that extra mile to provide a wonderful web interface for use of and help with their distro - in many languages as well. Also of particular interest is their users' contributions of their screenshots. There are some great looking desktops shown there! All in all, Slax is a very respectable project and their distro is an amazing offering. The developers work hard to offer such a fantastic distro and provide timely updates. I've always like Slax quite a bit and this offering continues that tradition. It is definitely worth the download!

Related Links:



Some recent changelog activity includes:

v 5.1.4 SLAX (all editions) (6th of May 2006)

- added KDE 3.5.2, koffice 1.5.0
- updated alsa sound drivers
- updated to latest Linux-2.6.16 patches
- updated ndiswrapper and atheros wifi drivers
- fixed gtk2 config to use nicer default theme and font (firefox users are happy)
- fixed manual IP configuration
- dhcpcd now waits only 5 seconds to DHCP response
- removed noatun at all
- upgraded many libraries from Slackware current
- added new busybox binary to linux live scripts, this fixes some accidental problems with mounting union during startup.
- created official development module and kernel source module for SLAX
- added iocharset= boot option, to mount NTFS/DOS fs with your encoding
- added make_disk.bat to CD tree, to create USB bootable disk in windows
- properly remount ro disk device if SLAX is using data from it
- added FUSE and SSHFS filesystems, this will replace webconfig in the future
- cups set as a default printing system in KDE
- artsd doesn't autosuspend now, as this caused hundred of artsd processes
to be started on some machines (and in vmware), causing SLAX to swap or hang
- autoexec boot argument replaces "~" by spaces now, very useful if you need
to execute some command with parameters
- when autoexec is used, halt (powerdown) instead of reboot
- added openldap client and upgraded samba client files
- removed 2 useless videos from k3b extras
- and finally, added kernel boot splash image (no patches needed!). Use vga=normal boot parameter if you like the old text mode
v 5.1.0 SLAX (all editions) (31th of March 2006)

- added DejaVu fonts (Bitstream Vera with enhancements)
- added missing libmikmod libraries
- added missing libstdc++ libraries
- properly unmount device mounted by changes= boot argument
- added kbuildsycoca to kde-uselivemod to rebuild menu entries
- webconfig configuration size limit raised from 8MB to 28MB
webconfig now saves ALL modifications in the whole filesystem
- webconfig now uses direct access (uselivemod and dir2mo),
configsave and configrestore are deprecated and will be replaced by
changes= cheatcode soon.

v 5.0.8 Standard Edition (23th of March 2006)

- updated to Linux Kernel 2.6.16
- based on newest linux live scripts
- updated squashfs and unionfs kernel modules
- this fixes uselivemod and configsave/configrestore
- the rest remains the same, KDE 3.5.
- fixed bug in mounting of dos partitions (long filenames work now)
- slax now uses only 60% of RAM maximum for its filesystem - Slax Server Edition released, includes Apache 2, PHP 5, MySQL 5.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Great review of Slax, but slax needs architecture ?

Why architectural change for slax developers?

First, the distro runs in uncompressed codes and i486(i386 16bit to 32 bit with Fpu) platform, both are not ideal. Because some application software is 16 bit not efficient in 32 bit platform; but i486 instructions are not sufficient for i686 instructions for branch prediction in one clock cycle.

If run in tgz, same as in other tiny Linux, it will be 1/3 the length of 200 mb. And, the maximum requirement of dram will be 128 mb instead of 384 mb. If run in i386 platform Slackware Linux kernels are perfected for KDE 3.5.x already. Slax only has to pick and choose files in installation script.

The old fashioned concept of using hdd for configsave caused uncertainty due to windows partitions existed on whatever hdd has on the computer. If configsave is written on the wrong partition, it can not be retrieved on subsequent boot. The distro should insist on cheap USB key on most i686 computers. Anything older, Slax should think of floppy like Knoppix, only saving the config array codes not the entire file.

The concept of running Slax from cdrom is unthinkably slow. Copy2ram can be 128 mb of existing dram if run from tgz compressed files.

This kind of architectural consideration for livecd should be understood before wasting user time to live with imperfect scheme of things to come. Sad but true.

Footnote:
Configsave has to be in a compressed drive(Linux partition) to be always on the first physical partition of the hdd(residing behind windows files) and the whole drive can be retrieved into the dram(ramdisk) during boot.

Slax? Slow?

Have you actually USED Slax before? I've never heard someone call running from Slax slow before. I've used it on everything from 233 MHz K-6s to 633 MHz Celerons to Sempron 2800+s, and I have to say that I've never used a faster live-cd. I agree, if it was architecture specific, it might be faster, but that would break the wide compatibility users of the distro enjoy.

As far as using different compression, I'd have to say that I'll take the size of the SquashFS modules over the speed of tgz packages any day. The goal of this project is to fit a functional Slackware system into a footprint small enough to fit on a 210 MB cd. Tomas has done exactly that, and I have to say that to this day, I am amazed at the results.

And finally, I'll address your concerns with the amount of memory required... this is a function of KDE, not Slax in particular. I booted Slax on a computer with 60 MB of RAM just this morning. You can run Fluxbox in 128 MB of RAM, as well as XFCE. Tomas has created different Slax versions to address these concerns, and the modular design allows even further customizations with comparative ease.

Question is always how fast is fast in software ?

First, computation in L1 and L2 cache is always faster then in drams. Then ramdisk is always faster than prefetching from hdd or cdrom or USB flash drives(nanosecond delay consideration). Firmware(Asic) always runs faster than software in drams, because of clock speed.

So, architecture is the design of speed. If architecture is not correct then speed is sacrificed. If wait state is zero, your computation will really fly. But some newer computers have wait state of mid teens to mid twenties from cpu to dram or ramdisk. Larger L2 cache(upto 2 mb) can save 20% time doing computations in L2 cache like i586 write back or additional 20% gain in i686 branch prediction or dual core threads. Reading tables is much faster than adding or subtracting registers. Older computers maybe slow but the wait state may be only three clock cycles.

How data is transferred means a lot in speed. Compressed data has fewer bytes to transfer. Decompression software is very short and efficient(3x to 9x).

It is all mathematics, not human perception; so if you look at the way data is transferred, you know it is slower or faster. We like to help distros to consider speed by properly design their architecture for maximum speed in data transer rates.

Good point

I speak of things I know not of. I can see where you're coming from now, and I don't disagree. Unfortunately, I know that getting Tomas to implement such changes will be fairly difficult.

Tuxmachines is both hardware and Linux ?

Most distro lead developers are Linux first and logic fix becomes priority. I hope thry come to Tuxmachines to look at architecture considerations to strip down codes for maximum efficiency in functionality. Never try to work around some one's legacy codes. Go straight for the jocular, the function.

The Linux philosophy of shared modules is to do only one function at a time. Then you never will have conflicts, if you remove the module immediately afterwards. The concept of plug-ins and add-ons and extension are now the rage.

Ask Tomas to join us, there are codes out there he can share to restructure the Slax architecture.

Race among speed

The present Slax is by no means slow. But,we are in a jet era. Here,a fast object looks slower next day. And,we try to compete with speed.

Nobody gets to live life backward. Look ahead, that is where your future lies.