| DistroWatch Weekly
|DistroWatch Weekly, Issue 728, 4 September 2017
Welcome to this year's 36th issue of DistroWatch Weekly!
New distributions come along all the time, trying to solve old problems in new ways, improving on a parent distribution or showcasing new applications. This week we begin with a review of Nitrux, a project that is attempting all three. The Nitrux distribution features a custom, Plasma-based desktop environment called Nomad. It also offers a new package manager, firewall configuration tool and custom music player. Our Feature Story explores the details of the Nitrux distribution and its new utilities. In our News section we discuss a new community repository for SUSE Linux Enterprise, remote desktop tools coming to GNOME running on Wayland and an update to Bodhi Linux's installation media. We also cover two new changes coming to the Linux Mint distribution and Manjaro dropping support for 32-bit computers. Then, in our Tips and Tricks column, we talk about the Void distribution's approach to source-based software management. Plus we share the distribution releases of the past week and provide a list of the torrents we are seeding. In our Opinion Poll we ask our readers how important an operating system's package manager is when deciding what distribution to run. Finally, we are happy to welcome the BackSlash Linux project to our database. We wish you all a fantastic week and happy reading!
- Review: Nitrux 1.0.2
- News: SUSE creates new community software repository, remote desktop tools coming to GNOME on Wayland, Bodhi publishes updated media, Mint rewrites backup tool, Manjaro dropping 32-bit support
- Tips and tricks: Void source packages
- Released last week: Redcore Linux 1708, Emmabuntus 8-1.03, Bodhi Linux 4.3.0
- Torrent corner: 4MLinux, BlackArch, Bodhi, Emmabuntus, IPFire, KaOS, Linux Lite, Live Raizo, Manjaro, ReactOS, Redcore, Sabayon
- Opinion poll: Is the package manager important?
- New additions: BackSlash Linux
- New distributions: Namib GNU/Linux
- Reader comments
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (68MB) and MP3 (86MB) formats.
|Feature Story (by Jesse Smith)
Nitrux is a fairly new addition to the DistroWatch database. The distribution features a custom desktop environment, called Nomad, which is based on KDE's Plasma 5 desktop. The Nomad desktop reportedly features a simplified system tray and a friendly, graphical front-end for the UFW firewall utility. Nitrux also ships with a custom software manager called NX Software Center and a music player called Babe. The Nitrux project previously featured the Anbox utility for running Android apps on GNU/Linux desktop distributions, but Anbox has been removed in recent versions of the Nitrux distribution.
Nitrux is available in just one edition and is built for 64-bit x86 computers exclusively. Originally I tried to download Nitrux from the project's website and found my download kept getting disconnected partway through. I switched to downloading the project's ISO file (1.0GB in size) from a SourceForge mirror and this download completed successfully.
Booting from the Nitrux installation media brings up a menu asking if we would like to launch the distribution's live mode or start the system installer. Taking the live mode option, we are brought to a graphical login screen. We can sign into the Nomad desktop by using "nitrux" as both the username and password.
The Nomad desktop appears to use KDE's Plasma desktop software, but with a high degree of customization. The main desktop panel containing the application menu and system tray is placed at the top of the screen. A quick-launch bar is displayed at the bottom of the screen. The launch bar at the bottom of the desktop displays icons, but no tool tips or text to indicate what clicking on each icon will open. The application menu is displayed as a large grid of icons. The first page of the menu displays commonly used (or "favourite") applications. The second page lists all installed applications. The desktop's default background is mostly white with red and purple at the corners in shades that remind me of cotton candy.
Nitrux 1.0.2 -- The Nomad desktop and application menu
(full image size: 56kB, resolution: 1280x1024 pixels)
Looking around the live desktop environment I did not find any launcher for a system installer. I checked the project's website and could not find any documentation on installing the operating system. I rebooted the computer and selected the installation option from the ISO's boot menu. The system installer is one I had not used before. It is a graphical application which begins by asking us to create a new username and password for ourselves. The partitioning screen comes next. Here I was shown a list of partitions, but there wasn't any clear indication of how I should proceed to change disk partitions or assign them to mount points. With some trial and error I found I could click a partition to highlight it and then click a box to assign the partition to a mount point. I could not find any way to create new partitions, so it seems we need to use a separate partition manger (such as GParted) before we begin the installation process.
Once we set up mount points we can choose whether to install a boot loader. Then the installer copies its files to the disk. When the installer finished, I was presented with a mostly blank screen with a quick-launch bar at the bottom and no clear way to shut down the computer or reboot. I used the quick-launch bar to open a terminal and forced a reboot from there.
When I booted into my freshly installed copy of Nitrux I was presented with a login screen. Signing in, I was once again shown the project's system installer with no desktop environment. It seems that when we install Nitrux from the minimal environment that just runs the installer, we end up with an operating system that just provides enough of an environment to launch its installer.
I booted from the installation media once more and went looking through the live desktop environment. I eventually discovered that the system installer is launched from a graphical utility called Systemback which is typically used to backup and restore the operating system. I went through the installation process again and, when I was finished, was presented with a full copy of Nitrux, complete with functioning desktop environment.
At least I ended up with a working desktop system when I ran Nitrux inside a VirtualBox virtual machine. When I tried to launch Nitrux on my physical desktop machine the distribution failed to boot. This surprised me as Nitrux is based on Ubuntu, a distribution which tends to work well with my hardware. This left me to experiment with Nitrux in the virtual environment. I found the operating system, when logged into the Nomad desktop, used 480MB of RAM. The desktop environment was sluggish at first, however performance picked up quite a bit after I disabled file indexing and some visual effects from the System Settings panel. Nitrux automatically integrated with VirtualBox and was able to make use of my computer's full screen resolution without any configuration on my part.
Left to explore Nitrux in a VirtualBox environment, I started looking around the Nomad desktop. Nomad's information screens identify it as being based on KDE Plasma 5.10, but the environment looks and acts quite a bit differently than Plasma. For example, applications use a unified menu bar, which is displayed in the panel at the top of the screen. The application menu is a large grid of icons and, unlike the Plasma desktop, Nomad will not allow the menu to be swapped out for alternative menus. An effort appears to have been made to streamline Plasma, removing customization options and alternative widgets.
There are some other odd design choices too. For example the virtual terminal application has a bright blue background. The default fonts tend to have a tall, thin look which I found hard on my eyes after a while.
Nitrux 1.0.2 -- A virtual terminal and the notification area
(full image size: 61kB, resolution: 1280x1024 pixels)
Another problem I ran into is the distribution sometimes displays icons without accompanying text or tool tips. This can leave us somewhat in the dark as to what controls do. For example, when signing out of the Nomad desktop we are presented with a confirmation screen containing four symbols: a line, a circle, a lighting bolt and an arrow. Given the context I was able to work out which button corresponded to a given action (reboot, shut down, logout and sleep) but the lack of accompanying text meant I spent more time interpreting Nomad's screens than would normally be required if text had simply been included. This is an issue that popped up a number of times during my trial and it made using Nitrux feel like using an operating system with a foreign language locale selected.
Another visual problem I ran into was the desktop's top panel would sometimes be invisible when I logged in. I could still click on the panel to open the application menu, but the panel was not drawn on the screen. With a little experimenting I found this was caused by VirtualBox's 3-D support. Disabling VirtualBox's 3-D display feature caused the Nomad panel to always be displayed properly.
Software management on Nitrux is handled primarily by the NX Software Center. When NX Software Center first opens we are presented with a window containing two buttons near the top. Both buttons look to me to be "Home" buttons, judging by their shape, but there is no text to give them context. The first tab shows a single icon labelled "Core". It is not clear right away whether this is an installed package, an available package or an upgrade as no further information is provided. The second tab shows us a list of categories. Some of these categories are software related, but others do not appear to be. For example, some listed categories are Business, Communication, Developer Tools, Food & Drinks, Games, and Health & Fitness. Clicking a category shows us available packages in the given category. Some of these items are fairly clearly labelled, carrying names like "Investment Viewer" while others are more cryptic, such as the "irpf2017" package. A text field near the top of the window lets us search for specific packages by name.
Nitrux 1.0.2 -- The NX Software Center
(full image size: 257kB, resolution: 1280x1024 pixels)
Clicking on some packages opens up a new page containing a description of the selected package and a screen shot. Other times, clicking on a package does not bring up anything other than a blank page and the words "Other open source". At the bottom of the information screen is an Install button. Sometimes clicking this button causes the selected package to be installed and its icon added to the application menu. Other times, clicking the Install button results in an error simply reporting "not found" and the package is not installed.
Once I had installed a few items I found they were added to the first tab in the NX Software Center so I gather the first tab lists installed items. So far as I could tell, NX Software Center only lets us work with Snap packages, not Debian packages and to work with Debian archives we need to turn to the command line.
Nitrux 1.0.2 -- Browsing available packages
(full image size: 566kB, resolution: 1280x1024 pixels)
Since Nitrux uses Ubuntu repositories (specifically Ubuntu 17.10's repositories), I has expected the distribution to offer APT and apt-get package management tools. However, Nitrux ships with pacapt which is basically a command line program which uses the Pacman package manager's syntax and works with Debian packages. This means that instead of using "apt-get upgrade" to install software updates, we run "pacman -Syu".
While using Nitrux I never saw any indication software updates were available and I had to check for security updates manually. There is no graphical update manager, leaving the user to download security updates from the command line.
Nitrux uses the KDE System Settings panel to configure the desktop experience. For the most part the settings panel is pretty standard and contains the same configuration modules used by other platforms running KDE software. There are several modules available for changing the look of the desktop, adjusting short-cuts and tweaking visual effects. There is a module for setting up KDE Connect, a service which facilitates communication with Android devices. There is also a tool for enabling and disabling systemd services.
Nitrux 1.0.2 -- The settings panel
(full image size: 111kB, resolution: 1280x1024 pixels)
There were a few odd design choices here too. For example, the tool to create and adjust user accounts is not called "Users", but rather "Account Details". There is no module for setting up printers and scanners. There are three tools listed under the panel's Network category. These three modules are called Connections, Settings, and Connectivity. At first these may seem like three ways of describing the same thing, but upon closer inspection these modules handle setting up network connections, managing proxies and working with Samba shares, respectively.
The Nitrux website makes special mention of the distribution's firewall. The firewall utility is a graphical front-end for the UFW firewall. The custom firewall tool has a fairly simple layout which allows us to create new rules that either deny or allow network traffic. We can fine-tune the rules a bit, selecting source and destination addresses and ranges of ports. The firewall tool works, though I'm not sure if I see a large difference between using it or the more commonly used GUFW front-end for the UFW firewall.
I ran into a couple of issues when trying to print. The first was there is no printer configuration module available. I also found the CUPS printing software is not installed by default. I checked in the Nitrux software manager and could not find any front-end to working with printers or CUPS. I then switched to the command line and installed the system-config-printer package along with CUPS and CUPS drivers. The printer configuration utility was not added to my application menu so I launched it from the command line. CUPS was able to detect my network printer, but attempting to complete the setup resulted in CUPS throwing a vague "Internal error" message and failing to complete the connection to my printer.
Nitrux 1.0.2 -- Trying an alternative look
(full image size: 340kB, resolution: 1280x1024 pixels)
Finally, on the subject of system configuration, there is an application included with Nitrux called Kvantum Manager. This utility offers a quick and easy way to tweak the Nomad desktop environment. These tweaks can help us alter the desktop's theme, improve performance and place text under icons. I was not able to use Kvantum to get rid of the unified menu panel or switch application menus, but I did get a faster desktop with more text to assist in navigating the interface.
Nitrux does not ship with many applications by default. We are given a few common desktop programs such as the Chromium web browser (without Flash support), the Kate text editor and the Dolphin file manager. The distribution ships with the Babe music player, which I will come back to later, and the VLC multimedia player. Codecs are included for playing common media formats. We are given a PDF viewer, the Ark archive manager and a hardware information browser. Nitrux ships with version 6.3 of the GNU Compiler Collection and the systemd init software. The distribution runs on version 4.11.0 of the Linux kernel.
Earlier I mentioned the Babe music player which appears to be a media player unique to Nitrux. The initial screen Babe greets us with is a bit confusing. Near the top of the window is an empty Sources list. Then there is a plus sign in the middle of the window and a drag-n-drop region on the right. Near the bottom of the window we find an area which I think should allow us to type in a YouTube address and another box where I think we can select the location of extensions. There seem to be several options open to us, but not a lot of familiar-looking controls. I tried the + button first and was given the chance to select a directory where my audio files were kept. I started by selecting a directory with just two audio files. Babe locked up for a few seconds and then displayed an error message which simply read "oops".
Nitrux 1.0.2 -- The Babe music player
(full image size: 276kB, resolution: 1280x1024 pixels)
I next tried dragging audio files from the Dolphin file manager to the drag-n-drop region of Babe's window. The media player appeared to lock up for about a minute while a lot of data was passed over my network connection and then Babe crashed. After this, I switched to using VLC to play audio and video files and found the VLC multimedia player worked well.
Nitrux's motto is "Simple, quick and responsive." During my trial, I felt as though none of those descriptions suited the distribution. With its default settings, the Nomad desktop was not particularly responsive (though it might have been if I had managed to get the distribution running on physical hardware). Nitrux was relatively slow to boot and applications were not particularly quick (or slow) to load.
This is a young project and it has a lot of problems, ranging from hardware compatibility to lack of an update manager, to a software manager that was only able to install packages about two-thirds of the time, to a music player that crashed when asked to play audio files. There is a noticeable lack of documentation and on-screen queues for completing tasks. Perhaps the most obvious example of this lack of guidance comes at install time. I found selecting the Install option from the live media's boot menu would result in the operating system not installing properly. I had to load the live desktop, launch the backup manager and use that to launch the system installer - a process that is as roundabout as it is counter-intuitive.
What really puzzled me about Nitrux is the distribution is based on software that works well with my computer and that I find useful. Nitrux is largely based on Ubuntu and the KDE Plasma desktop, both examples of software that play well with my hardware. Yet Nitrux has its own system installer which is less friendly than Ubuntu's. The desktop is less flexible and slower than Plasma. The software manager does not function as well as Ubuntu's Software Center and cannot work with Debian packages.
I was unhappy with the distribution's approach of removing the APT tools and update manager and replacing them with command-line only tools which use Pacman syntax. Keeping APT and pacapt together might have made sense for appealing to Pacman fans, but stripping APT and its related tools out entirely just crippled package management on the distribution without adding any benefit.
This style of approach seems to be repeated throughout the distribution, replacing working utilities (music player, system installer, software manager, application menu) with alternatives that do not function as well as the ones provided by the parent distribution.
* * * * *
Hardware used in this review
My physical test equipment for this review was a desktop HP Pavilon p6 Series with the following specifications:
- Processor: Dual-core 2.8GHz AMD A4-3420 APU
- Storage: 500GB Hitachi hard drive
- Memory: 6GB of RAM
- Networking: Realtek RTL8111 wired network card
- Display: AMD Radeon HD 6410D video card
* * * * *
Visitor supplied rating
Nitrux has a visitor supplied average rating of: 8.8/10 from 6 review(s).
Have you used Nitrux? You can leave your own review of the project on our ratings page.
|Miscellaneous News (by Jesse Smith)
SUSE creates new community software repository, remote desktop tools coming to GNOME on Wayland, Bodhi publishes updated media, Mint rewrites backup tool, Manjaro dropping 32-bit support
SUSE is working to expand the number of software packages available to its enterprise customers with a new, community run repository. The new software repository is called SUSE Package Hub and is offered as a free add-on for SUSE Linux Enterprise customers. A post on the SUSE blog states: "It's a place where SUSE Linux Enterprise users can go to find a collection of popular open source packages that are pre-built for SUSE Linux Enterprise Server 12, ready to install and use. While the packages from the SUSE Package Hub are not officially supported by SUSE, they are officially approved for use, and you can use these packages with SUSE Linux Enterprise Server without worrying about breaking your SUSE support contract. And even better than Rerun, packages in SUSE Package Hub are free with a valid SUSE Linux Enterprise subscription." New packages can be submitted to the repository by community members and third-party software vendors.
* * * * *
The Wayland protocol is expected to eventually replace the X display server (currently used by most distributions) in the near future. In fact some distributions, such as Fedora, are already using Wayland by default to power the GNOME desktop. One drawback to using the new Wayland technology has been the lack of remote desktop utilities. Thanks to Jonas Ådahl from Red Hat, remote desktop access is coming to GNOME running on Wayland sessions. "GNOME's Vino remote desktop server was left behind when GNOME transitioned their desktop from the X compositor to Wayland. This meant that people who use distributions that stay close to upstream, like Fedora 25, have been left without a working VNC or even an RDP server for almost a full year. Jonas Ådahl from Red Hat has been busy adding new D-Bus APIs to libmutter. Mutter is the GNOME window manager and Wayland compositor. The two new APIs, org.gnome.Mutter.RemoteDesktop and org.gnome.Mutter.ScreenCast, expose a PipeWire stream containing the contents of the system's screens. The new APIs can create full-screen streams, or streams for individual windows. Only the former has been implemented." A post on the Ctrl blog website has further details.
* * * * *
The Bodhi Linux project published a new version, 4.3.0, this week and then quickly published a minor bug-fix release, version 4.3.1. The reason for the quick update was an issue in the default software repository configuration which affected users of Bodhi's Standard edition. "It seems like just yesterday that I was posting about Bodhi 4.3.0. Oh wait, it was just yesterday. In a friendly reminder that I am still human - we had a pretty major issue with one of the Bodhi 4.3.0 discs. Most issues we can simply patch via the package manager after the fact without releasing a new set of ISO images, but this issue was fairly unique. The new system was failing to add the official Bodhi repository to the installed system. Because of this I've published a set of discs with the 4.3.1 version number. You will only be affected by this issue if you installed Bodhi 4.3.0 using the Standard release." People who have already installed Bodhi Linux 4.3.0 can fix the issue themselves by adding the line "deb http://packages.bodhilinux.com/bodhi xenial b4main" to their /etc/apt/sources.list file.
* * * * *
The Linux Mint team has unveiled a few new changes that will be coming to the distribution in the near future. One feature grants applications the ability to share progress information with the desktop environment, which allows a progress bar to be displayed in the task switcher. "When an application is busy doing something it usually shows you a progress bar. Instead of mindlessly looking at the bar and waiting for it to reach 100% people usually seize the opportunity to do something else or distract themselves on the Web while waiting. The problem is.. how do you know when the application is ready if you can't see its progress bar? How can you keep an eye on the progress of the operation after you minimize the window or focus other windows on top of it? Some applications like the USB Stick formatter or the Nemo file operations worked around that problem by changing their window title to indicate their progress. That way their percentage is visible not only on their titlebar but also in the panel window list. Windows 7 did even better, they implemented a mechanism which allows applications to communicate progress to their environment. We decided to make this possible in Linux by implementing it in LibXapp." In addition, the backup utility has been given an overhaul, streamlining the backup process and allowing the backup application to run as a regular user instead of as the administrator. Details on both changes, along with screen shots, can be found on the Linux Mint blog.
* * * * *
Philip Müller has announced Manjaro Linux will begin phasing out support for 32-bit computers in the final quarter of 2017. A post on the Manjaro Linux website has the details: "Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture. The decision means that v17.0.3 ISO will be the last that allows users to install 32-bit Manjaro Linux. September and October will be our deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging will no longer require that from maintainers, effectively making i686 unsupported."
* * * * *
These and other news stories can be found on our Headlines page.
|Tips and Tricks (by Jesse Smith)
Void source packages
Last May I reviewed an independently developed Linux distribution called Void. The Void project has a number of unusual characteristics which make it an interesting distribution to follow. Void uses the runit init software rather than the more commonly used systemd and SysV init. Void is a lightweight, rolling release project which uses Flatpak packages to expand its range of available software. Void also uses a custom package manager, the X Binary Package System (XBPS). I talked a bit about these features in my review, but glossed over another significant feature: Void's source-based packages.
Void's source-based packages are handled by a framework that should feel familiar to people who have run Gentoo or one of the BSDs. The source framework - the tools for building Void's source packages and the recipes for turning the source code into executable files - is stored in a git repository and managed by the xbps-src utility. To get started, I recommend reading Void's wiki page on using xbps-src.
To start using Void's source packages, or ports system, we need to install the xtools package and download a copy of the source framework. We can accomplish this with the following four commands:
Note the "./" in front of the xbps-src command. This is required because the xbps-src script is inside the void-packages directory. At this point we have the framework in place to start configuring source packages and building them into installable packages. A list of the available software can be found under the srcpkgs directory. There are hundreds of packages available, so take your time browsing! Each package's meta data, distro-specific patches and configuration settings can be found in a directory named after the package. For example, the information for the VLC multimedia player can be found under srcpkgs/vlc. Each package's directory contains a template file which contains meta information and configuration settings. While we could edit this file directly to change settings, the recommended approach is to use the xbps-src utility to toggle any configuration changes we wish to make.
git clone https://github.com/voidlinux/void-packages
To see what configuration options are available for a given package we can run xbps-src with the show-options flag. For example:
./xbps-src show-options vlc
We can then turn certain options on or off with the -o flag. For instance the following command disables the Lua option when compiling the VLC media player:
./xbps-src -o ~lua pkg vlc
At this point I feel it is important to stop and address the pkg parameter in the above line. The xbps-src script accepts a number of action commands. The pkg parameter causes Void to build the selected software into a binary package we can install, like a .deb or .rpm archive on other distributions. There are a number of other parameters we can try:
|./xbps-src pkg vlc
||build a package for the VLC software
||deletes the VLC package from the system
||displays a list of installed packages
|./xbps-src install vlc
||install the VLC software
Details on the XBPS build process, its stages and options can be found in the xbps manual. I found it to be a helpful document, especially when I was playing around with alternative configurations for packages.
Running the command for building a package, for example: "./xbps-src pkg vlc", will download the necessary dependencies, compile the source code and save the resulting binary package in the hostdir/binpkgs directory. From there we can install the newly created package using the xi command. For example:
The xi command will prompt us for our sudo password if required so the new package can be installed on the operating system.
The documentation mentions we can use the command ./xbps-src install to install software rather than building a package for it. I tried this and the process appeared to complete successfully, but it did not result in the specified software being installed in my path. I checked the documentation and it says the newly built software will be installed in the directory masterdir/destdir/packagename. However, when I looked, my masterdir/destdir directory was completely empty, so I'm not sure where my software went after it was built. After that, I returned to building packages and manually installing them with the xi command.
When we are through with software and want to remove it, we can use the xbps-remove command. For example, to uninstall the Firefox browser we can use
The above command removes the Firefox browser, but not any dependencies the browser might leave behind. To also clear away package dependencies which are no longer required we can run:
xbps-remove -o firefox
On the whole, I found the xbps-src approach to building source code into packages to be fairly straight forward. The framework seems to be solid and useful. Having direct access to the build recipes as well as easy access to key configure flags certainly introduces a good deal of flexibility into the build process.
I am more familiar with FreeBSD's ports system so I think it's natural I draw some comparisons between the two. One of the big things that stood out for me was that FreeBSD organizes its 27,000+ ports into categories. So a port might be named "www/firefox" while on Void all ports are stored in one directory, so the name of the package is just "firefox". This is more simple and saves us some hunting, but means the srcpkgs directory is likely to get quite large over time.
Another thing I noticed was Void's ports are kept on GitHub where it is easy to submit a new package or an update. FreeBSD takes a more roundabout approach and has people send patches to the bug tracker when a port needs to be submitted or updated. Though I think FreeBSD's tools for handling ports are a bit streamlined in comparison. FreeBSD (and, to a point, Gentoo) limits the number of tools used. On FreeBSD I can checkout the ports framework with one command (portsnap) and perform builds, configuration, installs and removals with another command (make). Void uses four tools: git to checkout ports, xbps-src to build and configure packages, xi to install software and xbps-remove to delete old packages. The effects are the same and the steps approximately the same, but Void uses different tools for different jobs while FreeBSD mostly unifies things under its make utility.
My final comparison is I found the meta-data on Void's packages to be easier to read. I find FreeBSD ports to be somewhat cryptic, even after using (and creating them) for years. Void's template files are quite clear and I was able to read and modify them without requiring any documentation. That was a pleasant surprise and it helped me dive quickly into working with Void's collection of packages.
All in all, I liked Void's approach to working with source builds. It took me a little while to get familiar with the various options, but the result is a powerful collection of tools which give us flexibility when it comes to the features we build into our software.
* * * * *
More tips can be found in our Tips and Tricks archive.
|Released Last Week
Redcore Linux 1708
Ghiunhan Mamut has announced the release of a new snapshot of Redcore Linux, a rolling release desktop distribution based on Gentoo. The new snapshot offers several package upgrades and new fixes. "This release focuses on polishing the overall look'n'feel and out of the box experience of the distribution. New features are still present though. Here is a brief changelog since Redcore Linux 1706: resync with Gentoo stable portage tree (27.08.2017); Linux kernel LTS 4.9.40 with BFQ and UKSM enabled by default; Linux kernel 4.12.x available in the repository, for those who may want to use newer kernels; early CPU microcode updates are now enable by default for both Intel and AMD, this should improve the overall stability; graphics stack updated to mesa 17.1.7, llvm 4.0.1, libdrm 2.4.83, xorg-server 1.19.3; better WIFI connectivity support, Broadcom, Mediatek and Ralink chips should now work out of the box." A complete list of changes can be found in the release announcement. The Redcore Linux installer now requires the target computer has 2GB of RAM and 20GB of hard disk space.
The Emmabuntus project has announced the release of an update to the project's Debian-based edition. The new release will probably be the last to be based on Debian 8 "Jessie" as the new version, likely to arrive in September 2017, will be based on Debian 9 "Stretch". "This Debian Edition 1.03 version includes the following fixes and enhancements: Version based on Debian 8.9. Replacement of Icedove by Thunderbird. Replacement of the httpredir repositories by the FTP ones. Replacement of the now obsolete Pipelight and Pepper Flash by Adobe Flashplayer. Replacement of the now obsolete Skype 4.3 by the version 5.3, on 64-bits architecture only. Addition of the Arduino IDE. Addition of a function to change the Dock level within the Xfce menu. Addition of the French and English tutorials to configure a printer." A complete list of changes can be found in the project's release announcement.
Bodhi Linux 4.3.0
Jeff Hoogland has announced the release of a new version of the lightweight Bodhi Linux distribution. Bodhi ships with the Moksha desktop (a fork of Enlightenment) and is available in three flavours: Standard, AppPack (offering more applications) and Legacy (for older computers). The project's release announcement reads: "Today I am pleased to announce the release of Bodhi Linux 4.3.0. This is a normal update release and it comes three months after the release of Bodhi 4.2.0. Existing Bodhi 4.x.y users do not need to reinstall as the primary goal of this update release is to simply keep the current ISO image up to date. This release image includes EFL 1.19.1, Terminology 1.1.0, Ephoto 1.5, and Linux kernel 4.11. As with every release in the 4.x.y Bodhi series it is built on top of the rock solid foundation that is Ubuntu 16.04."
Bodhi Linux 4.3.0 -- Running the Moksha desktop
(full image size: 839kB, resolution: 1280x1024 pixels)
BlackArch Linux 2017.08.30
BlackArch Linux is an Arch Linux-based distribution designed for penetration testers and security researchers. The project has announced the availability of a new snapshot of the distribution. The new ISO image carries the version number 2017.08.30 and the distribution's blog provides the following release announcement: "Today we released new BlackArch Linux ISO images. Here's the changelog: bug fix - strap.sh (removed 'http:' for PGP key server); updated BlackArch installer to version 0.5.2 (update SHA1 sum of strap.sh); include Linux kernel 4.12.8; updated many BlackArch tools; updated all system packages; updated all window manager menus (Awesome, Fluxbox, Openbox). We wish to thank all of BlackArch's users, mirrors, and supporters. Thanks for your help." BlackArch Linux is available in Live and net-install editions. Download options include a live dual-layer DVD image or a single-CD network installation ISO.
Linux Lite 3.6
Jerry Bezencon has announced a new release of Linux Lite, a beginner friendly Linux distribution based on Ubuntu and featuring the Xfce desktop environment. The new version, Linux Lite 3.6, makes it easier to select nearby software sources for faster downloads and includes a new way to search through documentation. "Linux Lite 3.6 Final is now available for download. There have been a number of changes since the 3.4 release. In this release, we introduce two major new features. Firstly, Lite Sources is a repository selector that allows you to easily select a software repository nearest to you. When new versions of Linux Lite branded applications are released, you'll now get much faster download speeds thanks to Lite Sources. The second newest feature for Linux Lite 3.6 is the inclusion of both an on-line and off-line search engine for the Linux Lite Help Manual. Search results are highlighted to allow you to easily find the help content you need fast." Details on how to use these features, along with screen shots, can be found in the project's release announcement.
Linux Lite 3.6 -- Running the Xfce desktop
(full image size: 307kB, resolution: 1280x1024 pixels)
Linux From Scratch 8.1
Bruce Dubbs has announced the release of Linux From Scratch (LFS) and Beyond Linux From Scratch (BLFS) 8.1. The new release of the book, which guides readers through building their own Linux distribution, offers many updated packages and several fixes over the previous 8.0 release of the Linux From Scratch instruction book. The release announcement states: "The Linux From Scratch community is pleased to announce the release of LFS version 8.1, LFS version 8.1 (systemd), BLFS version 8.1, and BLFS version 8.1 (systemd). This release is a major update to both LFS and BLFS. The LFS release includes updates to glibc-2.26, binutils-2.29, and gcc-7.2.0. In total, 32 packages were updated, fixes made to bootscripts, and changes to text have been made throughout the book. The BLFS version includes approximately 900 packages beyond the base Linux From Scratch Version 8.1 book. This release has over 885 updates from the previous version including numerous text and formatting changes." The guides are available in SysV init and systemd editions.
KaOS is an independently developed Linux distribution which focuses on providing a polished collection of KDE/Qt-based software. The project's latest snapshot, KaOS 2017.09, features a hardened Linux kernel with Address Space Layout Randomization (ASLR). The latest snapshot also includes the Nomad firewall utility and the Kooka scanner tool. "It has been a few years, but finally there is an up to date (Qt5/kf5 based) firewall application available again. Nomad-firewall is available on this ISO. A second scan application is added, Kooka (just ported to kf5). This application has quite a few more options than skanlite, so it is nice to be able to add a second (Qt/kf5 based) option for scanning. Krita 3.2 has the new option to use the G?MIC plugin. For that gmic-qt is added to the repositories. With this, the options to add effects to any artwork/image are sheer endless. A change in how printer packages are packaged makes it that now most printers are automatically recognized and setup, no need any longer to run any print wizard. This counts for both Live mode and installed system." Additional changes are detailed in the project's release announcement.
Manjaro Linux 17.0.3
Philip Müller has announced the release of an update to the Manjaro Linux distribution, a desktop-focused derivative of Arch Linux. This update, Manjaro Linux 17.0.3, brings a number of bug fixes and newer packages. It is also likely to be the last version of Manjaro Linux to support 32-bit computers. "Manjaro Gellivara was a great release! Now we are proud to announce v17.0.3, our final release of Gellivara. It took us a little over two months to finish this updated version. We improved our hardware detection, fixed some features in our installer (Calamares), added the latest packages available to our install media and polished our release as a whole. Everyone, who used older install media than v17.0.2 release, should read also this announcement about password weakness and follow its advice to secure your systems. Also, Gellivara is the last edition of Manjaro Linux supporting 32-bit Architecture. Read more about this decision here." The release announcement has more details.
IPFire 2.19 Core 113
IPfire is an independent Linux distribution for use on firewalls and routers. The project has released a new update, IPFire 2.19 Core Update 113. The new version includes the Who Is Online utility to assist administrators is viewing which network devices are connected. "This is the official release announcement for IPFire 2.19 – Core Update 113. The change log is rather short, but comes with a big new feature: Who Is Online? (or WIO in short) has finally arrived on IPFire. It has been ported by the original author Stephan Feddersen and Alex Marx and is available as a usual add-on package called wio. It is a built in monitoring service for the local network showing what devices are connected, which ones are on line and can also send alarms on various events. Give it a try!" Further details on this release and its updated packages can be found in the project's release announcement.
* * * * *
Development, unannounced and minor bug-fix releases
The table below provides a list of torrents DistroWatch is currently seeding. If you do not have a bittorrent client capable of handling the linked files, we suggest installing either the Transmission or KTorrent bittorrent clients.
Archives of our previously seeded torrents may be found in our Torrent Archive. We also maintain a Torrents RSS feed for people who wish to have open source torrents delivered to them. To share your own open source torrents of Linux and BSD projects, please visit our Upload Torrents page.
Torrent Corner statistics:
- Total torrents seeded: 553
- Total data uploaded: 15.3TB
|Upcoming Releases and Announcements
Summary of expected upcoming releases
Is the package manager important?
There are many factors to consider when selecting a Linux distribution to install. People often look at the default desktop environment, whether a project is a rolling release or fixed, the range of package selection and default applications.
This week we would like to find out how big a roll the default package manager plays in your decision to install a distribution. Does it really matter to you whether a distro uses RPM, APT, Pacman or Emerge? Or is the package manager low level enough that you do not think about how software management works behind the scenes?
You can see the results of our previous poll on using Snap vs Flatpak in last week's edition. All previous poll results can be found in our poll archives.
Is the package manager important?
|Yes the package manager is very important to me: ||1058 (57%)|
| Yes the package manager is somewhat important to me: ||520 (28%)|
| No the package manager is not important to me: ||282 (15%)|
New projects added to database
BackSlash Linux is an Ubuntu-based desktop distribution featuring a custom shell running on top of the KDE Plasma desktop. BackSlash features a user interface inspired by macOS.
BackSlash Linux Olaf -- Checking for updates
(full image size: 363kB, resolution: resolution: 1280x1024 pixels)
* * * * *
Distributions added to waiting list
- Namib GNU/Linux. Namib GNU/Linux is an Arch-based distribution featuring the MATE desktop environment. The graphical Calamares system installer assists users in setting up the operating system.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 11 September 2017. Past articles and reviews can be found through our Article Search page. To contact the authors please send e-mail to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews/submissions, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, donations, comments)
- Bruce Patterson (podcast)
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 2, value: US$107.02)
|Linux Foundation Training
|• Issue 759 (2018-04-16): Neptune 5.0, building containers with Red Hat, antiX introduces Sid edition, fixing filenames on the command line|
|• Issue 758 (2018-04-09): Sortix 1.0, openSUSE's Transactional Updates, Fedora phasing out Python 2, locating portable packages|
|• Issue 757 (2018-04-02): Gatter Linux 0.8, the UNIX and Linux System Administration Handbook, Red Hat turns 25, super long term support kernels|
|• Issue 756 (2018-03-26): NuTyX 10.0, Neptune supplies Debian users with Plasma 5.12, SolydXK on a Raspberry Pi, SysV init development|
|• Issue 755 (2018-03-19): Learning with ArchMerge and Linux Academy, Librem 5 runs Plasma Mobile, Cinnamon gets performance boost|
|• Issue 754 (2018-03-12): Reviewing Sabayon and Antergos, the growing Linux kernel, BSDs getting CPU bug fixes, Manjaro builds for ARM devices|
|• Issue 753 (2018-03-05): Enso OS 0.2, KDE Plasma 5.12 features, MX Linux prepares new features, interview with MidnightBSD's founder|
|• Issue 752 (2018-02-26): OviOS 2.31, performing off-line upgrades, elementary OS's new installer, UBports gets test devices, Redcore team improves security|
|• Issue 751 (2018-02-19): DietPi 6.1, testing KDE's Plasma Mobile, Nitrux packages AppImage in default install, Solus experiments with Wayland|
|• Issue 750 (2018-02-12): Solus 3, getting Deb packages upstream to Debian, NetBSD security update, elementary OS explores AppCentre changes|
|• Issue 749 (2018-02-05): Freespire 3 and Linspire 7.0, misunderstandings about Wayland, Xorg and Mir, Korora slows release schedule, Red Hat purchases CoreOS|
|• Issue 748 (2018-01-29): siduction 2018.1.0, SolydXK 32-bit editions, building an Ubuntu robot, desktop-friendly Debian options|
|• Issue 747 (2018-01-22): Ubuntu MATE 17.10, recovering open files, creating a new distribution, KDE focusing on Wayland features|
|• Issue 746 (2018-01-15): deepin 15.5, openSUSE's YaST improvements, new Ubuntu 17.10 media, details on Spectre and Meltdown bugs|
|• Issue 745 (2018-01-08): GhostBSD 11.1, Linspire and Freespire return, wide-spread CPU bugs patched, adding AppImage launchers to the application menu|
|• Issue 744 (2018-01-01): MX Linux 17, Ubuntu pulls media over BIOS bug, PureOS gets endorsed by the FSF, openSUSE plays with kernel boot splash screens|
|• Issue 743 (2017-12-18): Daphile 17.09, tools for rescuing files, Fedora Modular Server delayed, Sparky adds ARM support, Slax to better support wireless networking|
|• Issue 742 (2017-12-11): heads 0.3.1, improvements coming to Tails, Void tutorials, Ubuntu phasing out Python 2, manipulating images from the command line|
|• Issue 741 (2017-12-04): Pop!_OS 17.10, openSUSE Tumbleweed snapshots, installing Q4OS on a Windows partition, using the at command|
|• Issue 740 (2017-11-27): Artix Linux, Unity spin of Ubuntu, Nitrux swaps Snaps for AppImage, getting better battery life on Linux|
|• Issue 739 (2017-11-20): Fedora 27, cross-distro software ports, Ubuntu on Samsung phones, Red Hat supports ARM, Parabola continues 32-bit support|
|• Issue 738 (2017-11-13): SparkyLinux 5.1, rumours about spyware, Slax considers init software, Arch drops 32-bit packages, overview of LineageOS|
|• Issue 737 (2017-11-06): BeeFree OS 18.1.2, quick tips to fix common problems, Slax returning, Solus plans MATE and software management improvements|
|• Issue 736 (2017-10-30): Ubuntu 17.10, "what if" security questions, Linux Mint to support Flatpak, NetBSD kernel memory protection|
|• Issue 735 (2017-10-23): ArchLabs Minimo, building software with Ravenports, WPA security patch, Parabola creates OpenRC spin|
|• Issue 734 (2017-10-16): Star 1.0.1, running the Linux-libre kernel, Ubuntu MATE experiments with snaps, Debian releases new install media, Purism reaches funding goal|
|• Issue 733 (2017-10-09): KaOS 2017.09, 32-bit prematurely obsoleted, Qubes security features, IPFire updates Apache|
|• Issue 732 (2017-10-02): ClonOS, reducing Snap package size, Ubuntu dropping 32-bit Desktop, partitioning disks for ZFS|
|• Issue 731 (2017-09-25): BackSlash Linux Olaf, W3C adding DRM to web standards, Wayland support arrives in Mir, Debian experimenting with AppArmor|
|• Issue 730 (2017-09-18): Mageia 6, running a completely free OS, HAMMER2 file system in DragonFly BSD's installer, Manjaro to ship pre-installed on laptops|
|• Issue 729 (2017-09-11): Parabola GNU/Linux-libre, running Plex Media Server on a Raspberry Pi, Tails feature roadmap, a cross-platform ports build system|
|• Issue 728 (2017-09-04): Nitrux 1.0.2, SUSE creates new community repository, remote desktop tools for GNOME on Wayland, using Void source packages|
|• Issue 727 (2017-08-28): Cucumber Linux 1.0, using Flatpak vs Snap, GNOME previews Settings panel, SUSE reaffirms commitment to Btrfs|
|• Issue 726 (2017-08-21): Redcore Linux 1706, Solus adds Snap support, KaOS getting hardened kernel, rolling releases and BSD|
|• Issue 725 (2017-08-14): openSUSE 42.3, Debian considers Flatpak for backports, changes coming to Ubuntu 17.10, the state of gaming on Linux|
|• Issue 724 (2017-08-07): SwagArch 2017.06, Myths about Unity, Mir and Ubuntu Touch, Manjaro OpenRC becomes its own distro, Debian debates future of live ISOs|
|• Issue 723 (2017-07-31): UBOS 11, transferring packages between systems, Ubuntu MATE's HUD, GNUstep releases first update in seven years|
|• Issue 722 (2017-07-24): Calculate Linux 17.6, logging sudo usage, Remix OS discontinued, interview with Chris Lamb, Debian 9.1 released|
|• Issue 721 (2017-07-17): Fedora 26, finding source based distributions, installing DragonFly BSD using Orca, Yunit packages ported to Ubuntu 16.04|
|• Issue 720 (2017-07-10): Peppermint OS 8, gathering system information with osquery, new features coming to openSUSE, Tails fixes networking bug|
|• Issue 719 (2017-07-03): Manjaro 17.0.2, tracking ISO files, Ubuntu MATE unveils new features, Qubes tests Admin API, Fedora's Atomic Host gets new life cycle|
|• Issue 718 (2017-06-26): Debian 9, support for older hardware, Debian updates live media, Ubuntu's new networking tool, openSUSE gains MP3 support|
|• Issue 717 (2017-06-19): SharkLinux, combining commands in the shell, Debian 9 flavours released, OpenBSD improving kernel security, UBports releases first OTA update|
|• Issue 716 (2017-06-12): Slackel 7.0, Ubuntu working with GNOME on HiDPI, openSUSE 42.3 using rolling development model, exploring kernel blobs|
|• Issue 715 (2017-06-05): Devuan 1.0.0, answering questions on systemd, Linux Mint plans 18.2 beta, Yunit/Unity 8 ported to Debian|
|• Issue 714 (2017-05-29): Void, enabling Wake-on-LAN, Solus packages KDE, Debian 9 release date, Ubuntu automated bug reports|
|• Issue 713 (2017-05-22): ROSA Fresh R9, Fedora's new networking features, FreeBSD's Quarterly Report, UBports opens app store, Parsix to shut down, SELinux overview|
|• Issue 712 (2017-05-15): NixOS 17.03, Alpha Litebook running elementary OS, Canonical considers going public, Solus improves Bluetooth support|
|• Issue 711 (2017-05-08): 4MLinux 21.0, checking file system fragmentation, new Mint and Haiku features, pfSense roadmap, OpenBSD offers first syspatch updates|
|• Issue 710 (2017-05-01): TrueOS 2017-02-22, Debian ported to RISC-V, Halium to unify mobile GNU/Linux, Anbox runs Android apps on GNU/Linux, using ZFS on the root file system|
|• Issue 709 (2017-04-24): Ubuntu 17.04, Korora testing new software manager, Ubuntu migrates to Wayland, running Nix package manager on alternative distributions|
|• Issue 708 (2017-04-17): Maui Linux 17.03, Snaps run on Fedora, Void adopts Flatpak, running Android apps on GNU/Linux, Debian elects Project Leader|
|• Full list of all issues|
|Random Distribution |
Thinstation is a modern thin client that does work on its own for basic operations like web browsing, managing removable media and printers, but rely on servers for major applications as well as administration of the clients. The clients may be diskless or boot from local media. Thinstation works as a client using X, ICA, RDP, SSH, NX, telnet, tn5250 and other protocols and works on standard PC hardware.