| DistroWatch Weekly
|DistroWatch Weekly, Issue 657, 18 April 2016
Welcome to this year's 16th issue of DistroWatch Weekly!
One of the more exciting aspects of the open source community is that there are always people trying something new. There is always a new design on the horizon, waiting to be tested and either adopted or discarded. This week we focus on new technologies that are currently available or will soon be ready to download. We begin with a look at Redox, a UNIX-like operating system written in Rust that includes some interesting design choices. In our News section we cover improvements to Linux Mint's update manager and changes planned for the next release of Fedora. Plus FreeNAS has decided to upgrade older versions of Samba following the Badlock bug and we discuss Canonical's plan to support Snappy packages in Ubuntu 16.04. In our Questions and Answers column we talk about menus and short-cuts in various desktop environments. Then we share the torrents we are seeding and explore last week's releases. In our Opinion Poll we raise the idea of voting for distributions on our waiting list. Plus we share a new resource where readers can find hardware that works with open source operating systems. We wish you all a wonderful week and happy reading!
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (22MB) and MP3 (30MB) formats
|Feature Story (by Jesse Smith)
An introduction to Redox
Back in March, a young operating system project attracted attention in the open source community. The project is called Redox and its developers are working on a Unix-like operating system written in the Rust language. The Redox operating system features a microkernel design (like MINIX), the permissive MIT license and some interesting design ideas.
While I read a lot of opinions in March about the developers and their design goals, I encountered very little commentary on what it was like to use the young operating system itself. This led me to become curious and download the project's small installation ISO which is just 26MB in size.
Before getting into my experiences with Redox, I want to talk briefly about some of the design decisions the developers have made. They seem to feel that Unix (or related operating systems like Linux distributions) has a generally good design, but with some key flaws or hangovers from past decades. For example, the project's documentation suggests that Unix's "Everything is a file" concept is dated and their modern design declares "Everything is a URL". In a way, this makes sense. On Linux, our hard drive is treated like a file under the /dev directory, so we can end up in some strange conceptual territory when we realize we are working in a directory on a device that is located in another directory. Redox's "Everything is a URL" philosophy works around such issues by giving users a way to access devices which are not part of the file system. Personally, I think the developers are trading one set of problems for another by using URLs, but I acknowledge they have highlighted an issue and provided a workaround.
The Redox project also takes the stance that the C programming language may produce fast running applications, but quite often security and stability issues can be traced back to quirks of the C language or common mistakes made by C programmers. Rust strives to be more secure and offers some protection against common implementation problems. By using Rust instead of the traditional C language in development the Redox programmers hope to make a more stable and more secure operating system.
Design aside, let's look at what happens when we boot from Redox's installation media. Booting from the Redox media takes about three seconds and brings us to a text console. We are presented with a message suggesting we run "redox-installer" to set up the operating system. A quick examination of the command line interface reveals that we are running a minimal shell and we have root access. Exploring a little further I found that the installation media actually runs a minimal Linux distribution. The usual /etc, /bin and /proc directories exist along with the BusyBox collection of Unix utilities. We have access to the vi editor and commands to browse directories, monitor system processes and read manual pages (though no documentation files exist on the system). In the background the installation media runs version 4.4.3 of the Linux kernel. The whole live environment uses approximately 10MB of memory, making it a surprisingly compact Linux implementation.
Of course I did not download the Redox ISO in order to play with Linux, I wanted to experience something new. I looked at the redox-installer file and discovered it is a simple, 12 line shell script. The script presents us with a list of local hard drives and asks on which one we wish to install Redox. The script then confirms our choice and, without further customization or prompts, uncompresses a file containing the Redox operating system and writes it to our hard drive using the dd command. Hopefully nothing of importance was on that hard drive.
I tried working with Redox in a VirtualBox virtual machine and on a physical desktop computer. In both instances, the Linux-based installation media booted, but the installed Redox operating system did not. For the time being, it seems Redox is not yet at a point where I can run it in any practical sense, though I have heard from another user who was able to get Redox installed in a virtual machine.
For those lucky folks who are able to get Redox running, the operating system is not yet at a point where development of Redox can be performed on Redox. Put another way, there are not yet enough tools and development utilities in place to work on Redox from within Redox. The operating system exists in more of a proof-of-concept stage than as a practical platform at this point.
When Redox first started getting attention on various open source forums, there were many negative voices criticizing the project. And, to a point, that is to be expected. If someone mentions on-line that they are enjoying a salad for lunch, by supper someone will have drawn a parallel to Hitler being a vegetarian. But sifting through the reactions to Redox I found that most of the critics seemed to be engaged in shooting the messenger.
From what I have read of their design plans, the Redox developers have correctly identified some problems with Unix, GNU/Linux and the BSDs. Some of their opinions on operating design I may not agree with, but I do believe they raise points worth considering and, in some cases, are correct in pointing out issues with existing operating systems which could be fixed. The Redox developers point out the C language, which is typically used for kernel development, has weaknesses when it comes to protecting memory and using variable types. Hardly a day goes by when I do not read a bug report that traces back to these same weaknesses, making it difficult to argue with the Redox developers. Rust, the Redox team claims, would avoid these common problems and they may be right. I do not think we are likely to see anyone try re-write the Linux kernel in Rust, but doing more to mitigate the dangers of using C to develop Linux should be considered.
Likewise, the Redox team points out that having a smaller kernel with drivers running outside of the core kernel makes the system safer and possibly more stable. I tend to agree and some projects, like MINIX, have done some remarkable things to help systems recover from faulty modules or to upgrade drivers in place without requiring a reboot.
My point is that the Redox team has come along and pointed out various issues with how our favourite operating systems are designed and developed. This makes some people defensive and leads to people lashing out against the new ideas presented. And I feel that reaction is not helpful. GNU/Linux and BSD systems are practical and widely used, but that does not make them perfect. Our established operating systems tend to carry with them a good deal of legacy concepts and potential weaknesses that come from being around for multiple decades. I am not saying we should throw them away and start over, that wouldn't be at all practical. But I am suggesting we consider if there are ways we might improve our existing systems.
Redox may never be a practical replacement for GNU/Linux distributions, but it might serve as a testing platform for ideas that could be adopted by other operating systems. The uutils project, for example, seeks to recreate the GNU core utilities in Rust to make them more portable and less prone to memory issues. While uutils may never replace the GNU programs, they might offer advantages or design ideas we can all benefit from. Let's not write off projects like Redox or uutils because they are different or trying to accomplish a task that has been done before. Their developers are testing ideas which we might all benefit from one day.
* * * * *
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)
New features coming to Linux Mint, highlights of Fedora 24, FreeNAS bumps Samba version and Ubuntu 16.04 to support Snappy packages
In their monthly newsletter, the Linux Mint team discussed some of the new improvements coming to the Linux Mint distribution. One of the new key features offers better handling of kernels in the update manager. The update manager will also provide more information about software updates and how they relate to stability and regressions, allowing the user to select an update policy. "The Update Manager was already configurable, but it wasn't clear how to configure it, and why. In particular, the concepts of regressions, stability and security weren't clearly explained and users had to acquire these online. To raise awareness around these concepts and show more information, a new screen welcomes users to their update manager and asks them to select an update policy." Touchpad support has also been improved in the MATE and Cinnamon desktop environments.
* * * * *
The next version of Fedora is expected to launch in June of this year and the Red Hat-sponsored distribution has a number of important changes planned. The Marksei blog has a summary of important changes arriving with Fedora 24. Key features include all packages being built with the new GNU Compiler Collection (version 6), the Fedora Server edition will be 64-bit only and an Astronomy spin will be available. The blog reports systemd will be split into multiple packages and Fedora will ship with version 4.5 of the Linux kernel, with 4.6 available as an optional update. One of the bigger changes for developers will be the availability of Docker images: "Starting with version 24 a new service to build Docker Images will be available. This will enable to produce more than one base image to provide additional layered software (like Cockpit) and enable contributors to modify Dockerfiles from which Docker Images will be built. More can be found here."
* * * * *
Last week there was a lot of hype surrounding the Badlock vulnerability in Samba. Though some of the concern over the vulnerability was unwarranted, open source projects have been quick to update their Samba packages and push out updates. The FreeNAS project, when faced with backporting a complex fix, decided to take this opportunity to upgrade older installations of the Samba file sharing software. Jordan Hubbard commented, "Because of the complexity of the fixes to Samba and the difficulty in back-porting them to Samba 4.1, we also decided to upgrade all TrueNAS/FreeNAS 9.3 users to Samba 4.3.6 - a newer and more capable version of Samba that is already in use by FreeNAS 9.10 - at the same time. FreeNAS 9.10 users will only see a fix for Badlock, not a Samba upgrade as well."
* * * * *
Snappy packages, which were introduced as an experimental technology for Ubuntu last year, will be available to Ubuntu 16.04 users later this month. The new Snappy packages can be installed alongside traditional Deb packages on Ubuntu 16.04, allowing users to install more up to date software on their long term support release. "Snap packages enable developers to bring much newer versions of apps to Ubuntu 16.04 LTS. Newer versions of KDE, GNOME, browser or other desktop environment apps will usually build easily on older LTS releases, but the complexities of packaging and providing updates have prevented us from delivering them in the past. The security mechanisms in snap packages allow us to open up the platform for much faster iteration across all of our flavours as snap applications are isolated from the rest of the system. Users can install a snap without having to worry whether it will have an impact on their other apps or their system. Similarly, developers have a much better handle on the update cycle as they can decide to bundle specific versions of a library with their app. Transactional updates make deployments of snap packages more robust and reliable." Further details on Snappy packages and Ubuntu's Desktop edition can be found in this Insights post. A cheat sheet of Snappy package manager commands can be found on our Package Management page.
* * * * *
These and other news stories can be found on our Headlines page.
|Questions and Answers (by Jesse Smith)
Menus, short-cuts and accessibility
Hoping-for-a-more-accessible-desktop asks: Using my desktop computer, I often want to use the keyboard to cycle the focus (using Tab or Shift+Tab) and navigate menus (using Alt+[underlined letter in each menu item]). In their default configuration, many distros make this difficult. I'm not visually impaired, yet low contrast (or none at all) and one pixel thin rectangles (or none at all) make it hard to distinguish between focused and unfocused elements to see where the focus is. As far as I recall, even a high contrast theme failed to address this particular problem. Alt key short-cuts are sometimes missing, and sometimes not readily apparent.
I guess I can improve focus contrast by adjusting the values for border thickness and colour, but which lines exactly, in which file?
As for the Alt key neglecting problem, I do not know which software layer (i.e. individual application, window manager, desktop environment, distro etc.) is responsible for this, so I don't know which part I'd have to replace. Also, I wouldn't know which alternative is more supportive of menu navigation by Alt key. Any suggestions would be greatly appreciated.
DistroWatch answers: This is one of those questions that I thought I would spend about five minutes researching, find out what toggles the visibility of Alt key short-cuts and spend another five minutes writing out the solution. As it turned out, exploring this problem took a lot longer than I expected and the more I looked at it, the deeper the rabbit hole became.
In the desktop environments I tend to use most (Lumina and KDE), Alt short-cuts, window borders and selected GUI elements are all recognizable and easily accessible. This made me wonder just which systems were using lower contrast elements and not displaying Alt key short-cuts. So I grabbed a computer, installed the major desktop environments (Cinnamon, GNOME, KDE, Lumina, LXDE, MATE and Xfce) on it and tested each environment to see how each one presented its menus and selected elements.
At first it seemed as though menu Alt key short-cuts and highlighting contrast were a function of the desktop environment. Specifically, Qt-based desktops such as KDE and Lumina would show me high contrast GUI elements and display menu Alt key short-cuts. Meanwhile, the GTK-based desktops like Cinnamon and GNOME did not show these short-cuts and featured lower contrast elements. However, my initial hypothesis was proven false when I realized applications in Xfce and LXDE (both GTK-based environments) did display Alt short-cuts and made seeing selected items easy. I modified my working theory to suggest GTK2 and Qt desktops would, by default, draw the Alt short-cuts and display high contrast items while GTK3-based desktops would not.
Closer inspection revealed my premise to be wrong when I started to run GTK3-based software in Qt-based desktop environments. If I ran a GTK3 application in Qt-based desktop environments such as Lumina or KDE, then the application's menu items and Alt short-cuts would be displayed. And if I ran a Qt-based application in a modern GTK3 desktop, its elements would also be displayed in high contrast and its Alt short-cuts would be displayed. In fact, if I ran a GTK3 application in a GTK2 desktop environment, like Xfce or LXDE, then elements and short-cuts were also more accessible.
What this led me to is the idea that Alt keyboard short-cuts and low-contrast GUI elements appear to result from a combination of GTK3-based applications running in GTK3-based desktop environments. Running Qt-based (or GTK2-based) applications in any desktop environment usually (not always, but usually) caused the Alt short-cuts to be displayed and resulted in graphical elements that were easier to see and interact with.
Which raised the question of how to make Alt short-cuts, borders and highlighted elements more visible when working in pure GTK3 environments. One thing I noticed was when working with GTK3 applications, if I used the mouse to click on an application's menu, Alt short-cut keys were not displayed. However, if I held down the Alt key then the short-cuts became visible. This is not ideal as it requires we hold down the Alt key, but it works. I also found suggestions on various forums that said using either of the two following commands would make Alt key short-cuts permanently visible in GTK environments:
dconf write /org/gnome/desktop/interface/automatic-mnemonics false
And, for older versions of the GNOME desktop:
gsettings set org.gnome.desktop.interface automatic-mnemonics false
While some people reported success using the above commands, they did not work for me in my test environments.
I also found that the accessing menus of some modern GTK3 programs using my keyboard did not work as there appeared to be no short-cut key (at least none I could find) to open some of the menus. Some modern applications divide up their menus into separate, isolated entities just represented by icons. Some menus have Alt short-cuts while others, apparently, do not. I found this inconsistency quite frustrating and I was happy to leave such applications for better alternatives. So far as I have been able to find, there is no solution for this type of bad design.
In the end, I found there really is not much consistency in the design and behaviour of Linux desktop applications and there is a variety of behaviour depending on which desktop environment is in use. This makes finding a single solution, whether it is a theme or setting or configuration option, difficult. Some applications, especially those developed for GNOME Shell, appear to be very focused on mouse and touch interfaces, but largely ignore or hide short-cuts when accessed via a keyboard.
My suggestion is to experiment with different desktop environments and applications. For instance, use KDE or LXQt instead of GNOME if keyboard input and Alt short-cuts are important to you. Look into using VLC instead of Totem for playing video files if you like to keep your hands on the keyboard. Rather than trying to alter the behaviour of specific applications or desktops, the best solution is probably to find the tools designed with your preferences in mind.
As for things like contrast and the size of window and element borders, these can usually be adjusted by using different themes. Distributions typically offer multiple themes for each desktop environment and experimenting with the alternative desktop themes will probably fix the remaining issues, such as element contrast and borders.
* * * * *
Past Questions and Answers columns can be found in our Q&A Archive.
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: 184
- Total data uploaded: 34.5TB
|Released Last Week
Chris Buechler has announced the availability of pfSense 2.3. The new release of this FreeBSD-based firewall operating system includes a number of new changes to its web interface and fixes several bugs from previous releases. "We are happy to announce the release of pfSense® software version 2.3! The most significant changes in this release are a rewrite of the webGUI utilizing Bootstrap, and the underlying system, including the base system and kernel, being converted entirely to FreeBSD pkg. The pkg conversion enables us to update pieces of the system individually going forward, rather than the monolithic updates of the past. The webGUI rewrite brings a new responsive look and feel to pfSense requiring a minimum of resizing or scrolling on a wide range of devices from desktop to mobile phones. For the highlights, check out the Features and Highlights video. Past blog posts have covered some of the changes, such as the performance improvements from tryforward, and the webGUI update." Further information can be found on the project's Features and Changes page.
IPFire 2.19 Core 100
The IPFire project has released the 100th update to the project's 2.19 branch. The new version, IPFire 2.19 Core 100, introduces a 64-bit build along with an updated Linux kernel. "It is a great moment to us and we are very proud to release the 100th Core Update today. This update will bring you IPFire 2.19 which we release for 64-bit on Intel (x86_64) for the first time. This release was delayed by the various security vulnerabilities in OpenSSL and glibc, but is packed with many improvements under the hood and various bug fixes." A number of fixes have been backported to the project's Linux kernel: "As with all major releases, this one comes with an updated Linux kernel to fix bugs and improve hardware compatibility. Linux 3.14.65 with many backported drivers from Linux 4.2 is also hardened stronger against common attacks like stack buffer overflows. Many firmware blobs for wireless cards and other components have been updated just as the hardware database." Additional information can be found in the project's release announcement. Download (SHA1): ipfire-2.19.x86_64-full-core100.iso (159MB, torrent, pkglist)
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
Voting for distros on the waiting list?
We received a lot of distribution submissions with multiple new projects appearing in our inbox every month. While we try to evaluate each new distribution and move quality projects from our waiting list to the DistroWatch database in a timely manner, sometimes promising projects fall through the cracks. Other times a project might take time to mature, but then be forgotten and remain stuck on our waiting list.
Sometimes people will e-mails us to bring an up and coming distribution to our attention, other times we catch word of exciting distributions on forums. Unfortunately, there are times when projects slip by and remain in waiting list limbo.
This week we are putting forward the idea of allowing our readers to vote for distributions on our waiting list in order to bring promising projects to our attention. Do you think voting projects from the waiting list into our database would be a good way to get quality projects the attention they deserve? Or would a voting process be more likely to promote projects that have a vocal user base rather than quality features to share?
You can see the results of our previous poll on upstream vs downstream distributions here. All previous poll results can be found in our poll archives.
Voting for distros on the waiting list?
|I support voting for distros on the waiting list: ||492 (38%)|
| I prefer the current vetting process: ||398 (31%)|
| Either approach is fine: ||354 (28%)|
| I have an alternative idea to be shared in the comments: ||34 (3%)|
Locating compatible hardware
One of the more frequent questions we get asked is where a person can purchase computers that are known to work with Linux or BSD. There is a demand for laptops and desktop computers that are completely compatible with open source operating systems.
To aid people in their search for compatible computers and hardware components, we have created a page dedicated to providing links to companies which sell computers that are either compatible with Linux or which sell computers with Linux or BSD pre-installed. This page also links to hardware compatibility databases and resources where people can find hardware certified to work with Linux and BSD.
The organizations on our new Hardware Resources page are not affiliated with DistroWatch and we are not endorsing their products. The Hardware Resources page is intended to provide a starting point for people looking to purchase hardware that is compatible with free and open source operating systems.
The new Hardware Resources page can be located through our sitemap.
* * * * *
Distributions added to waiting list
- Debtailor. Debtailor is a distribution based Debian and Ubuntu which provides live images and runs without any network services enabled by default.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 25 April 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)
- Bruce Patterson (podcast)
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 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|
|• Issue 702 (2017-03-06): Fatdog64 Linux, elementary OS bundled with new netbook, Haiku announces new features, security and the size of a distro's development team|
|• Issue 701 (2017-02-27): OBRevenge 2017.02, Mageia 6 delays, NetBSD reproducible builds, questions about swap space, trying to steam video on a Raspberry Pi|
|• Issue 700 (2017-02-20): RaspBSD, Debian replaces Icedove with Thunderbird, Fedora's licensing guidlines, tips for switching shells, finding battery charge, getting IP address and killing processes|
|• Issue 699 (2017-02-13): Clear Linux, GhostBSD network utility ported to FreeBSD, Ubuntu coming to Fairphone, elementary OS crowd funding an app store|
|• Issue 698 (2017-02-06): Solus 2017.01.01, comparing containers with portable applicatins, Tails dropping 32-bit support, Debian Stretch enters freeze|
|• Issue 697 (2017-01-30): Subgraph OS 2016.12.30, running Ubuntu on an Android phone, Arch Linux phasing out 32-bit support, Linux Mint testing updated LMDE media|
|• Issue 696 (2017-01-23): GoboLinux 016, remotely running desktop applications, Solus adopting Flatpak, KDE neon using Calamares, TrueOS tests OpenRC|
|• Issue 695 (2017-01-16): Zorin OS 12, Peppermint team fixes installer bug, Debian refreshes Jessie media, Ubuntu improves low graphics mode, Exciting things coming in 2017|
|• Full list of all issues|
|Random Distribution |
Zopix was a Linux distribution derived from Knoppix. It was a live CD, a ready-to-use Zope working environment consisting of open-source and free software distributed under GPL.