| DistroWatch Weekly
|DistroWatch Weekly, Issue 735, 23 October 2017
Welcome to this year's 43rd issue of DistroWatch Weekly!
Last week was an eventful one in the open source community. Early in the week developers were racing to push out security patches to fix a bug in wireless network encryption and later in the week we saw the release of Ubuntu 17.10 and its many community editions. In our News section we cover these events along with improvements to the Solus distribution, Parabola GNU/Linux-libre experimenting with OpenRC builds and Manjaro trying to make using the on-line version of Microsoft Office feel more like running a native Linux application. First though, Joshua Allen Holm takes the ArchLabs distribution for a spin and reports on his experiences. Plus we explore how to set up and use a new software build system called Ravenports. Ravenports is able to build the same software ports across multiple operating systems and we talk about its uses in our Tips and Tricks column. In our Opinion Poll we ask our readers if you use cross-platform port systems, like Ravenports or pkgsrc. Plus we share the distribution releases of the past week and provide a list of torrents we are seeding. We wish you all a terrific week and happy reading!
- Review: ArchLabs Linux Mínimo
- News: Solus updates, Manjaro improving on-line MS-Office integration, Ubuntu's changing desktop sessions, Parabola creates OpenRC spin, information on the WPA vulnerability
- Tips and tricks: Building software with Ravenports
- Released last week: Ubuntu 17.10, Ubuntu MATE 17.10, DragonFly BSD 5.0.0
- Torrent corner: Artix, AUSTRUMI, Kubuntu, Lubuntu, Ubuntu, Ubuntu Budgie, Ubuntu MATE, Ubuntu Studio, Xubuntu
- Opinion poll: Cross-platform ports and packages
- New distributions: Retrobuntu, Hyperbola GNU/Linux-libre, MultiBootUSB-Live
- Reader comments
|Feature Story (by Joshua Allen Holm)
ArchLabs Linux Mínimo
ArchLabs is a lightweight Linux distribution designed to provide a BunsenLabs-like experience based on Arch instead of BunsenLabs's Debian base. While there are certainly many stylistic similarities shared by ArchLabs and BunsenLabs, the latest ArchLabs release, named Mínimo, is clearly something that is inspired by BunsenLabs, but not a straight port of BunsenLabs onto Arch. ArchLabs has forged its own path, resulting a distribution that is BunsenLabs-like, but very much its own thing.
To find out what ArchLabs had to offer I gave it a try inside a VirtualBox virtual machine and bare metal on my laptop. Below, I take a look at the desktop environment, the install process, a handy setup script called AL-Hello, and more.
The install disc for ArchLabs Linux Mínimo is 956MB. For users just wanting to try out the distribution, the image comes with VirtualBox guest additions pre-installed. Booting the ArchLabs image in a virtual machine or from a USB drive on bare metal should be a familiar experience for anyone experienced with any modern Linux distribution. The live desktop environment boots quickly and the installer can then be run from the live environment.
ArchLabs 2017.09 -- The Calamares system installer
(full image size: 180kB, resolution: 1360x768 pixels)
The installer for ArchLabs is called Calamares. While much easier than Arch's do-everything-yourself install process, Calamares works pretty much like every other standard Linux installer out there. There are really no surprises here. The installer asks for the same information and does the same things as all the other Linux installation programs.
The only issue I had with Calamares happened the first time I tried to install ArchLabs in VirtualBox. For optimal installation, Calamares needs an Internet connection, but it only checks to see if there is an active network connection. When I was installing, my host computer was not connected to the Internet. The virtual machine had an active network connection, but when it finally tried to get data from the Internet near the end of the installation process, the installer failed, and it did not do so cleanly. Since this problem might also occur in situations where the machine is connected to a LAN with no outside access to the Internet, the installer should really start by checking to see if it has Internet access, not assuming it has Internet access just because it has an active network connection. In situations were there was no network connection or there was a network connection with an active connection to the Internet, the installation process worked as expected.
ArchLabs desktop environment
The desktop for ArchLabs is based on Openbox with a Polybar panel at the top of the screen. This top bar has four virtual desktops; a small shortcut menu for accessing the default web browser, terminal, and file manger, and logging out and shutting down the system; a window switcher that displays a count of how many windows are open; a network connection manager; volume control; and a clock. The application menu is accessed by right-clicking on the desktop. While lightweight, the desktop is aesthetically pleasing with nice transparencies, polished icons, and clean window decorations. On my system, I found that the desktop with nothing extra installed and no applications running used between 160MB and 180MB of RAM, but the blog post announcing the release of Mínimo lists RAM usage closer to 260MB. Either way, much, much lighter than some of the alternatives.
ArchLabs 2017.09 -- The default desktop
(full image size: 201kB, resolution: 1360x768 pixels)
The default ArchLabs desktop does not come with much software. Firefox for web browsing, Geany for text editing, Audacious for audio, MPV for video, Thunar for file management, and a few other utilities come pre-installed. However, installing additional software is very easy using the AL-Hello script that runs after the system has been installed. This script asks dozens of questions, letting the user customize their system to their liking. To give just a few examples: the script asks if the user wants to add a dock, what office software they would like (if any), if they want to install Steam, if they want to install extra media codecs and fonts, and the list goes on.
ArchLabs 2017.09 -- The customization script
(full image size: 172kB, resolution: 1360x768 pixels)
While very thorough, the AL-Hello script is not perfect. Each question is just a single line in the terminal with no context. If a user is unfamiliar with a particular option, they have to look elsewhere to find out what the programs mentioned are and what they do. Because each prompt is a single line in a standard sized terminal window, there is plenty of room to provide more text explaining what various choices are. Another minor problem is that some of the options give multiple options and an “install all” option, but if the choices are A, B, and C, with D being install all, there is no way to just install A and C, for example. Don't get me wrong, the script is wonderful, but both of these issues are usability enhancements I would very much like to see in future releases.
ArchLabs 2017.09 -- The Pacli package manager
(full image size: 206kB, resolution: 1360x768 pixels)
The AL-Hello script does a great job of getting a system up and running with a large selection of packages, but it does not cover everything. After the initial setup, ArchLabs uses Pacli to handle installing and updating software. This text-based utility has options for installing software, updating the system, and all the other traditional package manager tasks. If the text-based interface is too spartan, Pamac is available as one of the many options available in the AL-Hello script. Pamac provides a graphic interface for installing and updating software, for users who prefer graphical interfaces to text-based ones. Either way, there are plenty of software packages available, so installing all of their favorite applications should not be a problem for most users.
ArchLabs is a great combination of lightweight and, thanks to its Arch base, constantly up-to-date software. While probably not for everyone, ArchLabs is a polished distribution that anyone looking for an Arch-based distribution that has a pre-configured desktop and software selection should check out. The only drawback is that, like many lightweight distributions, selecting applications based on what is deemed best for an individual task can result in an odd hodgepodge of applications that all behave differently. Of course, the choice of what to install is up to the user, so that might not be a problem for some, but having applications from Xfce, GNOME, KDE, etc., can lead to a jumbled user experience.
* * * * *
Hardware used in this review
My physical test equipment for this review was a Lenovo Ideapad 100-15IBD laptop with the following specifications:
- Processor: 2.2GHz Intel Core i3-5020U CPU
- Storage: Seagate 500GB 5400 RPM hard drive
- Memory: 4GB of RAM
- Networking: Realtek RTL8723BE 802.11n Wireless Network Adapter
- Display: Intel HD Graphics 5500
* * * * *
Visitor supplied rating
ArchLabs has a visitor supplied average rating of: 8.9/10 from 92 review(s).
Have you used ArchLabs? You can leave your own review of the project on our ratings page.
|Miscellaneous News (by Jesse Smith)
Solus updates, Manjaro improving on-line MS-Office integration, Ubuntu's changing desktop sessions, Parabola creates OpenRC spin, information on the WPA vulnerability
The Solus project published a newsletter this week which laid out several important changes and upgrades coming to the distribution. Among the key changes are an upgrade of the GNOME desktop to version 3.26.1 and getting the Control Centre to better integrate with the rest of the distribution. Behind the scenes, the LLVM compiler has been upgraded to version 5.0.0. Several changes have been applied to the Steam gaming portal too: "Linux Steam Integration has seen three releases this week and features a new 'liblsi-intercept', which controls the dynamic linking for Steam binaries, resolving some long-standing issues such as crashes on start, broken full screen views, and ensures that the Steam client uses OS-provided libraries. liblsi-intercept also provides a whitelist to allow Steam to continue to load its own private libraries and our intercept behaviour is controlled on a process-name basis. What does this mean? Well it means the Steam client is now using more system libraries, such as SDL, which fixes crashes as well as full screen issues when watching a game trailer in the store."
* * * * *
The Manjaro Linux team is working to integrate the on-line version of Microsoft Office with the Linux desktop using the Jade Application Kit. The new functionality, which makes Microsoft's on-line productivity tools appear to run like native Linux applications, can be set up on Manjaro by installing the ms-office-online package. A discussion on the new functionality can be found on the Manjaro forum.
* * * * *
This past week there has been a lot of talk about a vulnerability in most implementations of WPA2 which could make it possible for attackers to break the encryption on wireless network traffic. The vulnerability is widespread and affects most major desktop and mobile operating systems. The FreeBSD team has a good summary of the issue: "A vulnerability was found in how a number of implementations can be triggered to reconfigure WPA/WPA2/RSN keys (TK, GTK, or IGTK) by replaying a specific frame that is used to manage the keys. Such reinstallation of the encryption key can result in two different types of vulnerabilities: disabling replay protection and significantly reducing the security of encryption to the point of allowing frames to be decrypted or some parts of the keys to be determined by an attacker depending on which cipher is used. We are actively working on a patch for the base system to address these issues. Current users who use Wi-Fi with WPA2 should use a wired connection as a workaround, and we strongly recommend using end-to-end encryption methods like HTTPS or SSH to better protect against this type of attack."
* * * * *
With the launch of Ubuntu 17.10 this week, the distribution is making GNOME the default desktop instead of the formerly used Unity desktop. With this change, some people running Ubuntu and Ubuntu GNOME may be wondering about how to upgrade and which desktop sessions will be available. The DidRocks blog has some answers and a guide for navigating the various desktop options: "The 'Ubuntu' session corresponds to GNOME Shell experience with our modifications (Ubuntu Dock, appindicator support, our theme, small behaviour changes). You have probably seen those and followed their development on previous blog posts. This is the default session running under Wayland. The 'Ubuntu on Xorg' session, being similar to the previous one, but running on Xorg as the name indicates. Users who can't run Wayland (using NVIDIA proprietary driver or unsupported hardware) should be automatically fallbacked and only presented with that session."
* * * * *
The developers of Parabola GNU/Linux-libre, a free software distribution based on Arch Linux, are experimenting with new spins of their operating system. The new spins will feature the OpenRC init software instead of systemd. A post on the project's news page reads: "Since a considerable amount of Parabola developers and users prefer to use the OpenRC init system instead of systemd, which is the default, we are proud to announce the first releases of Parabola GNU/Linux-libre OpenRC Edition ISOs! As of now they are still in beta, you can get them here. These are not official, yet, but we are working on fixing all their issues. You can help by testing them and giving us some feedback so we can improve them. Besides this, due to a bug in MATE, we are planning to replace MATE with LXDE in the graphical ISOs (available with systemd and OpenRC) and include the Calamares installer for a more user-friendly experience for newcomers."
* * * * *
These and other news stories can be found on our Headlines page.
|Tips and Tricks (by Jesse Smith)
Building software with Ravenports
One challenge software developers and packagers constantly face is the effort required to get new projects packaged for the wide variety of operating systems and package managers present in the open source community. If I write a new utility and want to share it with the community, then I (or other packagers) need to create a variety of packages in various formats. Traditionally, I might need to make an RPM package for the Fedora family of distributions, a Deb package for the Debian family, and another package for the Arch family. If I want to support the BSDs, then each flavour (FreeBSD, NetBSD, OpenBSD, etc) has their own unique style of creating and testing ports & packages.
Portable package formats such as Flatpak and Snap reduce the effort package maintainers and developers need to put into supporting each separate platform, but we can still easily run into cases where we need to work with four or five separate package formats to support a wide range of open source systems. This results in a lot of duplicate effort, basically teaching each package manager how to build and install the software. Ideally, it would be nice to create just one package or port script for the software we write and have it work across all open platforms. This is where a young project called Ravenports shines. The Ravenports website describes the project as follows:
Ravenports is an integrated system designed to build packages of complex software on all UNIX-like platforms. It is considered "universal" because Ravenports is not anchored to any single operating system; once the build procedure for a particular software is created, that software is then available for all supported platforms. The simplest use case is to access the freely available prebuilt package repository for each supported platform.
What this means is I, as a developer, can create one set of rules for building my software on the Ravenports framework. That one recipe can then be used to build native packages that will install and run on DragonFly BSD, FreeBSD and almost all flavours of Linux. This has the potential to be a huge time saver for developers and people porting software. We do not need a separate build file or script for every operating system and package manager, we just need one Ravenports port and the software should build and run everywhere.
This idea sounds good, at least for hardworking developers and package maintainers, but does Ravenports deliver on its lofty goals? I decided to test Ravenports on a copy of Manjaro Linux and find out.
Ravenports does have a few restrictions in its current form. Right now, Ravenports runs on 64-bit x86 systems exclusively. Some of the tools used to set up Ravenports are 64-bit executables and simply will not run on 32-bit computers. On Linux, there is a library dependency, but this should not be an issue for any mainstream Linux distributions.
The Ravenports project has documentation which explains how to set up the ports system on Linux distributions. The initial set up of Ravenports just takes a minute and, when it is completed, we essentially have two key tools available in our operating system's /raven directory.
The first significant tool is a native, statically-linked version of the FreeBSD pkg package manager. This package manager can be used to find packages in the Ravenports test repository, install packages (either from a remote source or locally), display package information and statistics and remove unwanted Ravenports packages. The pkg package manager is located at /raven/sbin/pkg-static. I like the pkg package manager, it is fast, has informative prompts and offers a fairly straight forward syntax.
The second tool we get when we install the Ravenports framework is a utility called ravenadm, which can be found in the /raven/bin directory. The ravenadm program can be used to discover what ports are available, whether we have installed a specific port or not, and build local copies of a port. The main function of ravenadm is to turn source code into binary packages and we can do this using the build keyword. For example we can fetch and package the curl application using:
sudo /raven/bin/ravenadm build curl
Ravenports has a much more elegant approach to showing us what it is doing than most other port build systems I have encountered. Most port systems flood the terminal with each instruction the build is performing and any output from the compiler or other build tools. This show-everything approach can be useful for debugging issues, but it is ugly and typically unhelpful in other situations as the user is not shown useful progress information or statistics. Ravenports takes a cleaner approach. Instead of being shown step-by-step instructions, we are given a general overview of what the build process has done and plans to do. While it is working, Ravenports displays a dashboard in the terminal which shows how many ports it is going to build (including dependencies), how many it has built and how many ports have been completed successfully. The messy step-by-step details are logged to text files in the /var/ravenports/primary/logs/logs directory in case we need to go back and investigate a port which failed to build. Each port gets its own log file which greatly reduces the amount of scrolling we need to perform when searching for problems in the build information.
Ravenports -- Showing build status information
(full image size: 383kB, resolution: 1280x1024 pixels)
When my build process finished I was curious to see if my newly built software would run natively on my Linux box. However, it was not immediately clear where my freshly built packages had been stored. They were not in the /raven directory and the new software had not been copied into my user's path. I eventually found new packages were stored in the /var/ravenports/primary/packages/All directory. These packages could then be installed using the pkg package manager by running
sudo /raven/sbin/pkg-static add /var/ravenports/primary/packages/All/package-name
The above command installs our new package into the /raven directory. We can then run it using the program's full path or by adding /raven/bin to our user's executable path.
At this point it may be clear that installing software from Ravenports is not exactly convenient for end users. Which is fair, Ravenports is not attempting to make package management easier for end users, this is a framework for developers and packagers. Which means the questions we should be asking are whether or not Ravenports works and whether it makes packaging easier?
I am happy to report Ravenports definitely works. I tried installing pre-built software from the test repository and built three ports at random. All four packages installed and worked properly on my Manjaro Linux test box. And, assuming the framework is functioning as expected, I should be able to build the same ports on any other Linux distribution, DragonFly BSD or FreeBSD. This is a big step forward for people who maintain ports and packages. Typically I need to maintain separate build instructions for RPM- and Deb-based distributions as well as BSD ports. With Ravenports, I could use one set of instructions and have my software automatically packaged everywhere. It is potentially a huge time saver.
The only drawback I see with Ravenports is it requires each operating system to support it in some way, either by setting up a Ravenports software repository or linking to the Ravenports testing package repository. In theory, in a few years each distribution could compliment (or even replace) its existing build system with a Ravenports system and every upstream software project would only need one person to maintain the cross-platform port. But that would require each operating system to feature a way for users to easily install Ravenports packages. Historically it has been difficult to get open source systems to standardize on any one system, there is a lot of inertia when it comes to packaging open source software. Still, I think Ravenports holds a lot of promise as a cross-platform, write-once-package-for-everyone framework. It has the ability to do for packagers what Flatpak and Snaps have done for end users, reducing the effort required to create and distribute software packages.
* * * * *
More tips can be found in our Tips and Tricks archive.
|Released Last Week
DragonFly BSD 5.0.0
The DragonFly BSD project has announced the release of a new version of their operating system. The new version, DragonFly BSD 5.0.0, introduces a number of new features and improvements. In particular, version 5.0.0 features the advanced HAMMER2 file system, updated video drivers and the IPFW firewall has gained improved performance. "Preliminary HAMMER2 support has been released into the wild as-of the 5.0 release. This support is considered EXPERIMENTAL and should generally not yet be used for production machines and important data. The boot loader will support both UFS and HAMMER2 /boot. The installer will still use a UFS /boot even for a HAMMER2 installation because the /boot partition is typically very small and HAMMER2, like HAMMER1, does not instantly free space when files are deleted or replaced. DragonFly 5.0 has single-image HAMMER2 support, with live dedup (for cp's), compression, fast recovery, snapshot, and boot support. HAMMER2 does not yet support multi-volume or clustering, though commands for it exist. Please use non-clustered single images for now. IPFW has gone through a number of updates in DragonFly and now offers better performance. pf and ipfw3 are also still supported." Further information can be found in the project's release announcement.
Adam Conrad has announced the availability of a new version of the popular Ubuntu distribution. Ubuntu 17.10, which carries the codename "Artful Aardvark" switches the default desktop from Unity to GNOME. "Codenamed "Artful Aardvark", Ubuntu 17.10 continues Ubuntu's proud tradition of integrating the latest and greatest open source technology into a high-quality, easy-to-use Linux distribution. As always, the team has been hard at work through this cycle, introducing new features and fixing bugs. Under the hood, there have been updates to many core packages, including a new 4.13-based kernel, glibc 2.26, gcc 7.2, and much more. Ubuntu Desktop has had a major overhaul, with the switch from Unity as our default desktop to GNOME3 and GNOME Shell. Along with that, there are the usual incremental improvements, with newer versions of GTK and Qt, and updates to major packages like Firefox and LibreOffice." Additional information can be found in the release announcement and in the release notes.
Ubuntu 17.10 -- The GNOME application menu
(full image size: 1.8MB, resolution: 1360x768 pixels)
Ubuntu MATE 17.10
Martin Wimpress has announced the release of Ubuntu MATE 17.10. The new version features a number of desktop changes, including a global menu bar placed at the top of the screen. The 17.10 release also features an improved Heads-Up Display (HUD) which makes it possible to search through application menus using only the keyboard. "This is something we started during Ubuntu MATE 16.10 and never perfected, but is now ready for prime time. A favourite of Unity 7 users is the Heads-Up Display (HUD) which provides a way to search for and run menu-bar commands without your fingers ever leaving the keyboard. So if you're trying to find that single filter in GIMP but can't remember which filter category it fits into or if you can't recall if preferences sits under File, Edit or Tools on your favourite browser, you can just search for it rather than hunting through the menus. Just like Global Menus the HUD is currently only available via the Contemporary, Cupertino and Mutiny [layouts]." Further information on this release, along with screen shots, can be found in the project's release announcement.
The Xubuntu team has announced the release of Xubuntu 17.10. The new version includes significant improvements to accelerated video playback on Intel video cards. The distribution also includes support for driverless printing and includes the GNOME Font Viewer by default. "The GNOME Font Viewer is now included by default. This application simplifies viewing and installing fonts. Client side decorations (CSD) now consume much less space with the Greybird GTK+ theme. New device, mimetype, and monochrome panel icons have been included with the elementary-xfce icon theme. We usually link directly to the Ubuntu release notes, but there are several significant improvements that affect all flavours and our users: Accelerated video playback with Intel hardware should now work more reliably out of the box. The changes might also bring some performance improvements for Parole and Chromium users. Bluetooth and USB audio devices should now work better by default due to changes in BlueZ and PulseAudio. Driverless printing has been added to Ubuntu. This provides support for most modern printers: IPP Everywhere, Apple AirPrint, Mopria, PCLm, and Wifi Direct as supported. Other printers can still be added from the Printers dialog." Further information can be found in the project's release announcement.
The Kubuntu team has announced the release of a new version of their Ubuntu Community Edition featuring the Plasma desktop. The new release features Plasma 5.10, version 4.13 of the Linux kernel and upgrades to most of the operating system's desktop software. "Kubuntu 17.10 has been released, featuring the beautiful Plasma 5.10 desktop from KDE. Codenamed 'Artful Aardvark', Kubuntu 17.10 continues our proud tradition of integrating the latest and greatest open source technologies into a high-quality, easy-to-use Linux distribution. The team has been hard at work through this cycle, introducing new features and fixing bugs. Under the hood, there have been updates to many core packages, including a new 4.13-based kernel, KDE Frameworks 5.38, Plasma 5.10.5 and KDE Applications 17.04.3. Additional information and screen shots can be found in the distribution's release announcement and release notes.
Ubuntu Budgie 17.10
David Mohammed has announced the release of Ubuntu Budgie 17.10, a desktop Linux distribution featuring the simple but elegant Budgie desktop (originally developed by the Solus distribution). The new release comes with a refreshed look as well as a number of new desktop applets: "We are pleased to announce the release of a new version of our distribution, the second only as an official flavor of the Ubuntu family. Based on 17.04 experiences, feedback and suggestions we have received from our users, the new release comes with a lot of new features, fixes and optimizations: more customisation options via Budgie Welcome; complete desktop look and feel changes - more options; lots more Budgie applets available from independent developers; the best from the GNOME family as well as the fantastic Tilix terminal emulator with Quake mode enabled; stylish new login screen; latest upstream Budgie desktop version 10.4; Nightlight and Caffeine applets as standard." Here is the brief release announcement, with further technical details provided in the release notes.
Ubuntu Budgie 17.10 -- The welcome screen
(full image size: 375kB, resolution: 1280x1024 pixels)
Ubuntu Studio 17.10
Ross Gammon has announced the release of Ubuntu Studio 17.10, the latest version of the project's official Ubuntu variant designed for audio, video and graphics professionals. This is routine release with the usual round of software updates and a new experimental feature for improved performance during recordings: "We are happy to announce the release of our latest version, Ubuntu Studio 17.10 'Artful Aardvark'. As a regular version, it will be supported for 9 months. Since it's just out, you may experience some issues, so you might want to wait a bit before upgrading. The Ubuntu Studio Controls package has been updated to provide an experimental option to set the CPU governor to performance mode. This is important for recording. At the moment, the setting is not persistent, and needs to be reset at every reboot. BIOS settings may need to be changed for this setting to take effect. Audio - removed zynjacku as this software is no longer maintained by the original developer." See the release announcement and release notes for further information.
Simon Quigley has announced the release of Lubuntu 17.10, a desktop distribution built from Ubuntu packages, but featuring the Lightweight X11 Desktop Environment (LXDE) which is suitable for older computers: "Thanks to all the hard work from our contributors, Lubuntu 17.10 has been released. With the code name 'Artful Aardvark', Lubuntu 17.10 is the 13th release of Lubuntu, with support until July of 2018. What has improved since 17.04? We now ship with Linux kernel 4.13; general bug-fix release as we prepare to switch to LXQt; LXDE components have been updated with bug fixes; the artwork has received an update; the latest release of Audacious, version 3.9, is included by default; Hardinfo has been updated to the latest upstream snapshot." Also available is the Lubuntu "Next" variant, an experimental build of Lubuntu with the LXQt desktop: "Alongside Lubuntu 17.10 featuring LXDE, the Lubuntu team is proud to announce an early adopter's release of Lubuntu Next, featuring the LXQt 0.11.1 desktop environment which is the Qt 5 port of LXDE." Read the release announcement and release notes for more details.
* * * * *
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: 612
- Total data uploaded: 16.1TB
|Upcoming Releases and Announcements
Summary of expected upcoming releases
Cross-platform ports and packages
In our Tips and Tricks column we discussed Ravenports and how it can be used to build packages cross multiple operating systems. Ravenports is not the only cross-platform ports system and other projects, such as pkgsrc, assist users in installing applications on a variety of platforms.
This week we would like to know if you use a cross-platform ports framework or cross-distro package manager, like Ravenports. Please leave us a comment letting us know which one you use on your computer(s).
You can see the results of our previous poll on keeping utility discs on hand in last week's edition. All previous poll results can be found in our poll archives.
Cross-platform ports and packages
|I use multiple cross-platform ports systems: ||50 (5%)|
| I use one cross-platform ports system: ||83 (8%)|
| I do not use a cross-platform ports system: ||921 (87%)|
Distributions added to waiting list
- Retrobuntu. Retrobuntu is a Linux distribution based on Xubuntu 16.04 LTS. It features the RetroPie gaming software and Kodi media player.
- Hyperbola GNU/Linux-libre. Hyperbola GNU/Linux-libre is an Arch-based distribution featuring free (as in freedom) software only. The distribution uses OpenRC as the default init software.
- MultiBootUSB-Live. MultiBootUSB-Live is a portable, live desktop distribution based on Debian. It can be used to write multiple Linux distributions to a USB thumb drive.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 30 October 2017. Past articles and reviews can be found through our Article Search page. To contact the authors please send e-mail to:
|Linux Foundation Training
|• Issue 840 (2019-11-11): Fedora 31, monitoring user activity, Fedora working to improve Python performance, FreeBSD gets faster networking|
|• Issue 839 (2019-11-04): MX 19, manipulating PDFs, Ubuntu plans features for 20.04, Fedora 29 nears EOL, Netrunner drops Manjaro-based edition|
|• Issue 838 (2019-10-28): Xubuntu 19.10, how init and service managers work together, DragonFly BSD provides emergency mode for HAMMER, Xfce team plans 4.16|
|• Issue 837 (2019-10-21): CentOS 8.0-1905, Trident finds a new base, Debian plans firewall changes, 15 years of Fedora, how to merge directories|
|• Issue 836 (2019-10-14): Archman 2019.09, Haiku improves ARM support, Project Trident shifting base OS, Unix turns 50|
|• Issue 835 (2019-10-07): Isotop, Mazon OS and, KduxOS, examples of using the find command, Mint's System Reports becomes proactive, Solus updates its desktops|
|• Issue 834 (2019-09-30): FreedomBox "Buster", CentOS gains a rolling release, Librem 5 phones shipping, Redcore updates its package manager|
|• Issue 833 (2019-09-23): Redcore Linux 1908, why Linux distros are free, Ubuntu making list of 32-bit software to keep, Richard M Stallman steps down from FSF leadership|
|• Issue 832 (2019-09-16): BlackWeb 1.2, checking for Wayland session and applications, Fedora to use nftables in firewalld, OpenBSD disables DoH in Firefox|
|• Issue 831 (2019-09-09): Adélie Linux 1.0 beta, using ffmpeg, awk and renice, Mint and elementary improvements, PureOS and Manjaro updates|
|• Issue 930 (2019-09-02): deepin 15.11, working with AppArmor profiles, elementary OS gets new greeter, exFAT support coming to Linux kernel|
|• Issue 829 (2019-08-26): EndeavourOS 2019.07.15, Drauger OS 7.4.1, finding the licenses of kernel modules, NetBSD gets Wayland application, GhostBSD changes base repo|
|• Issue 828 (2019-08-19): AcademiX 2.2, concerns with non-free firmware, UBports working on Unity8, Fedora unveils new EPEL channel, FreeBSD phasing out GCC|
|• Issue 827 (2019-08-12): Q4OS, finding files on the disk, Ubuntu works on ZFS, Haiku improves performance, OSDisc shutting down|
|• Issue 826 (2019-08-05): Quick looks at Resilient, PrimeOS, and BlueLight, flagship distros for desktops,Manjaro introduces new package manager|
|• Issue 825 (2019-07-29): Endless OS 3.6, UBports 16.04, gNewSense maintainer stepping down, Fedora developrs discuss optimizations, Project Trident launches stable branch|
|• Issue 824 (2019-07-22): Hexagon OS 1.0, Mageia publishes updated media, Fedora unveils Fedora CoreOS, managing disk usage with quotas|
|• Issue 823 (2019-07-15): Debian 10, finding 32-bit packages on a 64-bit system, Will Cooke discusses Ubuntu's desktop, IBM finalizes purchase of Red Hat|
|• Issue 822 (2019-07-08): Mageia 7, running development branches of distros, Mint team considers Snap, UBports to address Google account access|
|• Issue 821 (2019-07-01): OpenMandriva 4.0, Ubuntu's plan for 32-bit packages, Fedora Workstation improvements, DragonFly BSD's smaller kernel memory|
|• Issue 820 (2019-06-24): Clear Linux and Guix System 1.0.1, running Android applications using Anbox, Zorin partners with Star Labs, Red Hat explains networking bug, Ubuntu considers no longer updating 32-bit packages|
|• Issue 819 (2019-06-17): OS108 and Venom, renaming multiple files, checking live USB integrity, working with Fedora's Modularity, Ubuntu replacing Chromium package with snap|
|• Issue 818 (2019-06-10): openSUSE 15.1, improving boot times, FreeBSD's status report, DragonFly BSD reduces install media size|
|• Issue 817 (2019-06-03): Manjaro 18.0.4, Ubuntu Security Podcast, new Linux laptops from Dell and System76, Entroware Apollo|
|• Issue 816 (2019-05-27): Red Hat Enterprise Linux 8.0, creating firewall rules, Antergos shuts down, Matthew Miller answers questions about Fedora|
|• Issue 815 (2019-05-20): Sabayon 19.03, Clear Linux's developer features, Red Hat explains MDS flaws, an overview of mobile distro options|
|• Issue 814 (2019-05-13): Fedora 30, distributions publish Firefox fixes, CentOS publishes roadmap to 8.0, Debian plans to use Wayland by default|
|• Issue 813 (2019-05-06): ROSA R11, MX seeks help with systemd-shim, FreeBSD tests unified package management, interview with Gael Duval|
|• Issue 812 (2019-04-29): Ubuntu MATE 19.04, setting up a SOCKS web proxy, Scientific Linux discontinued, Red Hat takes over Java LTS support|
|• Issue 811 (2019-04-22): Alpine 3.9.2, rsync examples, Ubuntu working on ZFS support, Debian elects new Project Leader, Obarun releases S6 tools|
|• Issue 810 (2019-04-15): SolydXK 201902, Bedrock Linux 0.7.2, Fedora phasing out Python 2, NetBSD gets virtual machine monitor|
|• Issue 809 (2019-04-08): PCLinuxOS 2019.02, installing Falkon and problems with portable packages, Mint offers daily build previews, Ubuntu speeds up Snap packages|
|• Issue 808 (2019-04-01): Solus 4.0, security benefits and drawbacks to using a live distro, Gentoo gets GNOME ports working without systemd, Redox OS update|
|• Issue 807 (2019-03-25): Pardus 17.5, finding out which user changed a file, new Budgie features, a tool for browsing FreeBSD's sysctl values|
|• Issue 806 (2019-03-18): Kubuntu vs KDE neon, Nitrux's znx, notes on Debian's election, SUSE becomes an independent entity|
|• Issue 805 (2019-03-11): EasyOS 1.0, managing background services, Devuan team debates machine ID file, Ubuntu Studio works to remain an Ubuntu Community Edition|
|• Issue 804 (2019-03-04): Condres OS 19.02, securely erasing hard drives, new UBports devices coming in 2019, Devuan to host first conference|
|• Issue 803 (2019-02-25): Septor 2019, preventing windows from stealing focus, NetBSD and Nitrux experiment with virtual machines, pfSense upgrading to FreeBSD 12 base|
|• Issue 802 (2019-02-18): Slontoo 18.07.1, NetBSD tests newer compiler, Fedora packaging Deepin desktop, changes in Ubuntu Studio|
|• Issue 801 (2019-02-11): Project Trident 18.12, the meaning of status symbols in top, FreeBSD Foundation lists ongoing projects, Plasma Mobile team answers questions|
|• Issue 800 (2019-02-04): FreeNAS 11.2, using Ubuntu Studio software as an add-on, Nitrux developing znx, matching operating systems to file systems|
|• Issue 799 (2019-01-28): KaOS 2018.12, Linux Basics For Hackers, Debian 10 enters freeze, Ubuntu publishes new version for IoT devices|
|• Issue 798 (2019-01-21): Sculpt OS 18.09, picking a location for swap space, Solus team plans ahead, Fedora trying to get a better user count|
|• Issue 797 (2019-01-14): Reborn OS 2018.11.28, TinyPaw-Linux 1.3, dealing with processes which make the desktop unresponsive, Debian testing Secure Boot support|
|• Issue 796 (2019-01-07): FreeBSD 12.0, Peppermint releases ISO update, picking the best distro of 2018, roundtable interview with Debian, Fedora and elementary developers|
|• Issue 795 (2018-12-24): Running a Pinebook, interview with Bedrock founder, Alpine being ported to RISC-V, Librem 5 dev-kits shipped|
|• Issue 794 (2018-12-17): Void 20181111, avoiding software bloat, improvements to HAMMER2, getting application overview in GNOME Shell|
|• Issue 793 (2018-12-10): openSUSE Tumbleweed, finding non-free packages, Debian migrates to usrmerge, Hyperbola gets FSF approval|
|• Issue 792 (2018-1203): GhostBSD 18.10, when to use swap space, DragonFly BSD's wireless support, Fedora planning to pause development schedule|
|• Issue 791 (2018-11-26): Haiku R1 Beta1, default passwords on live media, Slax and Kodachi update their media, dual booting DragonFly BSD on EFI|
|• Issue 790 (2018-11-19): NetBSD 8.0, Bash tips and short-cuts, Fedora's networking benchmarked with FreeBSD, Ubuntu 18.04 to get ten years of support|
|• Issue 789 (2018-11-12): Fedora 29 Workstation and Silverblue, Haiku recovering from server outage, Fedora turns 15, Debian publishes updated media|
|• Issue 788 (2018-11-05): Clu Linux Live 6.0, examining RAM consumpion, finding support for older CPUs, more Steam support for running Windows games on Linux, update from Solus team|
|• Full list of all issues|
Star Labs - Laptops built for Linux.
View our range including the Star Lite, Star LabTop and more. Available with a choice of Ubuntu, Linux Mint or Zorin OS pre-installed with many more distributions supported. Visit Star Labs for information, to buy and get support.
|Random Distribution |
MythDora was a specialized Linux distribution based on Fedora and MythTV, designed to simplify the installation of MythTV on a home theatre PC. In addition to MythTV and its plugins, MythDora includes extra Linux packages that are necessary for MythTV to run, and drivers for hardware commonly encountered in machines intended to run MythTV. Also included in MythDora are several video game emulators, and extra tools and scripts.