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

Devices: Xtra-PC, Arduino and Inventor Coding Kit

  • Xtra-PC Reviews – Best Linux USB-Stick? - Product Review by Rick Finn

    The Xtra-PC Linux USB-Stick might be your solution if you have problems with your old and slow PC. It's a small flash drive stick and it's using Linux OS to boost you PC's operations. Check out now.

  • Arduino Blog » Old keyboard turned into a new children’s learning toy

    Peter Turczak’s toddler son loves “technical stuff,” especially things like keyboards and computers that adults use. After discussing this with other likeminded technical parents, the idea of giving new life to an old (PS/2 or AT) keyboard as a teaching tool was hatched.

  • SiFive Helping To Teach Kids Programming With RISC-V HiFive Inventor Coding Kit

    SiFive in cooperation with Tynker and BBC Learning have launched a Doctor Who themed HiFive Inventor Coding Kit. This Initial HiFive Inventor Coding Kit is intended to help kids as young as seven years of age get involved with computer programming through a variety of fun exercises and challenges involving the RISC-V powered mini computer and related peripherals like LED lighting and speaker control. [...] So for those looking to get their kids involved with computer programming and looking for an IoT-type device with some fun sensors and various themed exercises to get them experimenting, the HiFive Inventor Coding Kit is worth looking into further. More details on the programming platform can be found via Tynker.com and on the hardware at HiFiveInventor.com. The HiFive Inventor Kit is available from Amazon.com and other Internet retailers for $75 USD.

Security Leftovers

  • Security updates for Monday

    Security updates have been issued by Arch Linux (atftp, coturn, gitlab, mdbook, mediawiki, nodejs, nodejs-lts-dubnium, nodejs-lts-erbium, nodejs-lts-fermium, nvidia-utils, opensmtpd, php, python-cairosvg, python-pillow, thunderbird, vivaldi, and wavpack), CentOS (firefox and thunderbird), Debian (chromium and snapd), Fedora (chromium, flatpak, glibc, kernel, kernel-headers, nodejs, php, and python-cairosvg), Mageia (bind, caribou, chromium-browser-stable, dom4j, edk2, opensc, p11-kit, policycoreutils, python-lxml, resteasy, sudo, synergy, and unzip), openSUSE (ceph, crmsh, dovecot23, hawk2, kernel, nodejs10, open-iscsi, openldap2, php7, python-jupyter_notebook, slurm_18_08, tcmu-runner, thunderbird, tomcat, viewvc, and vlc), Oracle (dotnet3.1 and thunderbird), Red Hat (postgresql:10, postgresql:12, postgresql:9.6, and xstream), SUSE (ImageMagick, openldap2, slurm, and tcmu-runner), and Ubuntu (icoutils).

  • About CVE-2020-27348

    Well this is a doozey. Made public a while back was a security vulnerability in many Snap Packages and the Snapcraft tool used to create them. Specifically, this is the vulnerability identified as CVE-2020-27348. It unfortunately affects many many snap packages… [...] The problem arises when the LD_LIBRARY_PATH includes an empty element in its list. When the Dynamic Linker sees an empty element it will look in the current working directory of the process. So if we construct our search paths with an accidental empty element the application inside our Snap Package could be caused to load a shared library from outside the Snap Package’s shipped files. This can lead to an arbitrary code execution. It has been common to put a definition of the LD_LIBRARY_PATH variable into a Snap Package’s snapcraft.yaml that references a predefined $LD_LIBRARY_PATH as if to extend it. Unfortunately, despite this being common, it was poorly understood that SnapD ensures that the $LD_LIBRARY_PATH is unset when starting a Snap Package’s applications. What that means is that where the author tried to extend the variable they have inadvertantly inserted the bad empty element. The empty element appears because $LD_LIBRARY_PATH is unset so the shell will expand it to an empty string.

  • Wait, What? Kids Found A Security Flaw in Linux Mint By Mashing Keys!

    Security flaws can be incredibly stupid and dangerous. Of course, I’m not judging anyone, we are humans after all. But this little incident is quite funny.

Audiocasts/Shows: Blender 2.91, Server Security, Linux in the Ham Shack and More

IBM/Red Hat Leftovers

  • Davie Street Enterprises: A case study in digital transformation

    We would like to introduce you to Davie Street Enterprises (DSE). DSE is a fictitious 100-year-old multinational corporation that is beginning its digital transformation journey. In this post we will lay the groundwork for a series following DSE as an illustration of how some Red Hat customers are preparing for and succeeding at digital transformation to save money, become more efficient, and compete more effectively. The company isn't real, but its struggle is very real for many organizations. Throughout this series, we will explore the business problems any number of organizations are challenged with and how DSE, with the help of Red Hat and its partners, plan to solve those problems. To start, let’s learn more about DSE, its business, and some of the associates involved in its digital transformation journey.

  • Farewell 2020: A year of togetherness with our EMEA partners

    When reflecting on 2020, I do what many people do and think about what things were like prior to this year. For me, I immediately go back to a spring day three years ago. Red Hat was hosting our EMEA Partner Conference; a mix of distributors, independent software vendors (ISVs), system integrators and solution providers from across the region. Alongside the usual product updates and market insight sessions you might expect, we decided to do a little drumming. A lot of drumming, in fact — 900 people banging bongos and clashing cymbals. Other than the noise, what I remember was the genuine sense of togetherness; embarrassment and egos put to the side in the pursuit of the perfect tempo. It seems drumming is a good signal of solidarity. Even in a large group, it’s easy to notice someone beating to a different rhythm. Trainers and coaches use this drumming technique frequently to promote unity and coordination. Our coach that day later congratulated me on "having such a tight knit group of employees." When I told him they weren’t our employees but partners from 550 different companies, he couldn’t believe it.

  • Visualizing system performance with RHEL 8 using Performance Co-Pilot (PCP) and Grafana (Part 1)

    When it comes to performance metrics data collection and visualization on Linux, PCP metrics collection and visualization are key. Red Hat Enterprise Linux (RHEL) 8 provides an excellent framework for collecting performance metrics and visualizing them! The days of poring over command line output to try and figure out what is happening on a system are gone. In this series, I’d like to introduce the power of using Performance Co-Pilot (PCP) and Grafana to visualize system performance data in RHEL. By default, Performance Co-Pilot is not installed on RHEL 8. We believe in giving users choices and as such, you have to opt-in to using Performance Co-Pilot.