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

Security: X.Org Server, USBHarpoon, Kubernetes Penetration Testing

  • Three New Security Advisories Hit X.Org's X11 Library
    It's been a while since last having any big security bulletins for the X.Org Server even though some of the code-base dates back decades and security researchers have said the security is even worse than it looks and numerous advisories have come up in recent years. But it's not because X11 is bug-free as today three more security bulletins were made public affecting libX11. Today's security advisory pertains to three different functions in libX11 that are affected by different issues. The security issues come down to off-by-one writes, a potential out of boundary write, and a crash on invalid reply.
  • USBHarpoon: How “Innocent” USB Cables Can Be Manipulated To Inject Malware
    Back in 2014 Black Hat Conference, crypto specialists Karsten Nohl and Jakob Lell introduced the concept of BadUSB — a USB security flaw which allows attackers to turn a USB into a keyboard which can be used to type in commands. Now, a researcher from SYON Security has managed to build a modified USB charging cable that will enable hackers to transfer malware on your PC without you even noticing it. Behind the hood is the BadUSB vulnerability. [...] While BadUSB is gradually climbing the ladder towards the mainstream cyber attacks, people are also coming up with the corresponding firewalls to tackle the new age attacks.
  • Open Source 'Kube-Hunter' Does Kubernetes Penetration Testing
    Aqua Security released the open source kube-hunter tool for penetration testing of Kubernetes clusters, used for container orchestration. "You give it the IP or DNS name of your Kubernetes cluster, and kube-hunter probes for security issues -- it's like automated penetration testing," the company said in an Aug. 15 blog post. The tool -- with source code available on GitHub -- is also packaged by the company in a containerized version, which works with the company's kube-hunter Web site where test results can be seen and shared.

Linux-Friendly Hardware From Tranquil PC and Aaeon

  • Rugged, Linux-ready mini-PC showcases Ryzen V1000
    Tranquil PC open pre-orders on a fanless, barebones “Mini Multi Display PC” mini-PC with AMD’s Ryzen Embedded V1000 SoC, 4x simultaneous 4K DisplayPort displays, 2x GbE, and up to 32GB DDR4 and 1TB storage. Manchester, UK based Tranquil PC has launched the first mini-PC based on the AMD Ryzen Embedded V1000. The Mini Multi Display PC is named for the Ryzen V1000’s ability to simultaneously drive four 4K displays, a feature supported here with 4x DisplayPorts. The NUC-like, aluminum frame system is moderately rugged, with 0 to 40°C support and IP50 protection.
  • Apollo Lake Pico-ITX SBC has dual GbE ports and plenty of options
    Aaeon’s Apollo Lake powered “PICO-APL4” SBC offers a pair each of GbE, USB 3.0, and M.2 connections plus HDMI, SATA III, and up to 64GB eMMC. Aaeon has spun another Pico-ITX form-factor SBC featuring Intel Apollo Lake processors, following the PICO-APL3 and earlier PICO-APL1. Unlike those SBCs, the new PICO-APL4 has dual Gigabit Ethernet ports, among other minor changes.

State Certifies LA County’s New Open-Source Vote Tally System

Los Angeles County’s open-source vote tally system was certified by the secretary of state Tuesday, clearing the way for redesigned vote-by-mail ballots to be used in the November election. “With security on the minds of elections officials and the public, open-source technology has the potential to further modernize election administration, security and transparency,” Secretary of State Alex Padilla said. “Los Angeles County’s VSAP vote tally system is now California’s first certified election system to use open-source technology. This publicly-owned technology represents a significant step in the future of elections in California and across the country.” The system — dubbed Voting Solutions for All People (VSAP) Tally Version 1.0 — went through rigorous security testing by staffers working with the secretary of state as well as an independent test lab, according to county and state officials. Read more

Mesa and NVIDIA Graphics on Linux

  • Collabora's Mesa EGLDevice Work To Better Support Multiple GPUs
    As covered earlier this month, Emil Velikov at Collabora has been working on EGLDevice support for Mesa. These EGL extensions originally developed by NVIDIA are being pursued by Mesa developers for better dealing with the enumeration and querying of multiple GPUs on a system. Right now there is the DRI_PRIME environment variable to allow toggling between systems primarily with two GPUs (namely, Optimus notebooks have been the main use-case) but using EGLDevice support by the Mesa drivers the matter of GPU selection for OpenGL rendering can be made by the application/toolkit developer and for other scenarios like multi-GPU systems running without a display server.
  • NVIDIA 396.54 Linux Driver Released To Fix A OpenGL/Vulkan Performance Bug
    One day after announcing the GeForce RTX 2070/2080 series, NVIDIA has released a new Linux driver. But it's not a major new driver branch at this time (that's presumably coming closer to the 20 September launch date) with the Turing GPU support, but is a point release delivering a practical bug fix. The sole change listed in today's NVIDIA 396.54 driver update is, "Fixed a resource leak introduced in the 390 series of drivers that could lead to reduced performance after starting and stopping several OpenGL and/or Vulkan applications."