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

Programming: WebAssembly, Mozilla GFX, Qt and Python

  • WebAssembly for speed and code reuse

    Imagine translating a non-web application, written in a high-level language, into a binary module ready for the web. This translation could be done without any change whatsoever to the non-web application's source code. A browser can download the newly translated module efficiently and execute the module in the sandbox. The executing web module can interact seamlessly with other web technologies—with JavaScript (JS) in particular. Welcome to WebAssembly. As befits a language with assembly in the name, WebAssembly is low-level. But this low-level character encourages optimization: the just-in-time (JIT) compiler of the browser's virtual machine can translate portable WebAssembly code into fast, platform-specific machine code. A WebAssembly module thereby becomes an executable suited for compute-bound tasks such as number crunching. Which high-level languages compile into WebAssembly? The list is growing, but the original candidates were C, C++, and Rust. Let's call these three the systems languages, as they are meant for systems programming and high-performance applications programming. The systems languages share two features that suit them for compilation into WebAssembly. The next section gets into the details, which sets up full code examples (in C and TypeScript) together with samples from WebAssembly's own text format language.

  • Mozilla GFX: moz://gfx newsletter #47

    Hi there! Time for another mozilla graphics newsletter. In the comments section of the previous newsletter, Michael asked about the relation between WebRender and WebGL, I’ll try give a short answer here. Both WebRender and WebGL need access to the GPU to do their work. At the moment both of them use the OpenGL API, either directly or through ANGLE which emulates OpenGL on top of D3D11. They, however, each work with their own OpenGL context. Frames produced with WebGL are sent to WebRender as texture handles. WebRender, at the API level, has a single entry point for images, video frames, canvases, in short for every grid of pixels in some flavor of RGB format, be them CPU-side buffers or already in GPU memory as is normally the case for WebGL. In order to share textures between separate OpenGL contexts we rely on platform-specific APIs such as EGLImage and DXGI. Beyond that there isn’t any fancy interaction between WebGL and WebRender. The latter sees the former as a image producer just like 2D canvases, video decoders and plain static images.

  • The Titler Revamp: QML Producer in the making

    At the beginning of this month, I started testing out the new producer as I had a good, rough structure for the producer code, and was only facing a few minor problems. Initially, I was unclear about how exactly the producer is going to be used by the titler so I took a small step back and spent some time figuring out how kdenlivetitle worked, which is the producer in use. Initially, I faced integration problems (which are the ones you’d normally expect) when I tried to make use of the QmlRenderer library for rendering and loading QML templates – and most of them were resolved by a simple refactoring of the QmlRenderer library source code. To give an example, the producer traditionally stores the QML template in global variables which is taken as a character pointer argument (which is, again, traditional C) The QmlRenderer lib takes a QUrl as its parameters for loading the Qml file, so to solve this problem all I had to do was to overload the loadQml() method with one which could accommodate the producer’s needs – which worked perfectly fine. As a consequence, I also had to compartmentalise (further) the rendering process so now we have 3 methods which go sequentially when we want to render something using the library ( initialiseRenderParams( ) -> prepareRenderer( ) -> renderQml( ) ) [...] The problem was resolved (thank you JB) finally and it was not due to OpenGL but it was simply because I hadn’t created an QApplication for the producer (which is necessary for qt producers). The whole month’s been a steep curve, definitely not easy, but, I enjoyed it! Right now, I have a producer which is, now, almost complete and with a little more tweaking, will be put to use, hopefully. I’m still facing a few minor issues which I hope to resolve soon and get a working producer. Once we get that, I can start work on the Kdenlive side. Let’s hope for the best!

  • How to Make a Discord Bot in Python

    In a world where video games are so important to so many people, communication and community around games are vital. Discord offers both of those and more in one well-designed package. In this tutorial, you’ll learn how to make a Discord bot in Python so that you can make the most of this fantastic platform.

  • Qt Visual Studio Tools 2.4 RC Released

    The Visual Studio Project System is widely used as the build system of choice for C++ projects in VS. Under the hood, MSBuild provides the project file format and build framework. The Qt VS Tools make use of the extensibility of MSBuild to provide design-time and build-time integration of Qt in VS projects — toward the end of the post we have a closer look at how that integration works and what changed in the new release. Up to this point, the Qt VS Tools extension managed its own project settings in an isolated manner. This approach prevented the integration of Qt in Visual Studio to fully benefit from the features of VS projects and MSBuild. Significantly, it was not possible to have Qt settings vary according to the build configuration (e.g. having a different list of selected Qt modules for different configurations), including Qt itself: only one version/build of Qt could be selected and would apply to all configurations, a significant drawback in the case of multi-platform projects. Another important limitation that users of the Qt VS Tools have reported is the lack of support for importing Qt-related settings from shared property sheet files. This feature allows settings in VS projects to be shared within a team or organization, thus providing a single source for that information. Up to now, this was not possible to do with settings managed by the Qt VS Tools.

Screenshots/Screencasts: 10 GNU/Linux Distros (Screenshots) and New Screencast/Video of Endeavour OS 2019.08.17

  • 10 Linux distros: From different to dangerous

    One of the great benefits of Linux is the ability to roll your own. Throughout the years, individuals, organizations, and even nation states have done just that. In this gallery, we're going to showcase some of those distros. Be careful, though. You may not want to load these, or if you do, put them in isolated VMs. We're not kidding when we say they could be dangerous.

  • Endeavour OS 2019.08.17 Run Through

    In this video, we are looking at Endeavour OS 2019.08.17.

A Cycle of Renewal, Broken: How Big Tech and Big Media Abuse Copyright Law to Slay Competition

In 1950, a television salesman named Robert Tarlton put together a consortium of TV merchants in the town of Lansford, Pennsylvania to erect an antenna tall enough to pull down signals from Philadelphia, about 90 miles to the southeast. The antenna connected to a web of cables that the consortium strung up and down the streets of Lansford, bringing big-city TV to their customers — and making TV ownership for Lansfordites far more attractive. Though hobbyists had been jury-rigging their own "community antenna television" networks since 1948, no one had ever tried to go into business with such an operation. The first commercial cable TV company was born. The rise of cable over the following years kicked off decades of political controversy over whether the cable operators should be allowed to stay in business, seeing as they were retransmitting broadcast signals without payment or permission and collecting money for the service. Broadcasters took a dim view of people using their signals without permission, which is a little rich, given that the broadcasting industry itself owed its existence to the ability to play sound recordings over the air without permission or payment. The FCC brokered a series of compromises in the years that followed, coming up with complex rules governing which signals a cable operator could retransmit, which ones they must retransmit, and how much all this would cost. The end result was a second way to get TV, one that made peace with—and grew alongside—broadcasters, eventually coming to dominate how we get cable TV in our homes. By 1976, cable and broadcasters joined forces to fight a new technology: home video recorders, starting with Sony's Betamax recorders. In the eyes of the cable operators, broadcasters, and movie studios, these were as illegitimate as the playing of records over the air had been, or as retransmitting those broadcasts over cable had been. Lawsuits over the VCR continued for the next eight years. In 1984, the Supreme Court finally weighed in, legalizing the VCR, and finding that new technologies were not illegal under copyright law if they were "capable of substantial noninfringing uses." Read more

Software, HowTos and Storage

  • Pause Music When Locking The Screen And Resume On Unlock For Spotify, Rhythmbox, Others

    When you lock your computer screen (without suspending the system), most desktop audio players continue playback in the background, sometimes not emitting any sound ¹. Due to this you may unintentionally skip parts of podcasts or songs in a playlist, etc. Enter pause-on-lock, a Bash script that pauses your music player when you lock the screen and resumes playback once the screen is unlocked. pause-on-lock works on Unity, GNOME, Cinnamon and MATE desktop environments, and by default it supports Spotify and Rhythmbox. With the help of playerctl (a command line controller for controlling media players that support the MPRIS D-Bus interface), this script can extend its supported music players to many others, including Audacious, VLC, Cmus, and others.

  • Easy Way to Screen Mirroring Android on Ubuntu!

    Screen Mirroring is one of the features found on smartphones, one of which is on Android. This feature serves to display the smartphone to a computer. This is very useful for example when used for demo applications that you make, or maybe for other things related to smartphones. In Ubuntu, we can do screen mirroring with applications available on Android, for example is AirDroid which can be used for screen mirroring through a browser. But I feel less optimal when using this instant method. Because there is a lag between activity on the smartphone and on the monitor screen on the computer, and the results are less than optimal. What might be the cause because it is opened through a browser and uses wi-fi? (Personal question). I am looking for another application for screen mirroring on Ubuntu, and one of the very good applications is Scrcpy. This application can be used for screen mirroring without a root device.

  • Command line quick tips: Searching with grep
  • How to Install Cezerin on Debian 9
  • How to Create a Bootable USB Stick from the Ubuntu Terminal
  • How to Install Git on Debian 10
  • How to Copy/Move a Docker Container to Another Host
  • Six practical use cases for Nmap
  • The Next Stage of Flash Storage: Computational Storage
  • NAS upgrade

    At some point in the future I hope to spend a little bit of time on the software side of things, as some of the features of my set up are no longer working as they should: I can't remote-decrypt the main disk via SSH on boot, and the first run of any backup fails due to some kind of race condition in the systemd unit dependencies. (The first attempt does not correctly mount the backup partition; the second attempt always succeeds).

  • Storage Concepts And Technologies Explained In Detail