| DistroWatch Weekly
|DistroWatch Weekly, Issue 653, 21 March 2016
Welcome to this year's 12th issue of DistroWatch Weekly!
Ever since Canonical announced the next version of Ubuntu will ship with ZFS support, there has been a lot of debate in the Linux community over the potential licensing conflicts and the legality of shipping ZFS support in a Linux distribution. Meanwhile, the Arch-based Antergos distribution has already started supporting ZFS storage volumes in the project's installer. This week we begin with a look at the Antergos distribution, its ZFS support and the distribution's flexible system installer. Read on to find out what other features this rolling release distribution has to offer. In our News section we discuss Debian's upcoming election for Project Leader, talk about a new Unix-like operating system written in Rust and link to a tutorial that explains how to get Netflix working on PC-BSD and FreeBSD. In our Myths and Misunderstandings column we talk about version numbers, what they mean and why they can be confusing. Plus we share the torrents we are seeding and then provide a list of the distributions released last week. In our Opinion Poll we ask how our readers test new distributions prior to installing them. We wish you all a fantastic week and happy reading!
|Feature Story (by Jesse Smith)
Antergos is a cutting edge Linux distribution which is based on Arch Linux. The project creates a powerful desktop oriented operating system that supports several desktop environments and install-time add-ons. Around the middle of February the Antergos project released a snapshot carrying the version number 2016.02.19. At the time I downloaded the ISO image, but was unable to get the distribution to boot on my hardware. I then moved on to explore other projects, but then discovered the Antergos developers had released an updated ISO, this one labelled 2016.02.21. I downloaded this new ISO and found it booted on my test system and so proceeded to experiment with the distribution.
There are two editions of Antergos, "Antergos Live" and "Antergos Minimal". Both editions are available in 32-bit and 64-bit x86 builds. The Minimal edition is about 530MB in size while the larger edition is a 1.6GB download. I decided to explore the larger edition.
Booting from the Antergos live media brings up a menu asking if we would like to boot from the computer's hard drive, start a live graphical desktop session or boot Antergos in text mode. Taking the desktop option loads the GNOME Shell desktop environment. A dock on the left side of the screen provides access to a few commonly used programs and the Antergos system installer, which is called Cnchi. Shortly after the desktop finished loading, a message popped up in the upper-right corner of the screen and let me know the system was checking for updates to the Cnchi system installer. A few seconds later, I was assured I had the latest copy of the installer. Then another window appeared in the centre of the desktop and asked if I would like to explore the live desktop further or install the distribution.
Antergos 2016.02.21 -- MATE desktop and application menu
(full image size: 180kB, resolution: 1280x1024 pixels)
The Cnchi installer is a graphical application which starts by asking us to select our preferred language from a list. The next two screens ask us to supply our country and our time zone, which we can find on a map of the world. We then confirm our keyboard's layout. The following screen asks which desktop environment we would like to install with options including Cinnamon, GNOME, KDE, MATE, Openbox and Xfce. We also have the option of installing Antergos without a desktop environment and interacting with the operating system via a text console. I decided to run Antergos with the MATE desktop. The next screen asks which optional software packages we would like to install. There are several add-ons: The Arch User Repository (AUR), Bluetooth support, Firefox, Truetype Fonts, Adobe Flash, a long term support kernel, printing support, LibreOffice, Steam, PlayOnLinux, the Uncomplicated Firewall utility and Samba. I chose to install everything except the LTS kernel and Bluetooth support. One thing I like about the screen which lists the optional add-ons is hovering the mouse pointer over any item in the list displays a brief description of the package.
Disk partitioning comes next. We can either let the installer take over the computer's entire disk with some suggestions from us or we can manually divide up our disk. If we take the manual option, Cnchi offers us a very nice, streamlined partition manager where we can work with Btrfs, ext2/3/4, JFS, XFS, fsfs and Reiser file systems. I quite like Cnchi's manual partitioning screen, but one feature that caught my eye is the guided partitioning option features ZFS support. In fact, Antergos may be the only desktop Linux distribution I have used so far that enables ZFS support out of the box and I decided to try it. When ZFS is enabled we are given the chance to adjust some settings, such as telling Cnchi how big our swap partition should be, whether to enable mirroring or RAID support, whether we want our /home directory on its own sub-volume and the name of the ZFS storage pool. There are a lot of options, but most people can get by just by taking the default settings. Once disk partitioning has been handled, we are shown a list of the actions the installer will take and we are asked to confirm Cnchi may proceed. We are then asked to provide a username and password so the installer can create an account for us. The installer downloads the components we have selected and installs its files. Installation took a long time during my test runs. Each installation (I performed five in total) took over an hour, including the time to download and unpack all the optional packages. Since it seems the entire operating system (over 850 packages) is downloaded each time we install it, I would recommend only using Antergos on computers that have access to a high-speed Internet connection.
Our freshly installed copy of Antergos boots to a graphical login screen where a digital clock sits in the middle of the display. Pressing a key or clicking on the clock presents a login form where we can sign in. I found the login screen's elements offered very little contrast and it was difficult for me to see the input fields.
The first time I installed Antergos I was unable to sign into my user account, the system merely returned me to the login screen without providing an error message. Switching to a command line terminal, I was able to sign in, but found my user did not have a home directory. With a little exploring, I discovered that while the ZFS volume which housed the base operating system had been mounted, the sub-volume containing my home directory had not mounted. I also found I was unable to list the available volumes using the zpool and zfs command line utilities. Other ZFS related commands worked, but the ones used to list volumes would immediately crash. I suspect this explains why the /home sub-volume did not mount properly. At this point I discovered I could fix the problem in one of two ways. I could place the command "zfs mount data/home" in a start-up script and that would force the sub-volume to mount and allow me to login to my account. The alternative was to run through the install process a second time, choosing to place all my data on one ZFS volume. I opted to try the latter approach to confirm everything would work properly if I kept the /home directory in the main storage volume.
Going through the Cnchi installer a second time and putting all my data on one storage volume did work as expected. However, I did discover a second problem: Cnchi is unable to remove existing ZFS pools. The user needs to manually destroy any existing ZFS volumes before trying to install Antergos on the hard drive. Otherwise the installation fails when Cnchi fails to remove the old ZFS volume.
Antergos 2016.02.21 -- Running various desktop applications
(full image size: 227kB, resolution: 1280x1024 pixels)
Once I got the ZFS volume and login issue sorted out, I was able to sign into my account and begin exploring the MATE 1.12.1 desktop environment. The desktop places the application menu and system tray at the top of the screen. A task switcher panel sits at the bottom. The background is plain blue. MATE's application menu is presented as one menu divided into three sections: Applications, Places and System. The Applications section of the menu is then further divided into Favourites and All Applications. Selecting All Applications splits the menu again with categories of software displayed to the left and specific applications from each category shown on the right. Personally, I found the menu to be both cluttered and a bit too nested for my taste as it always felt like there were a few extra steps involved in finding the application I wanted. I do want to give the menu designers credit though for making it easy to move applications from the depths of the nested menu to the Favourites section via a context menu, reducing the time it took to access frequently run programs.
In the system tray there is an icon which indicates when security updates are available. Right-clicking on the update icon gives us the option of launching the distribution's software manager or an update manager. Left-clicking the icon immediately launches the update manager. The update manager displays a simple list of available software updates waiting in the Antergos repositories. Each item in the list is displayed with the package's name and size. We can check a box next to each update to indicate whether we wish to install it. On my first day using Antergos, there was one update available, less than 1MB in size. The following day there were two more updates, each also smaller than 1MB. By the end of the week, more than 30 additional updates became available, totalling 91MB in size. The update manager successfully downloaded and installed each of the waiting packages.
By default, it seems the update manager does not check the Arch Linux AUR repository for new software updates. We can enable checks for updates in the AUR by opening the update manager's settings and putting a check in the appropriate box.
Antergos 2016.02.21 -- Managing packages with Pamac
(full image size: 172kB, resolution: 1280x1024 pixels)
Antergos ships with a graphical package manager called Pamac. The Pamac window is divided into two main panes. On the left we can set parameters for finding software. The left pane has tabs that will help us search for software by name, by category, by status or by repository. On the right side of the window is an alphabetical list of packages that match our current search parameters. Each package is displayed with its name, size and version number. We can click a box next to a package to choose whether to install or remove the selected item. Pamac is remarkably responsive and fairly easy to navigate. It may not be pretty, but it is certainly functional.
My one serious complaint with Pamac is that the available software categories are oddly specific and not always intuitive. Instead of the "Internet", "Graphics" and "Office" categories usually found in other package managers, we are presented with dozens of technical names like "Base", "System", "Qt", "Qt5" and "xorg-drivers". I suspect most new users are going to struggle with names like these. I encountered some confusion myself when searching for specific packages. For instance, there is a "Browsers" category where we can find web browsers, but there is also a "Firefox" category which does not contain the Firefox web browser, only plug-ins for Mozilla's web browser. There is an "Email" category which only contains one email client, but if we search for the term "email" in the search tab Pamac offers us a list of half a dozen email applications. The "System" category has ZFS packages and utilities, but the "ZFS" category does not contain ZFS utilities. This sort of maddening behaviour caused me to search for most items using keywords rather than categories. For people who want to manipulate software from the command line, Antergos ships with the pacman package manager. The pacman utility is very fast, though I find its syntax more terse (perhaps even cryptic) compared to other command line package managers.
Antergos 2016.02.21 -- The settings panel
(full image size: 200kB, resolution: 1280x1024 pixels)
Antergos provides us with a control panel where we can launch configuration modules to change our desktop environment and manage some aspects of the operating system. The control panel has modules for changing the desktop's theme and wallpaper. We can also find modules for managing printers, setting up network connections, configuring the firewall, the screen saver and start-up applications. These modules generally worked well. One module, the one for configuring the firewall, always failed to launch. I also regretted that I was unable to find a module for working with user accounts, either in the control panel or in MATE's application menu. Another minor annoyance appeared while I was using the Appearance module which changes the look and theme of the desktop. At one point I accidentally clicked on an alternative theme, causing MATE to immediately change its look. The original theme, called Custom, was immediately lost, preventing me from switching back. This quirk is not specific to Antergos, but rather seems to be common across distributions which ship with a special "Custom" MATE theme.
The distribution ships with a varied and useful collection of software. Looking through the application menu we find the Firefox web browser with Adobe's Flash plug-in, the Pidgin instant messenger software and the Transmission bittorrent software. LibreOffice is available along with the Atril document viewer and the Eye of MATE image viewer. PlayOnLinux and Steam are available to help us install Windows software and Linux games, respectively. Unfortunately, Steam would not launch on my test system. PlayOnLinux did work most of the time, but was not always able to successfully complete installations of Windows applications. The Pragha audio player and Totem video player are included. I found I was able to play music files, including mp3 files, in Pragha. However, I was not able to play video files using Totem. I downloaded a copy of the VLC media player from the Antergos software repository and found VLC was able to play my video files. Antergos also ships with the Xfburn optical disc burning software, a text editor, calculator and archive manager. Antergos ships with the GNU Compiler Collection for developers. In the background we find systemd 229 and version 4.4.1 of the Linux kernel.
The first user we create when setting up Antergos has the ability to perform administrator actions using the su and sudo commands. This concerns me a little as I do not think there is any part of the installation which asks us to set up a root password. It seems as though the root password is just automatically set to match the first user's account. Personally, I would rather the root account have its own password or the system lock root and get users to perform administrative actions using sudo exclusively. Having one password to access two accounts feels like a potential problem to me.
I tried running Antergos in two test environments, a physical desktop computer and a VirtualBox virtual machine. Antergos performed well in both environments, properly detecting my hardware and running smoothly. My one complaint was that when booting Antergos took over a minute and a half to reach the login screen. I am uncertain if this is an issue specific to ZFS or a result of some services (like dev-disk) which took an unusually long time to start-up. However, once the system had booted, Antergos was responsive. The distribution, with all optional add-ons installed, used about 6GB of disk space, plus a 500MB /boot partition formatted with the ext4 file system is set aside when we install Antergos on a ZFS volume. When logged into the MATE desktop, Antergos used approximately 560MB of memory. Some opponents of ZFS like to state the file system requires several gigabytes of RAM, but the ability to run the operating system, MATE and ZFS with under 600MB of memory indicates none of the distribution's components is particularly heavy.
Throughout the week, I was impressed with the features Antergos brings to the table. There is a lot of cutting-edge software included in the distribution. Antergos worked well in both of my test environments, has a very friendly system installer and lots of useful features. I especially like how the project ships one ISO image and we can select our desktop and add-ons from the Cnchi installer. This gives us a good deal of flexibility without cluttering up the project's download page with extra editions. I was also happy to see Antergos supports both Btrfs and ZFS as both are useful, advanced file systems. This may be the first Linux desktop distribution I have encountered which supports ZFS at install time.
However, on the other hand, I occasionally ran into problems. Usually small things, but ones that made Antergos feel less polished. For example, I mentioned earlier that asking the installer to place our /home partition on its own ZFS sub-volume would cause /home to not be mounted at all. Also, while most ZFS functions worked, listing volumes and snapshots did not, which puts a damper on some of the more useful ZFS functions. The Steam gaming portal did not work for me and Totem was unable to play my video files and I had to install an alternate media player. Most configuration modules worked beautifully, particularly the printer manager, but the firewall utility failed to launch.
I think the Antergos project is doing some interesting things and the developers are providing a great deal of flexibility combined with cutting edge software. Personally, I wish there was an off-line version of the Cnchi installer so I did not need to wait so long for packages to download each time I installed the distribution. And I did run into a few problems. However, overall I liked Antergos. The distribution is fast, easy to customize and provides access to a huge repository of software via the main repositories and Arch Linux's AUR community repository.
* * * * *
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
|Miscellaneous News (by Jesse Smith)
Debian prepares for Project Leader election, Redox developers create Unix-like OS, and a tutorial for watching Netflix on PC-BSD
Each year the Debian project elects a leader who helps guide and coordinate the efforts of groups within the Debian family of contributors. The election for Debian's next Project Leader is underway and it looks as though there will not be any competition for the office. At the moment, there is just one nomination: Mehdi Dogguy. Voting in the election will take place from April 3rd through to April 16th and it seems likely Dogguy will then take over the job of leading the hundreds of Debian developers. Dogguy has stated he would like to create a central roadmap for Debian which would outline a list of goals the distribution will strive to achieve in each release cycle: "I will initiate an effort in order to help our project to publish a roadmap; have each item described in a S.M.A.R.T way and make sure progress is made. I am sure that each team has its own set of ideas to implement. However, it is important to centralize those ideas to give them more visibility and have a better understanding of the big picture." The rest of Dogguy's platform is available on the Debian website.
* * * * *
Redox is a Unix-like operating system that is written in the Rust programming language. Rust is considered safer than traditional languages, such as the C language which is used to develop the Linux kernel. Redox uses a microkernel design and runs drivers in userspace for improved security and reliability. The developers have also stated their operating system will support the ZFS advanced file system. The project's documentation states that Redox will support running some Linux applications without virtualization. "Redox is a general purpose operating system and surrounding ecosystem written in pure Rust. Our aim is to provide a fully functioning Linux alternative, without the bad parts. We have modest compatibility with Linux syscalls, allowing Redox to run many Linux programs without virtualization. We take inspiration from Plan9, MINIX, and BSD. We are trying to generalize various concepts from other systems, to get one unified design." Redox development is still in its early stages, but the most recent release is reported to work on some hardware as well as in VirtualBox and Qemu virtual environments.
* * * * *
Accessing the Netflix video streaming service is a task that has posed a problem for FreeBSD and PC-BSD users for some time. It's a situation many FreeBSD users find frustrating as Netflix uses FreeBSD servers to provide their content. While Linux users can access their Netflix accounts using Google's Chrome web browser, the closed-source Chrome browser does not run on FreeBSD-based systems. Chrome has also resisted attempts to run it through both the WINE compatibility software and FreeBSD's Linux emulation software. One enterprising PC-BSD user has found a workaround which involves Pipelight and the Firefox browser that allows PC-BSD (and FreeBSD) users access Netflix. A video tutorial which explains how to set up Pipelight with Firefox is available. The video also covers some trouble-shooting steps in case things do not immediately work as planned.
|Myths and Misunderstandings (by Jesse Smith)
The value of version numbers
When it comes to software, version numbers are everywhere. If you check with your distribution's package manager you will see each component of the operating system has its own version number and these numbers mean something. Though what they mean varies a lot, depending on the project that develops the software.
A common source of confusion I often run into comes from the way people interpret version numbers. You might have heard someone say, "I never install a point-zero (x.0) release. Wait until x.1 or x.2 has been released before trying it." Or perhaps you have heard people say the opposite: "This version should be stable, the project has hit version x.0."
To be fair, in certain contexts, either of the above statements can be true. There are projects which produce multiple development builds prior to launching an x.0 release and their x.0 version will likely be stable. But there are also projects which push out x.0 releases as an early preview of things to come and their software might not be stable until x.2 or x.3 of the series arrives.
The unfortunate truth is there is no common practice when it comes to version numbers. Some projects use complex version numbers that carry a good deal of information. For example, one project might use "4.10.2" to indicate the 4th major version with 10 feature revisions and 2 minor patches. Another project might use "4.9" to indicate the version that comes after "4.8". Yet other projects create version numbers based on the date their project ships. All of these are valid ways to track software, the problem arises when people try to treat all version numbers in the same way. The truth is, whatever rules a project uses for labelling their software, those rules apply only to that project and do not automatically translate to other pieces of software.
As an example, I have worked on a few open source projects which used incremental version numbers. For instance, 4.8 was followed by 4.9, then 5.0, 5.1 and 5.2. It was a surprise to me how often our mailing list received comments from our users along the lines of, "There are a lot of great changes in this update. It feels like more of a 5.0 than a 4.6." Or perhaps, "This 6.0 release sounds good, but I'm going to wait for 6.1 or 6.2." Both sets of comments ignored how the project's versioning system worked. It didn't matter if we piled on lots of new features or spent the entire release cycle working on bug fixes, in the end the version number went up an additional 0.1.
I feel it is important to remember when looking at a product's version numbers that each project handles them differently. When in doubt, it is a good idea to ask on a mailing list or forum what kind of versioning scheme the project uses before trying to evaluate the software.
Another common mistake I encounter comes from people using version numbers to determine whether their distribution has addressed a security vulnerability. Often times, when a distribution patches a vulnerable piece of software, they do not increase the package's version number. For instance, let's say I am running a program called Foo with the version number 4.0. It comes to light that Foo 4.0 is vulnerable and the developers of Foo release a fixed version, Foo 4.1.
Often times, distributions will not package Foo 4.1 because it contains more than just the security fix, it also has a bunch of new features which have not been properly vetted. What they may do instead is copy just the fix from Foo 4.1 into their package of 4.0. Then I download the patched version of Foo 4.0 from the distribution's repositories and I'm safe. But, if I check the version number of Foo, I see it's at 4.0 when I know everything prior to 4.1 is considered vulnerable.
Package maintainers are in a difficult spot in these scenarios because if they keep the 4.0 version number, many people will think their software is outdated and contains the security vulnerability. But if they bump the version number of Foo to 4.1, then people will wonder why their software is missing the features advertised for the new version of Foo. Sometimes distribution package maintainers will add an extra version number to the end of the package, labelling their software Foo 4.0-1 or 4.0.1. That helps people keep track.
In the end, the best way to find out if your copy of a package has been patched against security vulnerabilities is not by looking at the version number, but rather checking the package's change log. This can be accomplished a few different ways, depending on the operating system you are running. On Debian and related distributions such as Ubuntu, the apt-get command will show recent changes and fixes applied to a package. For instance, to check on changes to the gcc package we would run:
apt-get changelog gcc
On Fedora and related distributions the equivalent command using the rpm package manager is:
rpm -q --changelog gcc
Other package managers have similar changelog and auditing features which can help identify fixed (or still vulnerable) software.
In the end, version numbers can be helpful, but they need to be viewed in context and they are usually not a good method for checking the state of a package's security.
Bittorrent is a great way to transfer large files, particularly open source operating system images, from one place to another. Most bittorrent clients recover from dropped connections automatically, check the integrity of files and can re-download corrupted bits of data without starting a download over from scratch. These characteristics make bittorrent well suited for distributing open source operating systems, particularly to regions where Internet connections are slow or unstable.
Many Linux and BSD projects offer bittorrent as a download option, partly for the reasons listed above and partly because bittorrent's peer-to-peer nature takes some of the strain off the project's servers. However, some projects do not offer bittorrent as a download option. There can be several reasons for excluding bittorrent as an option. Some projects do not have enough time or volunteers, some may be restricted by their web host provider's terms of service. Whatever the reason, the lack of a bittorrent option puts more strain on a distribution's bandwidth and may prevent some people from downloading their preferred open source operating system.
With this in mind, DistroWatch plans to give back to the open source community by hosting and seeding bittorrent files. For now, we are hosting a small number of distribution torrents, listed below. The list of torrents offered will be updated each week and we invite readers to e-mail us with suggestions as to which distributions we should be hosting. When you message us, please place the word "Torrent" in the subject line, make sure to include a link to the ISO file you want us to seed. To help us maintain and grow this free service, please consider making a donation.
The table below provides a list of torrents we currently host. If you do not currently 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 here. All torrents we make available here are also listed on the very useful Linux Tracker website. Thanks to Linux Tracker we are able to share the following torrent statistics.
Torrent Corner statistics:
- Total torrents seeded: 174
- Total data uploaded: 32.3TB
|Released Last Week
Anke Boersma has announced the release of KaOS 2016.03, the latest stable version of the desktop Linux distribution that features the latest Plasma desktop from KDE: "KaOS is proud to announce the availability of the March release of a new stable ISO image. The Plasma desktop includes Frameworks 5.20.0, Plasma 5.5.5 and KDE Applications 15.12.2. A few enhancements to the Plasma 5 experience have been added, these are KaOS-specific extras. You now have the option to calculate the MD5 sum from any file from the Dolphin service menu. Since the kf5 move there has not been a fully working GUI for user management, but there is one added now for KaOS - you will find it under system settings, account details. From there you can create new users, change existing user's role or delete a user. Also added is a KCM for locale and language settings. A new icon theme for light and dark themes has arrived. The Midna Dark theme received a complete overhaul with a new Plasma theme, window decorations, color scheme, and new SDDM and splash themes." Read the rest of the release announcement for further details and screenshots.
KaOS 2016.03 -- Welcome screen and drop-down terminal
(full image size: 212kB, resolution: 1366x768 pixels)
The Robolinux project has announced the availability of a new stable release of the project's Robolinux Raptor series. The new release, Robolinux 8.4, is available in Cinnamon, LXDE, MATE and LXDE flavours and features several privacy and anti-malware tools. " All Robolinux Raptor 8.4 versions are based on 100% rock solid current Debian 8 stable source code running the newest Debian 3.16 Linux kernel plus over 180 important upstream security and application updates. We also included the newest Firefox 45 and Thunderbird 38.7, Tor Browser, VirtualBox and replaced all of our 32-bit operating systems end of life Google Chrome versions with Chromium." A list of changes and available security tools can be found in the distribution's release announcement.
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
How do you test new distributions?
Before installing a new operating system it is nice to know whether the software will work as intended. There are a number of ways to test a Linux distribution before we install it. Most projects provide live media, allowing us to experiment with the distribution's hardware support, performance and default applications before installing the operating system. Other tools, such as virtual machines, allow us to perform a test installation before making space for a new system on our hard drive. Some people keep test machines around to assist in exploring new distributions.
This week we would like to know how you test a distribution before installing it to your computer's hard drive.
You can see the results of our previous poll on purchasing computers with Linux pre-installed here. All previous poll results can be found in our poll archives.
How do you test new distributions?
|Using a live disc/USB thumb drive: ||828 (37%)|
| Installing it in a virtual machine: ||519 (23%)|
| Running it on a spare computer: ||200 (9%)|
| A combination of the above: ||604 (27%)|
| None of the above: ||75 (3%)|
Distributions added to waiting list
- Studio 13.37. Studio 13.37 is a commercial distribution for audio and video production. The distribution runs from a live USB thumb drive.
- ubuntuBSD. ubuntuBSD combines the installer and utilities of Ubuntu with the kernel and file system support of FreeBSD.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 28 March 2016. 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)
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 0, value: US$0.00)
|Linux Foundation Training
|• 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|
|• Issue 707 (2017-04-10): PCLinuxOS 2017.03, Canonical stops Unity development, OpenBSD on a Raspberry Pi, setting up a VPN for privacy|
|• Issue 706 (2017-04-03): Super Grub2 Disk, Snap packages of deepin applications, Subgraph OS routes network traffic for one application, announcements from Linux Mint|
|• Issue 705 (2017-03-27): Minimal Linux Live, sharing control of the operating system, new KaOS features, Uplos32 provides 32-bit fork of PCLinuxOS|
|• Issue 704 (2017-03-20): ToarusOS 1.0.4, Linux Mint's security record, Debian starts Project Leader election, Ubuntu 12.04 reaches end-of-life|
|• Issue 703 (2017-03-13): SolydXK 201701, CloudReady, Solus announces new features, KDE Connect sends text messages from desktop, openSUSE's YaST module for Let's Encrypt|
|• Full list of all issues|
|Random Distribution |
Dzongkha Linux was a Debian-based distribution developed in Bhutan by the Department of Information Technology at the Ministry of Information and Communications. Dzongkha Linux was created with the sole aim of providing complete Dzongkha computing capability, free of cost.