| DistroWatch Weekly
|DistroWatch Weekly, Issue 564, 23 June 2014
Welcome to this year's 25th issue of DistroWatch Weekly! Diversity and open source go hand-in-hand. The developers and users of open source software have a wide combination of needs, jobs and tastes, leading to a software ecosystem as varied as the people involved in its creation. This week we celebrate open source diversity, starting with two reviews of very different projects. We examine Antergos, a cutting edge Linux distribution, and Q4OS, a highly conservative distribution. In our Questions and Answers column this week we talk about setting up live DVDs and USB thumb drives with multiple test distributions, perfect for distro-hoppers. We also saw diversity in the news last week. On the one hand, conservative and stable Debian received long term support for its ageing Squeeze branch. On the other end of the spectrum, the Fedora project is looking at adopting a new package manager and Ubuntu is rolling out testing images for its new Unity 8 desktop environment. Get all the details on these happenings below. As usual, we cover the distribution releases of the past week and look ahead to fun new developments to come. We wish you all a fantastic week and happy reading!
|Feature Story (by Jesse Smith)
Antergos, formally called Cinnarch, is a distribution derived from Arch Linux. In fact, Antergos claims to be compatible with the Arch Linux software repositories. The project, which carries the cute motto "Ready to KISS", supports a range of desktop environments, all of which are available at install time from the project's installation media. The distribution is available in 32-bit and 64-bit x86 builds and comes in just one edition. The download for Antergos is approximately 740 MB in size.
Booting from the Antergos media brings up the GNOME Shell desktop environment. On the desktop we are presented with a window which enables us to launch the distribution's system installer or close the window to experiment with the live environment. Jumping straight into the distribution's graphical system installer we find that the Antergos installer looks a lot like Ubuntu's system installer, though with navigation buttons placed at the top of the window instead of the bottom. We are walked through selecting our preferred language, choosing our country/location and choosing our time zone from a map of the world. Next we are asked to select our keyboard's layout from a list.
The following screen asks us to select our preferred desktop environment. Available desktops include Cinnamon, GNOME, KDE, MATE, Openbox and Xfce. There is also an option to skip installing any desktop environment and use a text console only. Unfortunately users are limited to installing just one desktop environment, we cannot select multiple desktops from the installer. Next we are given the choice of manually partitioning our hard drive or using a guided option. We can give the guided partition creation utility hints, such as asking it to create LVM volumes, use encryption or set aside a separate partition for our /home directory. The next screen asks us to create a user account and then the installer begins to copy its files to our local disk.
Antergos 2014.05.26 - the system installer
(full image size: 269kB, screen resolution 1024x768 pixels)
I attempted to install Antergos five times, using various options and drive layouts. Each time the installer locked up and failed to complete its tasks. Once the installer froze on the screen where we can choose our time zone and the other four times the installer locked up during the final step of the installer. Installation progress always stopped at the same point with the status message, "Updating community database (30%)". While the installer was frozen the rest of the desktop environment continued to work. I found that if I tried to update the distribution's pacman software database I would end up with error messages saying the file antergos.db could not be retrieved from the server mirrors.antergos.com. I suspect this is part of why the system installer consistently locked up. Oddly enough I could ping this remote server. In fact, if I opened a web browser I could visit the mirrors.antergos.com server and manually download the antergos.db file, which raises the question of why the package manager failed to perform the same task.
Sadly, the malfunctioning system installer brought my time with Antergos to a quick conclusion and I decided to spend some time this week looking at other, niche projects. One of these off-the-beaten-track projects was Q4OS.
* * * * *
The Q4OS project is, in a lot of ways, the polar opposite of Antergos. Where Antergos offers cutting-edge software, a modern desktop environment and a rolling-release platform, Q4OS ships with older packages, maintains a slow release cycle and features a classic desktop environment. The Q4OS website describes the distribution as a "desktop operating system designed to offer [a] classic style user interface, simple accessories and to serve stable API for complex third party applications. [The] system is also very useful for virtual cloud environments due to its very low hardware requirements." Q4OS uses the Debian Stable distribution as its base and ships one edition featuring the Trinity desktop environment. The Q4OS distribution is available in 32-bit and 64-bit x86 builds and the download image is about 330 MB in size.
Booting from the Q4OS media brings up a menu asking if we would like to perform a regular install or run a fully automated system installer. I went with the regular installer and was presented with a series of text-based menus. The installer walks us through selecting our preferred language, our location and creating a regular user account. When it comes to partitioning the hard drive we can ask the partition manager to divide the disk for us or we can manually partition the hard drive. The partition manager supports LVM, ext2/3/4, Btrfs, JFS and XFS formats. The system installer copies its files to our hard drive and then we reboot the computer.
The Q4OS distribution boots to a graphical login screen. I tried running Q4OS in a VirtualBox environment and on physical hardware. When we login to our account while the distribution is running inside VirtualBox a window opens and offers to download and set up optimized VirtualBox drivers which will improve our experience. Assuming we agree to download the drivers, an installation wizard opens and shows download and installation progress. When the new VirtualBox module has finished installing the wizard offers to log us out so that the display server can be restarted and we can take advantage of improved screen resolution. The installation and following logout went smoothly and, when I logged in again, my VirtualBox window was resized to match my display's resolution. I was pleasantly surprised by this as I have never seen a Linux distribution offer to optimize a VirtualBox session before. Some distributions include the required modules by default, but most do not and it would be nice if those which do not include VirtualBox support by default followed the example set by Q4OS.
Q4OS 0.5.11 - the Trinity desktop environment
(full image size: 104kB, screen resolution 1280x1024 pixels)
Another notification which popped up the first time I logged in warned me that Q4OS is beta software and may not be entirely stable. However, during my time with Q4OS I did not run into any stability issues. The distribution ran quickly and smoothly. The operating system performed well, with virtually no delay between the time I tried to open a new application or menu and the time when the action was completed. Q4OS runs the Trinity (KDE 3.5) desktop which is light on memory by modern standards, using just 70MB of RAM, and there are no visual effects enabled. The default theme has a Windows 2000 style to it, combined with classic KDE icons. The overall appearance of the desktop looks a touch dated, but not overly so. The interface is entirely functional and I had no trouble navigating or transitioning from a modern desktop environment to Trinity.
The Q4OS distribution ships with a small collection of software. We are given the Konqueror web browser and file manager, there are a few system administrator tools for working with user accounts and desktop settings. Network Manager is available to help us get on-line and the distribution comes with some documentation, including manual pages. There is no multimedia support available by default, but we can find additional packages in the Debian Stable repositories. The GNU Compiler Collection is installed for us and, in the background, we find the Linux kernel, version 3.2.
I did not find any graphical package manager in Q4OS's default installation, but we can use the apt-get command line utility. The apt-get program connects us to the Debian Stable repositories and gives us access to a large collection of software. I found that when I first installed Q4OS the package manager was locked and I had to locate and remove a lock file before I was able to update or install new software packages.
Early on I enjoyed using the Trinity control panel for adjusting the look and feel of the desktop. The Trinity desktop is quite flexible and the configuration tools are easy to navigate. In fact, the entire distribution is a good combination of classic utilities with high performance and stability. The only problem I ran into while playing with Q4OS was that, once I installed some Xfce applications, several of the Trinity configuration modules no longer worked, reporting they could not find the Xfce panel software. Otherwise, my brief time with Q4OS was a smooth and generally pleasant experience.
I was not sure how Trinity (KDE 3.5) would hold up after so long. I had not used a member of the KDE 3.5 family since 2008 and I had concerns about how I would slip back into an old mode of working after six years of KDE 4, Unity and other modern interfaces. I am happy to report the Trinity desktop has held up well. While it may look slightly dated, the Trinity interface behaves much the same way Xfce, LXQt or KDE 4 (without widgets) behave. All in all, my impression of Q4OS is that is reminds me of running plain Debian with the Xfce or LXDE desktop -- lightweight, fast and stable. There are not many applications in the default installation, but additional software can be installed at a later time, making Q4OS a small and stable platform.
* * * * *
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 and Ladislav Bodnar)
Debian "Squeeze" enters long term support status, Ubuntu tests Unity 8 desktop builds, Fedora considers new package manager, CentOS battles with version numbers
Starting June 16, Debian 6.0 "Squeeze" (also referred to as "oldstable") entered into long-term support status. Normally, at this point in Debian Squeeze's life cycle the distribution would no longer be receiving support, but a new team, operating separately from the official Debian security team, has taken over support for the ageing Debian release: "Official security support for Debian GNU/Linux 6.0 (code name "Squeeze") has ended on 31 May 2014. However long term support for the distribution is going to be extended until February 2016, i.e. five years after the initial release. Squeeze-LTS will not be handled by the Debian security team, but by a separate group of volunteers and companies interested in making it a success (with some overlap in people involved)." Companies or individuals benefiting from Squeeze's extended support are encouraged to participate in the Debian LTS program.
Speaking about Debian, last week's news about the distribution's switch back to the good-old glibc (from the abandoned eglibc) has caught the eye of the development community. Aurelien Jarno explains: "Five years ago Debian and most derivatives switched from the standard GNU C Library (glibc) to the Embedded glibc (eglibc). Debian is now about to take the reverse way, switching back to glibc as eglibc is now a dead project, the last release being the 2.19 one. At the time of writing the glibc package has been uploaded to experimental and sits in the NEW queue. The eglibc package is dead for a good reason: the glibc development has changed a lot in the recent years, due to two major events: Ulrich Drepper leaving Red Hat and the glibc development, and the glibc steering committee self-dissolving. This has resulted in a much more friendly development based on team work with good cooperation. The development is now based on peer review, which results in less buggy code (humans do make mistakes). It has also resulted in things that were clearly impossible before, like using the same repository for all architectures, and even getting rid of the ports/ directory."
* * * * *
Following the release of Ubuntu 14.04 the distribution's development team has begun work on a branch of Ubuntu which will feature Mir and the Unity 8 desktop environment. To enabled developers and users to test the new environment the Ubuntu team has started publishing daily snapshots of Ubuntu with the Unity 8 desktop: "The goal is to ramp up the quality of the Unity 8 desktop, without destabilizing our current environment. For that we are going to keep a Unity 7 image and add a new one for Unity 8 on the desktop, that new ISO should become the default one by 16.04." People wishing to try out the latest Mir and Unity 8 environment can download test images from the Ubuntu mirrors.
* * * * *
The DNF package manager is a fork of the YUM, the default package manager in distributions such as Fedora and CentOS. The DNF project has been progressing over the past few years and discussion is currently underway on the Fedora mailing lists as to whether DNF should replace YUM in Fedora 22: "DNF was forked from YUM in January 2012 and available for experimenting in Fedora since release 18. The project is now fully capable of replacing YUM in new Fedora installations. We want DNF to become the new default packaging tool in Fedora 22." There is also the interesting question of what to call the new package manager when it reaches Fedora. Should the fork be called DNF or YUM? At the moment, it appears likely the DNF fork will be renamed YUM to maintain backward compatibility with earlier Fedora releases and system administration scripts.
Would you like to be able to use Fedora as a development platform for Android applications? If so, read on. Last week, Ryan Lerch published an excellent article on doing just that (and more) - in ten minutes: "Android is one of the most popular mobile operating systems (and it is based on the Linux kernel too.) However, diving into developing apps for Android can appear to be a bit daunting at first. The following how-to runs you through the basics of setting up an Android development environment on your Fedora machine. The basic workflow is to download the Android SDK, use the SDK to generate a quick first “hello world” application, then test out that application with either a physical Android device or the Android emulator." Hands-on instructions for setting up an Android development environment on Fedora are in the linked story.
* * * * *
For most distributions, choosing a version number is probably the least worrying aspect of the project. But sometimes things get in the way, people get strange ideas and conflicts arise - and the unsuspecting victim of these situations is the poor old version number. As LWN discovers in "What's in a (CentOS) version number?", CentOS is the latest victim of this bizarre phenomenon: "Traditionally, CentOS releases have used the same version number as the RHEL release they are based on; CentOS 6.5 is a rebuild of the RHEL 6.5 release, for example. The CentOS developers now want to change to a scheme where the major number matches the RHEL major number, but the minor number is generated from the release date. So, if the CentOS version of RHEL 7.0 were to come out in July 2014, it might have a version number like 7.1407. Derivative releases from CentOS special interest groups (SIGs) would have an additional, SIG-specific tag appended to that number. To the CentOS developers, this change offers a number of advantages. The close tie with RHEL version numbers, it is claimed, can confuse users into believing that a release is supported with security updates when it is not."
|Questions and Answers (by Jesse Smith)
Multiple distributions on a DVD or USB thumb drive
Packing-them-in-tight asks: A general thought to pass around please, hopefully it might provoke someone who knows how to do it ... to do it! Most of the distros come as ISOs, needing to be written to a CD/DVD to become bootable. However, now that DVDs are so prevalent, cheap and readable on almost any hardware, surely a better idea is to provide distros in a form which would let them be written to a folder structure of some sort on a DVD -- to keep them isolated from each other -- and an option added to a general boot menu to permit the given DVD to boot whichever distro the user selects.
Extending that idea further, USB devices would be an even better choice. I can suggest a very simple way to be able to load a variable number of distros to a given DVD. For example, each ISO goes into a folder simply numbered from say /ISO1 to /ISO99 as necessary and the boot software would search for such folders, provide a list and load and boot the ISO chosen. That way a DVD could be updated with additional distros until there is no room left on the DVD. What do you think?
DistroWatch answers: What you are describing, putting multiple operating systems on a single live DVD/USB, has been done. There are a number of projects which allow users to run a variety of Linux distributions all from one CD/DVD/USB drive. A quick search turned up a few different methods for creating a multi-boot disc.
First, there is the command line utility MultiCD which requires a little Linux command line knowledge to get working, but gives a great deal of flexibility. For people who prefer a point-n-click option, there is YUMI. The YUMI application is cross-platform (working on both Linux and Windows) and provides a nice graphical interface. You might also look at SARDU which provides a graphical interface and walks the user through creating a multi-boot live disc or USB drive. Any of the above utilities will provide a fairly straight forward approach to placing multiple operating systems on one portable medium.
|Released Last Week
Rémi Verschelde has announced the release of Mageia 4.1, an unscheduled maintenance update that fixes a number of security issues and corrects an upstream syslinux bug: "While most of the world is turned towards Brazil to enjoy the World Cup, Mageia has been preparing its own major worldwide event: Mageia 4.1 has been released! If you were not expecting it, you might wonder what this unannounced 4.1 version is. It is a maintenance release for Mageia 4 which contains all security and bug-fix updates that were issued since the release in February 2014. In particular, the Mageia 4 ISO images were affected by an upstream syslinux bug which prevented installation using a burned DVD on some older hardware. Among the updated packages you will find the Linux kernel (version 3.12.21), various drivers for your hardware, and updated software." Here is the full release announcement.
Clemens Toennies has announced the release of Netrunner 14, a Kubuntu-based Linux distribution featuring a customised KDE 4.13 desktop and five years of security support: "The Netrunner team today released Netrunner 14 'Frontier' – 32-bit and 64-bit editions. The release follows Kubuntu's support cycle, giving it a full 5 year support life via the backport repositories. Release notes: long-term support; Firefox instant start (on machines with more than 2 GB of RAM); KDE Dreamdesktop for animated backgrounds; Baloo superseding Nepomuk; single-click activated by default; new default theme; Veromix audio applet; the latest package updates available in the repositories, e.g. KDE 4.13.1, Firefox 30, VLC 2.1.4, Skype 4.3, Muon Discover 2.2 and many more." Read the full release announcement which includes a video demonstrating the animated wallpapers feature.
Netrunner 14 - the default KDE desktop
(full image size: 1,264kB, screen resolution 1280x1024 pixels)
MakuluLinux 6.0 "KDE"
Jacque Raymer has announced the release of MakuluLinux 6.0 "KDE" edition, a Debian-based desktop distribution shipping with the very latest KDE desktop: "The long-awaited update to the KDE edition is now over, Stability, speed and beauty is what drives this edition. Based on KDE 4.13.1 and Linux kernel 3.14.x PAE, now also fully supporting systemd. Complete overhaul of themes in the new edition, far more consistent transparency in borders, panels, widgets, pop-up menus. Background theme now uses the same standard theme the rest of Makulu editions use, therefore you have this beautiful dark charcoal look. Please note that anyone wanting to change the theme need to change it for both user and root. Plenty of widgets, themes, styles and colours have been added to this edition allowing the user to customise the look easily to his own preference and taste with plenty choices at his finger tips." Read the complete release announcement for more details.
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
New distributions added to waiting list|
- n00bix. n00bix is a Debian-based distribution which ships with non-free firmware, systemd and the Enlightenment graphical user interface.
- Zentoo. Zentoo is a source-based distribution derived from Gentoo. Zentoo targets server deployments on 64-bit x86 platforms.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 30 June 2014. To contact the authors please send email to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, suggestions and corrections: news, donations, distribution submissions, comments)
- Bruce Patterson (feedback and suggestions: podcast edition)
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 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|
|• 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|
|• Full list of all issues|
|Random Distribution |
PilotLinux was a thin client live CD. This means that when you boot from a PilotLinux CD your PC has been temporarily transformed into a thin client machine. If a settings file was supplied booting from a PilotLinux CD will automatically connect you to your terminal server. Otherwise the PilotLinux GUI will be displayed and give you the ability to manually enter the server address.