Language Selection

English French German Italian Portuguese Spanish

Stx Linux 1.0 Final Look

Filed under
Linux
Reviews
-s

Stx Linux is a small lightweight operating system for the x86 arch. It is based on Slackware and slackware derivatives. One of the key features of Stx is it's ability to perform admirably on older hardware, and it's minimum requirements are a pentium 1 with 32 mb ram. Tuxmachines has covered some of the developmental releases, RC2 and RC3, but since final was released today, we felt it deserved yet another look.

The Stx site says, "STX Linux is a desktop Linux distribution especially targeted to older hardware. It also works quite well on new PC's." If you already have an older Stx install, Stibs has made some update patches available here. Today, we will report on a clean install as well as how the patch process went for us on our rc3 install.

The Changelog since rc3 includes:

  • 3 packaged Patches from the download page applied

  • Installer corrected for creating an fstab that allows normal users to mount cdrom and floppy drives
  • The usual package updates
  • Included Elleo's hacked eworkpanel with notification area
  • Included recompiled pyfltk (XFT font rendering now also in STXCC) Thx Mike
  • GTK 2 and EDE Themes switched to STX for a more uniform appearance, also Thx Mike Wink
  • Included gnome-cups-manager for printer administration (more common than the CUPS web frontend)
  • Included Requiredbuilder for creating dependecy files for Slackware/STX packages

Upgrading Current Install

My first test was upgrading my current rc3 install with the 3 patches made available on the Stx site. The install of the packages went smoothly and the upgrades were indeed implimented. I could see some new features already. Most noticable was the new login splash, wallpapers, and the incorporation of the Stx ede theme. I stated in my article on rc3 that I hoped the viagra logo didn't make it into the distro, but I knew it would. I was right. The new login screen and wallpapers now feature the new Stx logo. The root desktop wallpaper has a big old stop sign with the warning embossed "Think twice before you hit Enter." As you can see the "file splitter" (or menu entry) is now functional.

        

To patch/upgrade a rc3 install, download the 3 patches from the Stx Linux site and issue the command:
installpkg <stxpatches> It probably isn't necessary to reboot, but I did anyway. The process took less than 5 minutes start to finish. The patches are small to download and take a mere seconds to install.

Fresh Install

The installer has been discussed briefly before here on Tuxmachines, but for the newcomer I'll reiterate that it is what I call ascii-graphical. By that I mean that it's not a full blown fancy frame-buffered beauty like one finds in suse or mandriva, but yet it's not a text install demanding manual fdisks, mountings, and confusing commands. It does offer a 'graphical interface' of sorts, yet one uses the keyboard to navigate. It's one of the easiest and fastest installs to date. Missing is setting up a user account, but one is provided a chance to change the root password and a "demo" user (password: demo) is already setup. Once the system is in-place, you can setup a regular user through the Stx Control Panel.

As usual for Stx, the install went without a hitch and a nice light desktop resulted. For those who don't know, Stx features the Equinox Desktop Environment. It's main goal appears to be ease of use within a familiar environment, perhaps for those coming from Windows. Ede looks very much like a Win98 desktop. The newly included default Stx theme continues to appear very windows-like. I don't recall if this is exactly the same Stx theme that's been available on the Ede site for a while, but probably is. ...Which brings up another subject, there are quite a few nice themes available on the Ede site. But I'm getting off-topic.

The big ugly root stop sign wallpaper encountered in the patched system did not appear on the fresh install, but the viagra pill wallpaper did. It's not particularly repellant, but I prefer something with less of a message. I quickly changed my background to one of the others available thru the background settings module. In fact, ede comes with a control panel of its own in which you can change many settings such as the font, theme, and colors. As an aside, the fonts render much better in my fresh install.

Stx comes with lots of great applications for most popular tasks. One can, for example, listen to music, watch videos, surf the internet, answers emails, chat with friends, write a review, take screenshots and manipulate images, play some games, and even write a webpage.

        

        

Another difference in the patched system and the fresh install was the printer setup dialogue. Now that parellel ports detection was working, I clicked on printer setup in the Stx Control Panel. In the patched system, one is offered the browser based cups admin. In the fresh install, a little setup module opens a more familiar applet. They both do pretty much the same thing and both seem to work, but I like the gnome-cups-manager much better.

        

The Stx Control Panel is a really great thing. From there one can configure hardware, (un)install software, configure a network/internet connection, and set some system settings. It's a wonderful application, nice and light and all the modules seem to functional really well.

        

Through the Stx Control Panel one can install software. Stx includes slapt-get and the nice front-end gslapt. Already configured to use a Slackware 10.2 repository, one can, as an example, install jre, eog, or even KDE. I tested it installing jre, eog, and Fluxbox. I wanted eog because the image viewer provided couldn't seem to handle .pngs. In fact, I'd suggest to Stibs replacing Xfi with eog. Slapt worked wonderfully. I didn't even have to restart my browser for java to start working, eog rendered the images with no problems, and Fluxbox started right up. I'm not sure if KDE would go smoothly, perhaps I'll test it later. One needs to be cautious with gslapt/slapt-get as some things listed as installed aren't. Some things listed as not install are. So I "which binaries" and "locate libraries" before each installation to make sure. I'm guessing the "installed software" list slapt-get is using is left from Stibs' development system and it's not exactly accurate. Just a bit of caution is required. For example, gslapt states the kernel-source is installed, but it isn't. One can build a vanilla kernel from kernel.org (if they slapt-get --install diffutils) if desired to build any drivers you may need like nvidia. But it'd just be better if the ones matching the default kernel were included in the iso.

        

Several browser plugins worked out of the box such as the gxine movie player, flash, and javascript.

        

Then after installing java through gslapt:


Conclusion

So, as delivered Stx is a very capable yet light weight desktop system that has lots of personality and functionality. As installed one can accomplished most of their day to day tasks. Stx is ultra-stable and blazingly fast. As I've said before, I really like Stx a lot. If I mention it needs this or that, it's because I like it and plan to use it. The patches work fine, but I found the fresh install much cleaner and saw a few improvements not readily apparent in the patched system.

Stx is available for download primarily from ibiblio.org, but there are also two mirrors listed. They are the one in Germany and one in Bulgaria. I had the best luck from the one in Germany as ibiblio is always slow for me in my part of the world. For those who prefer bittorrent, they have that option available as well. Further, Stibs even offers the iso in 29 15 MB parts for those users on dial up. In addition, some Arabian Fonts are offered.

Previous coverage: RC3, RC2, RC Screenshots.

Current Screenshots.


More in Tux Machines

today's leftovers

  • Ubuntu Podcast from the UK LoCo: S12E33 – The Sentinel

    This week we’ve been to the Linux Application Summit in Barcelona. We round up news from the Ubuntu and desktop Linux community and bring you our picks from the wider tech news. It’s Season 12 Episode 33 of the Ubuntu Podcast! Alan Pope, Mark Johnson and Martin Wimpress are connected and speaking to your brain.

  • Kubernetes and the misconception of multi-cloud portability
  • Linux 5.5 To Finally Expose NVMe Drive Temperatures Via HWMON

    Linux for years has supported monitoring NVMe drive temperatures when installing the nvme user-space utility and run as root, etc. But now finally with Linux 5.5 the kernel is supporting NVMe drive temperature reporting through the hardware monitoring "HWMON" infrastructure alongside other hardware sensors. Come the Linux 5.5 stable release in early 2020 is the NVMe HWMON support to allow reporting the current NVMe drive temperature sensor(s) and min/max thresholds via this kernel infrastructure. This in turn allows user-space to simply query the data over sysfs without the need for any utilities, no root requirement, and should gracefully work with the various programs that report HWMON sensor readings to Linux desktop users.

  • PHP 5.3 To PHP 7.4 Performance Benchmarks On AMD EPYC

    With the big PHP 7.4.0 release due out next week, yesterday we published our PHP 7.4.0 benchmarks using the near-final build for this annual update to PHP. Those benchmarks compared previous releases as far back as PHP 5.6. But out of curiosity after that article I went to do some benchmarks going back to PHP 5.3 through PHP 7.4 and PHP 8.0-dev. With the AMD EPYC 7642 server running Ubuntu 19.10 used in yesterday's article, I ran the final PHP 5.3/5.4/5.5 benchmarks added in to yesterday's data. So for those curious how the historical PHP5 performance compares to the imminent PHP 7.4, these benchmarks are for your enjoyment today.

  • Wine Patches Coming To Allow UMIP Emulation - Works Around Issues For Ryzen 3000

    Coming up this weekend with the Linux 5.4 kernel is emulation/spoofing of the SGDT/SIDT/SMSW instructions around UMIP for allowing newer 64-bit Windows games to run on Wine and Steam Play (Proton). With newer CPUs like the AMD Ryzen 3000 series that support UMIP, these instructions are not allowed to run in user-space with Wine due to UMIP. So while the first stable kernel release is about to land with this support, some Wine-based emulation not contingent on the kernel patches is also in the works.

  • The different way to check whether you are using a 32-bit or 64-bit version of Linux on your computer
  • KF6 Sprint - Day One

    Today we started our KF6 sprint at the MBition office in Berlin. Beside the people attending in person, we have David Faure joining us via web conference. Thanks already to the people at MBition that spend time on making it possible to host the sprint there. First stuff to be discussed were some high level things, like does the monthly release scheme work out well. Short answer: yes :) The short period works well, allows people to fix issues directly in frameworks and still have that reasonable fast provided to the users. And the overhead of release creation is low, thanks to automation.

  • Zidoo M9 is a Rockchip RK3399 TV Box/Mini PC/SBC with Dual OS Support

    Zidoo has launched several TV boxes running Android over the years, some of which we reviewed such as Zidoo X9 (2015), or Zidoo H6 Pro.

  • Goldman Sachs is planning on giving some of its most valuable software to Wall Street for free

    Goldman Sachs wants to give away some of its most valuable software. The investment bank spent countless hours over 14 years developing a platform called Alloy to help it access and analyze the growing set of financial databases being created across the firm. Now Goldman is taking the unusual step of making that program, as well as the language underlying it, available to the rest of Wall Street for free as open-source software in collaboration with a nonprofit called Finos. The software and language "have grown to become critical tools within our firm across the trade lifecycle that help us price, assess and evaluate risk, clear transactions, and perform regulatory reporting," said Neema Raphael, co-chief data officer at Goldman. By making it publicly available, "we'll unlock tremendous value for the industry when we co-develop and share models."

  • Open source transparency comes to root of trust hardware

    Geopolitics have put enterprise data centers in the crosshairs of international espionage. From all corners of the globe, hackers of all sorts, including those aligned with national spy agencies, are zeroing in on hardware roots of trust. For any computing platform, the root of trust is the ultimate line of defense against cybersecurity attacks. No matter how secure your operating system and applications appear to be, they are acutely vulnerable if running on a hardware platform whose root of trust has been compromised by an unauthorized party.

  • Cloud Print becomes the latest product to face Google death squad

    At the end of 2020, after over a decade in beta, Google will pick up its product-ending shotgun and take Cloud Print for a talk behind the back shed, from which it will never return. "Beginning January 1, 2021, devices across all operating systems will no longer be able to print using Google Cloud Print," Google said in a support note. "We recommend that over the next year, you identify an alternative solution and execute a migration strategy." Last week for its own Chrome OS operating system, Google added CUPS printing, which it will use instead of Cloud Print.

  • Google shuts down its Cloud Print service after 10-year Beta

    Google revealed plans to shut down Cloud Print, a cloud-based printing solution, at the end of 2020 permanently. The company launched Cloud Print back in 2010 as a solution to print from any Internet connected device to compatible printers. The main benefit of the solution was that users did not have to install printer drivers on their client devices and that devices did not need to be in the same local network as the printer. The solution enabled printing on devices without official support from the printer's manufacturer or drivers for that particular device. On Windows users could install the Google Cloud Printer application to add cloud printing functionality to the operating system.

  • Google Cloud Print will be shut down on December 31, 2020

    After offering printing from any device, from any location, to any web-connected printer with Cloud Print, Google is shutting down the service that has technically been a beta product since 2010. Cloud Print will be gone by the end of next year and users will need to find an alternative before December 31, 2020. Chrome OS, which originally relied on Cloud Print entirely for printing needs, eschewing the need to develop native printing controls, is now going full native. Chrome OS already handles some administrative tasks for printers that use the Common Unix Printing System (CUPS). Google promises to expand administrative options through the end of the year, and add more robust support for external print servers and other security policy administration in 2020. Since Chrome OS and its apps relied entirely on Cloud Print, Google will also be developing APIs for third-party developers to handle printing tasks.

Why You Should Be Using Linux

How many times have you been happily working away when, out of nowhere, Windows either forced a reboot to update, stopped responding, or completely crashed? With Linux, those events are a thing of the past. Because of the way Linux was designed, you (the user) have complete control over nearly everything. Say, for example, an application fails on you. Instead of that application taking the entire desktop along for the ride (an issue that often stumps even software development providers), you can log into what’s called a virtual console and force that crashed application closed via the command line. Yes, that does take a bit more skill than the average user possesses, but once you know how it’s done, it becomes second nature. The likelihood of that actually happening, however, is low. The few instances where this has happened to me was due to my using beta or “nightly” releases of software, which the average user wouldn’t be working with. Linux simply works and works with an almost unheard of reliability. Read more

Industrial-grade Linux OS gets Over-the-Air updates

Modern embedded systems need a reliable and secure way to deliver software updates remotely. Toradex aims to accomplish this by publishing critical operating system updates to customers with devices running TorizonCore, an easy-to-use industrial-grade Linux OS. The system will provide full control over which updates and when these updates are pushed to their devices by way of a web interface. Additionally, customers will be able to push their own updates to their devices using the same OTA system. Managing deployed devices is made easy by providing a high-level view of all devices and their current status. Grouping devices together into fleets is supported and makes managing updates for many devices easy. Every device publishes information up to the server which can prove useful for evaluating device health, inconsistencies in deployed devices, etc. Read more

SUSE/OpenSUSE Development Report

  • openSUSE Tumbleweed – Review of the week 2019/47

    Another week, in which openQA did block some of the snapshots – and some issues it was unfortunately not able to see. Anyway, during the week 2019/47 we have released three snapshot into the wild (1116, 1118 and 1119), containing those changes: Mesa 19.2.4: fixes critical rendering issues from earlier Mesa 19.2.3. As this rendering issue did not happen on all graphics adapters, openQA had no chance of spotting it Linux kernel 5.3.11 KDE Plasma 5.17.3 Subversion 1.13.0 binutils 2.33.1

  • YaST Team: Highlights of YaST Development Sprints 88 and 89

    A few weeks ago, we wrote about the new ItemSelector widget that is finding its way into YaST user interfaces. It turned out that just a simple on/off status is not enough in some cases, so we had to extend that concept. For example, software modules may have dependencies, and we want to show the difference between one that was explicitly selected by the user and one that was auto-selected because some other software module requires it. This kind of shook the foundations of the underlying classes; all of a sudden a bit is no longer just a bit, but it needs to be broken down into even smaller pieces. Well, we cheated; we now use integer values instead. Most of the class hierarchy still only uses 0 and 1, but the new YCustomStatusItemSelector also supports using higher numbers for application-defined purposes. For each possible status value, the application defines the name of the icon to be displayed (for graphical UIs like the Qt UI), the text equivalent (for text mode / the NCurses UI), and an optional nextStatus which tells the widget what status to cycle to when the user changes the status of an item with a mouse click or with the keyboard. A value of -1 lets the application handle this. So this is not a one-trick-pony that is useful only for that one use case (the software modules), but a generic tool that might find good uses in other places all over YaST as well.