| DistroWatch Weekly
|DistroWatch Weekly, Issue 772, 16 July 2018
Welcome to this year's 29th issue of DistroWatch Weekly!
One of the joys of open source software is the way the developer community finds all sorts of new and unexpected approaches to solving problems. This week we begin with a review of an unusual distribution which combines packages from Arch with patches from Debian and includes free software only. Read on to learn more about the Hyperbola GNU/Linux-libre distribution. In our News section we talk about work being done to get desktop applications running on the UBports mobile operating system along with a look at reports of malware in the Arch User Repository. Plus we share news that OpenBSD will soon be able to auto-join wireless networks, Debian has updated the distribution's install media and Tails is making it easier to work with encrypted volumes. In our Tips and Tricks column we discuss a new utility for managing ZFS boot environments called zedenv. Boot environments are also the topic of our Opinion Poll and we would like to find out how many of our readers use these powerful snapshots of their operating systems. Plus we share the releases of the past week and provide a list of the torrents we are seeding. We wish you all a wonderful week and happy reading!
- Review: Hyperbola GNU/Linux-libre 0.2.4
- News: UBports running desktop applications, Arch reacts to AUR malware, OpenBSD gaining ability to auto-join wireless networks, Debian publishes new install media, Tails makes it easier to work with encrypted volumes
- Tips and tricks: Managing boot environments with zedenv
- Released last week: Scientific Linux 6.10, ArcoLinux 6.9.1
- Torrent corner: Archman, ArcoLinux, AUSTRIMI, Bluestar, Clonezilla, Debian, feren OS, Greenie, Live Raizo, Pardus Topluluk, ReactOS, Scientific, Ultimate Edition
- Opinion poll: Boot environments
- Reader comments
|Feature Story (by Jesse Smith)
Hyperbola GNU/Linux-libre 0.2.4
Hyperbola GNU/Linux-libre is a curious project that takes a number of interesting approaches which set it apart from other distributions. The Hyperbola distribution is based on snapshots of Arch Linux. While Arch Linux is a rolling release distribution, Hyperbola maintains fixed releases taken from Arch snapshots and then, according to the project's website, the Hyperbola developers mix in security updates from Debian. The idea is to create an Arch-like operating system with a fixed base and minor patch updates.
The distribution is dedicated to free software ideals and ships only libre software as defined by the Free Software Foundation. Finally, Hyperbola makes a special edition called Hypertalking which is based on TalkingArch and provides accessibility software for visually impaired users.
I downloaded the distribution's main edition which is available as a 672MB ISO. The distribution media will boot on both 32-bit and 64-bit systems with the option to select which architecture we want from the ISO's boot menu. When the disc boots we are presented with a text console where we are advised we can see documentation for getting on-line using the Lynx web browser by typing "lynx network.html".
The default, text-based interface on the disc is quite minimal, but it's enough to partition our hard drive and set up a local copy of the operating system. I don't think it's intended to do much more than that.
Instead of providing users with a system installer, Hyperbola follows the example of Arch Linux and provides an on-line install guide. The guide walks us through creating disk partitions, mounting them, making sure a network connection is enabled and setting up security keys. It's a bit of manual work, but for the most part new users will be able to copy the command line examples from the manual into their terminal to get a working system.
The guide concludes by getting us to install packages on our hard drive, set up a language locale, install the GRUB boot loader and create a password for the root user. After that, we can reboot the computer to start exploring Hyperbola. The manual steps are not difficult to follow for people familiar with the command line, but will probably deter Linux newcomers from trying the distribution.
Hyperbola starts off as a minimal operating system. The snapshot I was using ran version 4.9 of the Linux-libre kernel, a flavour of Linux that has had non-free components removed. Instead of Arch's default systemd init software, Hyperbola ships with OpenRC as its init implementation. At the moment, Hyperbola ships with the OpenSSL security library, but there are plans to switch to LibreSSL in a future snapshot.
Otherwise the base system features the standard GNU command line tools, manual packages and little more. There is no compiler, by default, no Java, and no desktop environment. Hyperbola very much holds to the idea that we need to build and customize our operating system from the ground up.
We can add new users to the system via the useradd command and we can use pacman to add new software to the distribution. Hyperbola does not have documentation nearly as extensive as Arch's famous wiki, but we can use most of Arch's documentation on Hyperbola. I say "most" because not everything translates over to Hyperbola's environment. Since Arch allows software published under non-free licenses and uses systemd to manage services, its approach varies in small ways from Hyperbola's. This means some steps in setting up services, trouble-shooting issues and getting a desktop environment set up will be different under Hyperbola. Users should be aware they will need to adjust some examples that use systemd to get them working with the OpenRC service manager and work around not having some packages.
Software and package management
Like its parent, Hyperbola uses the pacman command line package manager to install, remove and upgrade software. pacman works quickly and I encountered no problems while using it. Software appears to all be pulled from the distribution's own collection of custom repository mirrors.
Earlier I mentioned Hyperbola uses an unusual combination of Arch software with Debian patches, which is explained on the distribution's FAQ page: "Hyperbola is a long-term support distribution based on Arch GNU/Linux plus stability and security from Debian GNU/Linux. It isn't a rolling release distribution like Arch because Hyperbola is using Arch snapshots for its versions and Parabola blacklist as base to keep it 100% libre. Also Hyperbola is using Debian patches, therefore all packages are being stabilized with improvements through its development."
I'm not certain of the details of this update process. Arch and Debian name some software differently or may use slightly different versions of packages, leaving me to wonder exactly how patches get transferred from Debian into Hyperbola. At the moment I am not entirely clear on how long Hyperbola's "long-term support" cycle lasts. One might guess for as long as Debian Stable is supported, but I was not clear on this from the documentation provided. At the moment, Hyperbola is still a fairly young project so it may take time before users get a clear idea of the length of support cycles and how many versions will be supported at a time.
At first my trial with Hyperbola started out well. The dual-architecture CD was able to start in on my laptop in both Legacy BIOS and UEFI modes. The distribution, once installed, required less than 50MB of RAM with the default configuration and used around 1GB of disk space. The distribution was wonderfully fast, mostly because it runs so little software by default.
The main issues I ran into revolved around hardware support. When trying to run the distribution on my laptop, Hyperbola was unable to use my wireless network card. Given the situation I was in at the time, this basically turned my laptop into a typewriter as a wired connection was not always available, making it difficult to get on-line or install new software.
When running in VirtualBox, Hyperbola started off well, but ran into a snag with displaying a desktop. The distribution does not appear to include VirtualBox modules and this meant I struggled to get a fully functional desktop working in the virtual machine. Given more time I might have managed, but since setting up Hyperbola takes extra steps (compared to other distributions) I was running short on time to work around the driver issues.
My big concern with Hyperbola was the documentation. We can use the Arch wiki for most tasks, but there are enough little things that are different between Arch and Hyperbola (like using systemd versus OpenRC) that I think this project needs its own fork of the documentation. I also ran into an unfortunate oversight early on. When I launched the distribution on my laptop and found my wireless network wasn't detected, I ran "lynx network.html" to see the steps required to get it working. In the document there is a link to show trouble-shooting steps for when networking does not operate as expected. The link doesn't work because it points to an on-line resource. It is little details like this which will hopefully be addressed in future snapshots.
What drew me into trying Hyperbola is the distribution is just such an unusual mixture of design choices. It tries to be a fixed release, but is based on Arch Linux, a rolling release platform. The distribution tries to be convenient for visually impaired users through its Hypertalking edition, but also slows me down by effectively disabling some hardware devices by not including non-free drivers and firmware.
The distribution wants to be stable, free, near the cutting edge, accessible and minimal. It also pulls in ideas and software from at least four other projects. It's quite an odd combination and as a result I'm not entirely sure what use cases Hyperbola is targeting. People who want a libre distro like Trisquel, but prefer pacman for package management? People who love the manual approach of setting up Arch, but with Debian-like security updates? Hyperbola is so weird I can't help but appreciate it, but I'm not sure under what circumstances I would consider it the best tool for the job.
* * * * *
Hardware used in this review
My physical test equipment for this review was a de-branded HP laptop with the following
- Processor: Intel i3 2.5GHz CPU
- Display: Intel integrated video
- Storage: Western Digital 700GB hard drive
- Memory: 6GB of RAM
- Wired network device: Realtek RTL8101E/RTL8102E PCI Express Fast
- Wireless network device: Realtek RTL8188EE Wireless network card
* * * * *
Visitor supplied rating
Hyperbola GNU/Linux-libre has a visitor supplied average rating of: 10/10 from 1 review(s).
Have you used Hyperbola GNU/Linux-libre? You can leave your own review of the project on our ratings page.
|Miscellaneous News (by Jesse Smith)
UBports running desktop applications, Arch reacts to AUR malware, OpenBSD gaining ability to auto-join wireless networks, Debian publishes new install media, Tails makes it easier to work with encrypted volumes
One of the potential benefits to running a GNU/Linux operating system on a mobile device is it opens the door for running desktop applications on the mobile platform, greatly expanding the numbers of apps available on the device. The UBports community (who have continued the development of Ubuntu Touch) may soon be able to run desktop Ubuntu packages on mobile devices. In a Reddit post, one developer comments on the state of running desktop Ubuntu applications in a container on a UBports phone: "Libertine Manager is now in the system settings and makes installing 'desktop' apps easier (creates a container and installs apps inside with APT). Some apps work better than the others, in the video GNOME Calculator doesn't work that great yet, Solitaire seems to work ok and is quite usable on a phone." The video demonstrating installing desktop apps on the phone is included in the Reddit post.
* * * * *
People who run Arch Linux, or one of its many derivatives, received a reminder last week that while the Arch User Repository (AUR) is a convenient way to access a large number of software packages, the packages in that repository can come from anywhere and should not be blindly trusted. Sensors Tech Forum reports: "Linux users of all distributions have received a major warning not to explicitly trust user-run software repositories following the latest incident related to Arch Linux. The project's user-maintained AUR packages (which stands for Arch User Repository) have been found to host malware code in several instances. Fortunately a code analysis was able to discover the modifications in due time - only several days after the dangerous code was placed in the app installation instructions. The security investigation shows that a malicious user with the nick name xeactor modified in June 7 an orphaned package (software without an active maintainer) called acroraed. The changes included a curl script that downloads and runs a script from a remote site. This installs a persistent software that reconfigures systemd in order to start periodically. While it appears that they are not a serious threat to the security of the infected hosts, the scripts can be manipulated at any time to include arbitrary code. Two other packages were modified in the same manner." Most Linux distribution have optional add-on repositories where community members can upload scripts or packages. These third-party items should be audited before being installed.
* * * * *
The OpenBSD operating system is getting a new feature which many people running on other platforms probably take for granted: automatically connecting to wireless networks. Peter Hessler has published code which allows OpenBSD to connect to known wi-fi networks automatically when there is no current network connection. "Introduce 'auto-join' to the wi-fi 802.11 stack. This allows a system to remember which ESSIDs it wants to connect to, any
relevant security configuration, and switch to it when the network we are
currently connected to is no longer available."
* * * * *
The Debian project has published new install media for Debian 9 "Stretch". The new media does not represent a new version of Debian, but does include security fixes that have become available since Debian 9 was originally released. "The Debian project is pleased to announce the fifth update of its stable distribution Debian 9 (codename Stretch). This point release mainly adds corrections for security issues, along with a few adjustments for serious problems. Security advisories have already been published separately and are referenced where available. Please note that the point release does not constitute a new version of Debian 9 but only updates some of the packages included. There is no need to throw away old stretch media. After installation, packages can be upgraded to the current versions using an up-to-date Debian mirror." More information can be found in the project's news post.
* * * * *
The Tails project is working to make accessing encrypted volumes easier. The developers are a testing new features which would make it easier for users to access VeraCrypt volumes from the GNOME desktop. "We worked to integrate VeraCrypt support into the existing GNOME workflow for unlocking encrypted volumes. As a result, most of the features already provided for LUKS volumes are now also provided for VeraCrypt volumes. This includes unlocking volumes via the GNOME Disks application and integration into the places sidebar in GNOME Files. If your file containers have the ".hc" file extension, they will be recognized as VeraCrypt volumes and can be easily unlocked in GNOME Files. Additionally, we created a small application, VeraCrypt Mounter, which makes it easier to unlock VeraCrypt volumes, especially file containers that do not have the ".hc" extension." The project's news page has further details.
* * * * *
These and other news stories can be found on our Headlines page.
|Tips and Tricks (by Jesse Smith)
Managing boot environments with zedenv
Boot environments are handy tools for a system administrator to have. A boot environment is basically a snapshot (or copy) of the operating system which was taken at a point in time when the operating system was (presumably) working properly. Having a snapshot of the operating system stored on the disk means we can make all kinds of changes to the system, safe in the knowledge that we should be able to revert back to the working snapshot at any time. This means we can update the system, delete files, and change working configurations, safe in the knowledge that we will be able to reboot the computer and switch back to a working snapshot if anything goes wrong.
Boot environments are made possible by advanced file systems, such as Btrfs and ZFS. Typically Btrfs is used on Linux systems (like openSUSE) and ZFS is used by platforms such as FreeBSD. While these advanced file systems provide the underlying ability to create a snapshot of our working system, we still need tools to create and manage the snapshots. On FreeBSD-based systems the beadm command line tool is typically used to manage boot environments. On openSUSE the snapper tool is used.
In May a new, cross-platform boot environment manager was launched. The new tool is called zedenv and is still in its early development stage (it is still considered an alpha release at the time of writing). The zedenv command reportedly supports the same functions and has a similar syntax to beadm, but has the advantage of being designed to work across multiple operating systems and should work anywhere where ZFS and Python are available. The zedenv software also supports plugins which should make it possible to use the same code across a range of operating systems with different boot loaders.
Since I have already used beadm to manage ZFS snapshots on FreeBSD, I thought it would be fun to see if this new utility could manage ZFS boot environments on a Linux distro. This posed a bit of a problem though because very few Linux distributions support running from a ZFS root file system. There are possible workarounds to make Linux boot on ZFS, but most distributions do not offer an easy way to do this. Antergos appears to be one of the few exceptions. So I installed Antergos, opting to run the operating system from a ZFS volume.
Antergos makes it fairly easy to set up a ZFS volume, it is one of the check boxes on the installer's partitioning screen. The process of setting up ZFS takes a while though as the installer needs to build ZFS components, this added around twenty minutes to my install process, during which time the installer appeared to be locked up. However, the process did complete and I happily rebooted the computer to start working with Antergos running on ZFS.
There was a hiccup to overcome first. It appears as though the Antergos installer does not properly export (a special form of unmounting) the ZFS file system after it is set up. This meant my new ZFS root file system (called "mydata") could not be accessed, or "imported", when I first tried to boot my copy of Antergos. Getting a rescue prompt and running the following command worked around the issue:
zpool import -f mydata
From there, I made sure the git source control program was installed so I would be able to set up zedenv.
sudo pacman -Sy git
Then I followed the step-by-step instructions in the zedenv documentation to install the utility.
git clone https://github.com/johnramsden/pyzfscmds
At this point the installation appeared to have succeeded and I thought I should be able to create, list and activate boot environments by running the zedenv command. However, I soon found I was unable to create snapshots using zedenv. I could manually create snapshots using the lower level zfs command, but not new boot environments.
git clone https://github.com/johnramsden/zedenv
sudo python setup.py install
cd ../zedenv pyzfscmds
sudo python setup.py install
With a little trouble-shooting it turned out the problem was zedenv expects ZFS datasets to be created when the file system is set up. FreeBSD does this automatically, but Antergos does not. The zedenv author pointed out there are ways to work around this problem. However, given the nature of changing the ZFS datasets and boot settings, the user will probably want to create backups of their data before attempting the workaround. Long-term, I am hoping the Antergos team will be able to bring their ZFS setup more in line with that of other operating systems.
* * * * *
Speaking of other systems, I also tried zedenv on FreeBSD to see how the utility would compare to the popular beadm boot environment manager. FreeBSD is relatively quick to set up and also makes it possible to just check a box to automate placing the root file system on a ZFS volume.
Once FreeBSD's installation is complete we will need to install three packages to work with zedenv. We will need to install Python 3.6, the git source control tool and the Python setuptools package. These can be added to FreeBSD by running:
pkg install python36 git py36-setuptools
Then I ran the same git and Python commands as I did above to install zedenv on Antergos. At first zedenv failed to run, reporting a series of locale errors. I was able to quiet these errors and get zedenv to run without crashing by setting the LANG shell variable:
setenv LANG en_US.UTF-8
With these steps completed, I was able to create boot environments, list them, and activate them so the system would automatically boot into the one I wanted. The zedenv command also makes it possible to mount an existing environment to edit it. Let's look at an example of the command in use. Here we create a new environment snapshot, called "safe":
zedenv create safe
We can confirm the snapshot was created by listing all our snapshots:
There should be two snapshots listed, with one called "default" which is currently active. The other is the new one we created, called "safe". Now, suppose we did something foolish, like delete a bunch of programs we will need later. For example, suppose I deleted every program starting with the letter "d" in my /bin directory. We can then try to rescue the system by switching from our active (default) file system, to our good snapshot (safe).
zedenv activate safe
When the system reboots, the programs in /bin I recklessly deleted will have been restored because the "safe" snapshot was created before I removed the files. If I want to, I can then try to fix the default boot environment, where I deleted the programs. I can do this by mounting the default boot environment and copying the missing programs into it. This can be done as follows:
zedenv mount default /mnt
With the default snapshot repaired, I can activate it and boot into it again.
cp /bin/d* /mnt/bin/
zedenv umount default
zedenv activate default
Experienced FreeBSD users will note zedenv has a syntax and output virtually identical to beadm. The main differences are zedenv is designed to (hopefully) work the same on other platforms and it can be extended using plugins. Though this extra flexibility does come at the cost of having a dependency on Python.
Right now zedenv works. It does not yet hold an advantage over beadm on FreeBSD, but its goal of cross-platform use certainly sounds promising. I think the only thing holding back zedenv from being a big hit with Linux users is most distributions still have not embraced advanced file systems like ZFS and Btrfs. This will likely change over time, but right now most Linux distributions are still using more traditional file systems like XFS and ext4. It may take a while before boot environments catch on, outside of the openSUSE community.
* * * * *
Additional tips can be found in our Tips and Tricks archive.
|Released Last Week
Scientific Linux 6.10
Pat Riehecky has announced the availability of Scientific Linux 6.10, the final build of the Red Hat-based distribution's legacy branch, supported until November 2020: "Scientific Linux 6.10 i386/x86_64. According to the upstream lifecycle guide, 6.10 is expected to be the final release of EL6, with only important security errata or critical bug fixes going forward. Please run yum clean expire-cache. Major Differences from SL 6.9: sl-release - updated to use the 6.10 repositories; OpenAFS - updated to 18.104.22.168. Changed compared to Enterprise 6: httpd - changed the default index.html to remove upstream's branding; Plymouth - removed the red colors for text mode; redhat-logos - changed all trademarked icons and pictures from upstream, changed styles of items such as background, GDM and KDM to change the tradedress style; Anaconda - add the Scientific Linux install classes, DVD installs do not ask for the network unless needed; redhat-rpm-config - changed to recognize Scientific Linux as an Enterprise Linux; xorg-x11-server - changed to remove TUV's support URL...." See the release announcement and release notes for further information.
ArcoLinux (formerly known as ArchMerge), is an Arch-based project developing several ready-to-use distributions that feature a number of popular desktop environments. ArcoLinux 6.9.1 was pre-announced earlier this week, but the main Xfce edition was only made available yesterday. From the release announcement: "We decided to trim down our ISO images and remove elements we either don't use or which might be considered a security liability. You can install them if you want them after the installation of the ISO image. Our goal is to stay around 2 gigabytes for the ArcoLinux ISO image. Improvements: new logo has been included in the logos of the conkies; font display has been improved and resized to 11; added VMware configuration file to include 1920x1080 resolution; Neofetch has been upgraded from v4 to v5, we follow the official configuration and change it to our own ArcoLinux configuration; 000- script to use all cores now also includes 6 cores; new alias vbm to mount the Public folder when on VirtualBox; old alias 'update' is now 'sudo pacman -Syyu'...."
ArcoLinux 6.9.1 -- The default ArcoLinux desktop
(full image size: 1.5MB, resolution: 1280x1024 pixels)
* * * * *
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: 940
- Total data uploaded: 20.6TB
|Upcoming Releases and Announcements
Summary of expected upcoming releases
This week, in our Tips and Tricks column we discussed how to use a tool called zedenv to manage ZFS boot environments. Some operating systems, such as openSUSE and FreeBSD ship with built-in tools for managing and running the operating system from boot environments - file system snapshots that let us access past states of the operating system.
We would like to know how many of our readers currently use boot environments. And, if you do, which file system are you using?
You can see the results of our previous poll on how people are reacting to CPU security bugs in last week's edition. All previous poll results can be found in our poll archives.
|I am using boot environments with Btrfs: ||121 (9%)|
| I am using boot environments with ZFS: ||58 (5%)|
| I am using boot environments with another file system: ||173 (13%)|
| I am not using boot environments: ||935 (73%)|
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 23 July 2018. Past articles and reviews can be found through our Article Search page. To contact the authors please send e-mail to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews/submissions, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, donations, comments)
- Bruce Patterson (podcast)
|Linux Foundation Training
|• 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|
|• Issue 787 (2018-10-29): Lubuntu 18.10, limiting application access to specific users, Haiku hardware compatibility list, IBM purchasing Red Hat|
|• Issue 786 (2018-10-22): elementary OS 5.0, why init keeps running, DragonFly BSD enables virtual machine memory resizing, KDE neon plans to drop older base|
|• Issue 785 (2018-10-15): Reborn OS 2018.09, Nitrux 1.0.15, swapping hard drives between computers, feren OS tries KDE spin, power savings coming to Linux|
|• Issue 784 (2018-10-08): Hamara 2.1, improving manual pages, UBports gets VoIP app, Fedora testing power saving feature|
|• Issue 783 (2018-10-01): Quirky 8.6, setting up dual booting with Ubuntu and FreeBSD, Lubuntu switching to LXQt, Mint works on performance improvements|
|• Issue 782 (2018-09-24): Bodhi Linux 5.0.0, Elive 3.0.0, Solus publishes ISO refresh, UBports invites feedback, Linux Torvalds plans temporary vacation|
|• Issue 781 (2018-09-17): Linux Mint 3 "Debian Edition", file systems for SSDs, MX makes installing Flatpaks easier, Arch team answers questions, Mageia reaches EOL|
|• Issue 780 (2018-09-10): Netrunner 2018.08 Rolling, Fedora improves language support, how to customize Kali Linux, finding the right video drivers|
|• Issue 779 (2018-09-03): Redcore 1806, keeping ISO downloads safe from tampering, Lubuntu makes Calamares more flexible, Ubuntu improves GNOME performance|
|• Issue 778 (2018-08-27): GuixSD 0.15.0, ReactOS 0.4.9, Steam supports Windows games on Linux, Haiku plans for beta, merging disk partitions|
|• Issue 777 (2018-08-20): YunoHost 22.214.171.124, limiting process resource usage, converting file systems on Fedora, Debian turns 25, Lubuntu migrating to Wayland|
|• Issue 776 (2018-08-13): NomadBSD 1.1, Maximum storage limits on Linux, openSUSE extends life for 42.3, updates to the Librem 5 phone interface|
|• Issue 775 (2018-08-06): Secure-K OS 18.5, Linux is about choice, Korora tests community spin, elementary OS hires developer, ReactOS boots on Btrfs|
|• Issue 774 (2018-07-30): Ubuntu MATE & Ubuntu Budgie 18.04, upgrading software from source, Lubuntu shifts focus, NetBSD changes support policy|
|• Issue 773 (2018-07-23): Peppermint OS 9, types of security used by different projects, Mint reacts to bugs in core packages, Slackware turns 25|
|• Issue 772 (2018-07-16): Hyperbola GNU/Linux-libre 0.2.4, UBports running desktop applications, OpenBSD auto-joins wi-fi networks, boot environments and zedenv|
|• Issue 771 (2018-07-09): Linux Lite 4.0, checking CPUs for bugs, configuring GRUB, Mint upgrade instructions, SUSE acquired by EQT|
|• Issue 770 (2018-07-02): Linux Mint 19, Solus polishes desktop experience, MintBox Mini 2, changes to Fedora's installer|
|• Issue 769 (2018-06-25): BunsenLabs Helium, counting Ubuntu users, UBports upgrading to 16.04, Fedora CoreOS, FreeBSD turns 25|
|• Issue 768 (2018-06-18): Devuan 2.0.0, using pkgsrc to manage software, the NOVA filesystem, OpenBSD handles successful cron output|
|• Issue 767 (2018-06-11): Android-x86 7.1-r1, transferring files over OpenSSH with pipes, LFS with Debian package management, Haiku ports LibreOffice|
|• Issue 766 (2018-06-04): openSUSE 15, overview of file system links, Manjaro updates Pamac, ReactOS builds itself, Bodhi closes forums|
|• Issue 765 (2018-05-28): Pop!_OS 18.04, gathering system information, Haiku unifying ARM builds, Solus resumes control of Budgie|
|• Issue 764 (2018-05-21): DragonFly BSD 5.2.0, Tails works on persistent packages, Ubuntu plans new features, finding services affected by an update|
|• Issue 763 (2018-05-14): Fedora 28, Debian compatibility coming to Chrome OS, malware found in some Snaps, Debian's many flavours|
|• Issue 762 (2018-05-07): TrueOS 18.03, live upgrading Raspbian, Mint plans future releases, HardenedBSD to switch back to OpenSSL|
|• Issue 761 (2018-04-30): Ubuntu 18.04, accessing ZFS snapshots, UBports to run on Librem 5 phones, Slackware makes PulseAudio optional|
|• Issue 760 (2018-04-23): Chakra 2017.10, using systemd to hide files, Netrunner's ARM edition, Debian 10 roadmap, Microsoft develops Linux-based OS|
|• Issue 759 (2018-04-16): Neptune 5.0, building containers with Red Hat, antiX introduces Sid edition, fixing filenames on the command line|
|• Issue 758 (2018-04-09): Sortix 1.0, openSUSE's Transactional Updates, Fedora phasing out Python 2, locating portable packages|
|• Issue 757 (2018-04-02): Gatter Linux 0.8, the UNIX and Linux System Administration Handbook, Red Hat turns 25, super long term support kernels|
|• Issue 756 (2018-03-26): NuTyX 10.0, Neptune supplies Debian users with Plasma 5.12, SolydXK on a Raspberry Pi, SysV init development|
|• Issue 755 (2018-03-19): Learning with ArchMerge and Linux Academy, Librem 5 runs Plasma Mobile, Cinnamon gets performance boost|
|• Issue 754 (2018-03-12): Reviewing Sabayon and Antergos, the growing Linux kernel, BSDs getting CPU bug fixes, Manjaro builds for ARM devices|
|• Issue 753 (2018-03-05): Enso OS 0.2, KDE Plasma 5.12 features, MX Linux prepares new features, interview with MidnightBSD's founder|
|• Issue 752 (2018-02-26): OviOS 2.31, performing off-line upgrades, elementary OS's new installer, UBports gets test devices, Redcore team improves security|
|• Issue 751 (2018-02-19): DietPi 6.1, testing KDE's Plasma Mobile, Nitrux packages AppImage in default install, Solus experiments with Wayland|
|• Issue 750 (2018-02-12): Solus 3, getting Deb packages upstream to Debian, NetBSD security update, elementary OS explores AppCentre changes|
|• Full list of all issues|
|Random Distribution |
Knopperdisk was a Linux distribution designed for a USB pen drive. It was based on Gentoo Linux and contains various programs and utilities, such as network-related tools.