Language Selection

English French German Italian Portuguese Spanish

Stuck on Stux

Filed under
Linux
Reviews
-s

Stux Linux is an unique Linux distribution. Version 0.8.1 was released on the 7th and Distrowatch reports, "The new version is a quick bug-fix update to the new 0.8 series, which the developers launched a week ago. Some of the new features include: "Based on Slackware Linux 10.2 and Knoppix 3.7 for kernel and modules; all procedure and interfaces have been substantially reviewed; added boot option 'toram' to load STUX image in RAM and run from there; STUX Network Panel added - configure network for dial-up, ADSL, ethernet and wireless connections; STUX Media Center added; USB support enhanced; hard disk and USB installation process enhanced; created BitTorrent UI, also integrated in Firefox....""

It was quite the surprise to boot the livecd and watch a Knoppix init and hardware detection, being under the impression Stux was based on Slackware. However, this impression was correct. How did those developers come up with that idea? But the surprises don't end there. Wait until you see the desktop.

The default desktop environment is KDE 3.4.2. What makes this desktop unique is some of the customizations put in place. Granted most of them are mere KDE options, but how many developers have the courage to ship with them? Not so different is the gkrellm on the desktop in a transparent theme, nor the background of the famous blue-blend. Not so distinctive is the menu or even the windec and icons. Where the differences start are the panel arrangements. First is the launcher at the top of the screen, auto-hiding yet with a transparent background when visible. That in of itself may not impress, but it is also accompanied by the main panel at the bottom of screen with of course, transparency enabled, and also a few well chosen applets. The kasbar on the right, auto-hiding, as well as side-bar on the left were also something one doesn't encounter everyday in a distro by default.

        

It's different and refreshing in a way, however I think the main panel is a bit too cluttered. The cpu and memory monitors should probably be turned off and that functionality added to gkrellm, and that mixer is overkill as well. Most functions of a mixer are inoperative or not used very often in my case and suspect it may be so for many folk. That could at least be trimmed down if not removed completely. There is a mixer plugin for gkrellm as well and if stux is gonna have gkrellm on the desktop at boot, I say incorporate what they can into it. In addition, noatun has never been a very good application for me, I'm not sure I'd leave that applet either. But these are personal preferences and if installed onto the harddrive or saved the configuration I could easy change.

I was quite impressed with the Stux Control Center. From there one can configure various hardware devices, install software, and install the system to hard drive or even an usb key. It is different from other distro's control centers in presentation and functionality. Not only can you configure your system through it, but it is also an application launcher. It has several application buttons running down the right side as well as having a menu of clickable links. As stated I was quite impressed with it even if I encountered a few niggles.

I've been using Stux for a coupla days and I first began having issues when I attempted to use the control center to adjust my mouse settings so my scroll button would work. It wrote the new configuration and restarted X, but the system became quite sluggish and there was artifacting and visual corruption afterwards. I figured the scroll wasn't worth it, so I just rebooted to get the original default settings and performance back. But throughout the course of the day, surfing the internet, checking webmail, and trying to take screenshots and write this article, X has crashed out on me a few times and sent me out to the terminal. X always restarts, but it can be annoying when you haven't saved your work in a coupla paragraphs. However, the system seemed much more stable after a hard drive install. Your mileage may vary and you may not experience any negative issues with the livecd at all.

        

The greatest achievement in Stux I believe is their Stux Control Center as introduced above. It's unique appearance and the fact it opens upon start bring it into attention immediately. One of the functions it contains is a package manager. Besides the qtswaret found in the KDE menu, Stux seems to have its own package manager that can download Stux packages and install them to disk or ram. I decided to test the install to ram feature for the nvidia drivers, but alas I was met with a "not enough ram error." As my machine only contains 512mb of ram, my only recourse was to install onto harddrive.

        

The harddrive install is another unique interface with lots of nice options. There's a really nice description on the Stux site, but basically one clicks the harddrive target partition and check boxes for options. Some of these options include Install Current configuration which copies the root and etc partitions as they presently exist, format device, and install bootloader onto harddrive or mbr. There are buttons to launch qtparted or cfdisk if needed as well as option to create a boot floppy.

        

My experience with the harddrive install was mixed. I installed twice on two different partitions hoping to ascertain the most appropriate configuration of the installer. The first time the install itself went smoothly and I made a boot floppy to boot the system. It booted but locked up because of the "nv" driver bug, despite having edited the xorg.conf file for vesa from another linux install in order to avoid that. The fly in the ointment is that on every boot Stux/knoppix hardware detection is not only checking for new hardware each boot, it rewrites every config file previously edited. Not good.

The second install I unchecked "install current configuration" and it wouldn't even boot. It hung right after starting "multi-user" with an error about read-only filesystem. Ho hum.

So back in the original install, I tried to run the Stux package manager to install the nvidia drivers. It downloaded its nvidia package and tried to install it, however it errors out with the message something about the glx library missing. The kernel source was included, so I exited KDE and installed them using nvidia's installer/package. The Stux process edited the correct files however for use of the drivers upon reboot, indicating that it was just a problem with the package itself.

        

With the mixer and noatun applets big and bold and taking up much of the panel, it appears that Stux is trying to be an out-of-the-box multimedia system as well. In testing I found that xine could in fact play most of the video files I had on hand if it was in a standard video format such as mpeg and avi, further the win32codecs were available for installation through the Stux Packages installer. xawtv performs well after configuration of drivers and settings (as with any xawtv install), however I couldn't persuade xmms or kscd to play any audio cdroms. Flash and java weren't installed, but java was available through the package installer and installed without incident.

    

As far as applications, besides the full compliment of KDE applications, Stux is well equipped with many popular packages such as gimp, firefox/thunderbird, abiword and koffice, amule, gaim, xsane and qtswaret. There really aren't too many games, but there are several premier games or demos in available through the package installer.

        

So in conclusion, I think those Stux fellars might be onto a something a little different and out of the ordinary. As many people grow weary of the same ole same ole, Stux might have a chance to rival some of the big boys. They have some brave and bold default configurations that add to the user experience as well as wonderful original tools. Stux might need some more maturing and a bit more refining, but I predict great things to come of this project. If you're looking for something a little different, you just might become stuck on Stux. More Screenshots in the gallery.

More in Tux Machines

Sad News - Martin Schwidefsky

We are devastated by the tragic death of Martin Schwidefsky who died in an accident last Saturday. Martin was the most significant contributor to the initial s390 port of the Linux Kernel and later the maintainer of the s390 architecture backend. His technical expertise as well as his mentoring skills were outstanding. Martin was well known for his positive mindset and his willingness to help. He will be greatly missed. Read more

today's leftovers

  • This Week Twitter Taught Me: Thunderbird is Go, But Windows Text Editors are Not!
    Although it’s proving difficult to stay on (Linux related) topic, this series has proven a great success in only 3 weeks — so much so that I’m planning to launch three separate spin-offs! I mean, I might as well milk the franchise for all I can while the udders drip with goodwill, right? Keep an eye out for “This Week My Spam Folder Taught Me“, “This Fortnight a Disqus Bot Taught Me” (spoiler: bit repetitive that one) and, to serve the overlooked people-who-read-this-site-whilst-diving niche, “This Month Diving Taught Me”. I wouldn’t get your hopes up for the latter, though. I can’t swim, let alone dive…
  • Timetable Scheduler App For Linux
    Timetable is a scheduling app available on flathub repositories. The app is maintained by the Elementary OS team and thus it’s User Interface looks like its own native OS. Might look a bit out of place on GNOME, KDE, Cinnamon, etc but still yet the app works like a charm. Read on below to get more done with Timetable.
  • Juan Luis Baptiste : New docker images for upcoming mageia 7
    I have added new docker images for the upcoming mageia 7 release. Thanks to the latest work on our image build tools, the images are available in all architectures mageia 7 supports: x86_64 armv7hl aarch64
  • Manas and Marek: Improving Fedora release process
    Manas Mangaonkar (pac23) is working on the Change Management Tool, a tool for the Fedora Program Managers and contributors to propose, edit, and approve changes per Fedora’s change process. He was selected for Google Summer of Code 2019. We asked Manas a few questions as he prepares for his next three months working with Ben Cotton, his mentor for the summer.
  • Candy Tsai: Outreachy 2019 March-August Internship – The Application Process
    Really excited to be accepted for the project “Debian Continuous Integration: user experience improvements” (referred to as debci in this post) of the 2019 March-August round of the Outreachy internship! A huge thanks to my company and my manager Frank for letting me do this since I mentioned it out of the blue. Thanks to the Women Techmakers community for letting me know this program exists.
  • Ubuntu Weekly Newsletter Issue 579
  • Sony's Deal With Microsoft Blindsided Its Own PlayStation Team [iophk: "RIP Playstation"]

    Last week, the companies announced a strategic partnership to co-develop game streaming technology and host some of PlayStation’s online services on the Redmond-based company’s Azure cloud platform. It comes after PlayStation spent seven years developing its own cloud gaming offering, with limited success.

    Negotiations with Microsoft began last year and were handled directly by Sony’s senior management in Tokyo, largely without the involvement of the PlayStation unit, according to people familiar with the matter. Staff at the gaming division were caught off-guard by the news. Managers had to calm workers and assure them that plans for the company’s next-generation console weren’t affected, said the people, asking not to be identified discussing private matters.

Kernel: Guix and Logitech

  • Creating and using a custom Linux kernel on Guix System
    Guix is, at its core, a source based distribution with substitutes, and as such building packages from their source code is an expected part of regular package installations and upgrades. Given this starting point, it makes sense that efforts are made to reduce the amount of time spent compiling packages, and recent changes and upgrades to the building and distribution of substitutes continues to be a topic of discussion within Guix. One of the packages which I prefer to not build myself is the Linux-Libre kernel. The kernel, while not requiring an overabundance of RAM to build, does take a very long time on my build machine (which my children argue is actually their Kodi computer), and I will often delay reconfiguring my laptop while I want for a substitute to be prepared by the official build farm. The official kernel configuration, as is the case with many GNU/Linux distributions, errs on the side of inclusiveness, and this is really what causes the build to take such a long time when I build the package for myself. The Linux kernel, however, can also just be described as a package installed on my machine, and as such can be customized just like any other package. The procedure is a little bit different, although this is primarily due to the nature of how the package definition is written.
  • Improved Logitech wireless device support in kernel 5.2
    The just released 5.2-rc1 kernel includes improved support for Logitech wireless keyboards and mice. Until now we were relying on the generic HID keyboard and mouse emulation for 27 MHz and non-unifying 2.4 GHz wireless receivers. Starting with the 5.2 kernel instead we actually look at the devices behind the receiver. This allows us to provide battery monitoring support and to have per device quirks, like device specific HID-code to evdev-code mappings where necessary. Until now device specific quirks where not possible because the receivers have a generic product-id which is the same independent of the device behind the receiver. The per device key-mapping is especially important for 27MHz wireless devices, these use the same HID-code for Fn + F1 to Fn + F12 for all devices, but the markings on the keys differ per model. Sofar it was impossible for Linux to get the mapping for this right, but now that we have per device product-ids for the devices behind the receiver we can finally fix this. As is the case with other devices with vendor specific mappings, the actual mapping is done in userspace through hwdb.
  • The Better Logitech Wireless Device Support In The Linux 5.2 Kernel
    Red Hat's Hans de Goede who was involved in this latest Logitech support improvement work for the Linux 5.2 kernel has now blogged to share additional background information on the effort.

Top 20 best Tizen apps and games for April 2019

We are into May 2019, and it’s time for our monthly roundup of most downloaded Tizen apps and games for the previous month. The month of April 2019 did not see many new entrants making their way into that coveted Top 20 list, just three to be precise. An action game named Zombie Derby made the biggest jump to find itself on the fourth spot, whereas another action game, Mountain Sniper Jungle, enters the Top 20 list in the sixteenth position. A train simulator game named Euro Train Driving is the last new entrant on the list at seventeenth. The list is led by the usual trio of WhatsApp, Facebook and Facebook Messenger. The rest of the story is also pretty much the same: Hancom Office Viewer, Opera Mini web browser, HERE Maps, Instagram, Smart Tutor, Xender etc. Read more