| DistroWatch Weekly
|DistroWatch Weekly, Issue 494, 11 February 2013
Welcome to this year's sixth issue of DistroWatch Weekly! It has been an exciting week for users of open source software with big announcements coming out of the Ubuntu and GNOME projects. In this week's edition of DistroWatch Weekly we will look at the new developments underway in the GNOME community and look at the changes coming to Unity, Ubuntu's primary desktop environment. We also bring you news of Canonical's plans to launch a phone powered by the popular Ubuntu distribution. This week we turn a spotlight on server operating systems. Jesse Smith takes FreeBSD 9.1 for a spin and reports on his experience and how it compares to running Linux distributions on home servers. Plus we take a look at which Linux distributions are preferred for hosting web servers. In the Questions and Answers section we look at the common problem of broken software following an upgrade and share tips on how to deal with this issue. As always we look at the distribution releases of the past week, look forward to new releases to come and share news, reviews and podcasts from Around the Web. We wish you a pleasant week and happy reading!
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (21MB) and MP3 (34MB) formats
|Feature Story (by Jesse Smith)
Bringing home FreeBSD 9.1
At home I have an old machine which, around a decade ago, performed as someone's desktop computer. Abandoned by its former owners, it now sits in my home and gets used as a test bunny whenever I'm feeling experimental. For the past several months the machine has been running Ubuntu Server, partly because Ubuntu is quick to install and, when I break it, it's quick to re-install. In addition Ubuntu's installer was the first of several which was able to run on the hardware. The machine has been holding up well with Ubuntu and I've had no problems setting it up as a web server, ownCloud server, file server and test bed for ZFS-on-Linux technology. Still, I find when my computers work too well for too long I get bored. In order to experience some excitement I started thinking about what other operating system I might put on my test box and settled on FreeBSD.
There are a number of different download options for FreeBSD. The project supports four different architectures (i386, amd64, sparc64, powerpc64) and the i386 build is available in a few different flavours. We can download a CD-sized ISO, a 2.5GB DVD image or an image for USB flash drives. I opted to work with the DVD image. Booting from the downloaded image brings up a text menu asking if we would like to run the FreeBSD installer or make use of the command shell available on the media. Jumping into the installer we are asked to confirm our keyboard map and provide a hostname for our computer. We are then asked which optional components (games, documentation, ports and system source code) we would like to install. The next series of text-based menus deal with partitioning.
The partitioning section is where I hit my first snag. By default FreeBSD uses UFS as its file system, but one of the perks of running a FreeBSD system is having built in support for ZFS and its many advanced features. According to the FreeBSD documentation the installer supports ZFS. Maybe it does, but I couldn't get it to work. When I specified I wanted to set up partitions or slices using ZFS the installer would accept the order, then when I tried to proceed to the next step (formatting the hard drive) an error would appear saying the ZFS partition (or slice) could not be accessed. Following this I would be asked to restart the install process, beginning from the first screen of the installer. After my fourth attempt I finally gave in and accepted UFS as my primary file system.
After partitioning has been completed we are asked to set a root password and configure the system's network card. Here I ran into another problem as the installer wasn't able to make use of DHCP through my network card and I had to manually configure my connection. We are then invited to enable system services, such as secure shell support and network time synchronization. Our next step is to create a user account and fill in all its details, such as the user's shell, group and even the permissions on the user's home directory. Earlier I mentioned there are some optional packages we can install, including games, documentation and source code. I opted to install the documentation package. The installer informed me it was unable to perform the installation of the documentation package, though it was not clear as to why. With that the installation and initial configuration was complete and I was able to reboot the system to begin using FreeBSD.
Booting FreeBSD brings us to a text console where we are presented with a login prompt. My first order of business upon logging in was to check for system updates. At time of writing no updates to FreeBSD 9.1 were available. Looking around a little we find the system comes with a complete collection of UNIX userland tools and documentation in the form of man and info pages. As FreeBSD is currently in the process of switching their build processes from the GNU Compiler Collection to the Clang compiler both compilers are present on the base system. During the installation process I had requested OpenSSH be enabled and I found this service running in the background. The secure shell provided by OpenSSH allowed me to login remotely and I had no problem enabling public key logins. The system is quite clean, less than 30 process run on the default install and the system only uses around 50MB of active memory. Of course a server without services isn't much more than an ineffective space heater so my next task was to install additional software.
One of the more attractive features to find its way into FreeBSD in recent years is pkg-ng, a "next generation" package manager which provides FreeBSD users with modern package handling similar to Debian's APT or Red Hat's YUM. The pkg-ng software works with binary packages which have been built from the FreeBSD ports collection. Trying to run pkg-ng the first time causes the software to bootstrap itself, enabling the default repository. So far, so good. However, performing searches for packages turned up no results. Checking for repository updates showed the local package database was up to date. Having used pkg-ng last year I was a bit puzzled as to the lack of available software packages. Some browsing of the FreeBSD website revealed binary packages for pkg-ng and the traditional FreeBSD package management tools had been taken off-line following a security breach in late 2012. At the time of writing the repository of binary packages has been off-line for approximately two months and there is no estimate as to when the repository may be brought back on-line. This means software must be added to the system and upgraded by compiling software in the FreeBSD ports collection.
There were several pieces of software I wanted to install on my FreeBSD machine. These included a FTP server, the Apache web server, PHP, MySQL and ownCloud. The FTP server, Apache, PHP and MySQL server all built and installed. I found the FTP server would start and operate without any problems, however Apache refused to start. After some failed attempts to get it running the problem turned out to be Apache didn't like my machine's hostname ("xena") and required a fully qualified hostname in order to start. I provided Apache with a complete (though fake) domain name and it worked properly from then on. I also found that by default installing the PHP language does not provide PHP support for the Apache web server. I went back and reconfigured the PHP port and rebuilt it. This provided me with a PHP module which I could add to Apache and my web server was up and running.
The ownCloud software provided its own set of challenges. Getting the software installed from its port was easy, but I soon found ownCloud was installed with file system permissions which would prevent the service from being accessible. Additionally, the ownCloud port provides configuration steps to assist the user in enabling the cloud service on Apache services. The steps provided did not yield a working ownCloud system. Tweaking the ownCloud permissions and adjusting the software's configuration allowed me to access my newest web service. FreeBSD has long had a more hands-on reputation compared to Linux distributions and so I expected a little more manual configuration to be required. This was par for the course. What I did find odd however is that, by default, the PHP port does not supply a module for Apache and requires the user to specifically build this module. Considering how server oriented FreeBSD is I am surprised no one has created a unified Apache-MySQL-PHP (AMP) port for the operating system yet. It would certainly speed up the initial set up process.
One of the benefits of running FreeBSD is the excellent built-in support for the feature-rich file system called ZFS. FreeBSD comes with a modern implementation of ZFS which allows for the storage of massive amount of data, instant recovery from system crashes, instant file system snapshots, mirroring and data deduplication. FreeBSD provides a good deal of clear documentation for dealing with ZFS's many features and it makes setting up new file systems fairly straight forward. While I wasn't able to get ZFS working using the system installer, I was able to add devices and partitions post-install and migrate my users' home directories to ZFS. In the past people have claimed ZFS requires large amounts of memory to work. However, for simple home use I have found ZFS's memory use hardly shows up on the system at all and multiple devices with hundreds of gigabytes of data can be stored without any problems on a system with 512MB of RAM.
In the end, I did get all the services and features I wanted installed and running. The process of getting everything in place on FreeBSD required a good deal more time compared to performing similar setups with Ubuntu or CentOS -- around six hours for installing the operating system and compiling packages on FreeBSD next to an hour to install and configure everything with Ubuntu Server. Most of the extra time was due to compiling third-party software rather than having convenient binary packages. Another delay came from trouble-shooting Apache and ownCloud errors which I did not experience upon installing the same services on Ubuntu. Still, the end results achieved with both operating systems are quite similar. Aside from the time required to get all the pieces in place, the main practical difference is the organization of those pieces once they have been added to the system. Where Linux distributions tend to intermix the operating system, applications and services, FreeBSD makes a clear separation.
The operating system and the software we install on FreeBSD are divided, making for a clean working environment. I found FreeBSD used slightly less memory and ran fewer processes than my old Ubuntu Server install, though the difference is quite small. Setting up a FreeBSD server takes a bigger investment and makes for a more educational experience compared with Ubuntu which provided more of a quick install-and-go experience. Both have proven to be stable and both come with several years of support. FreeBSD is a powerful and useful platform, though the lack of binary packages does give me pause as it means (at least for the time being) future security updates will require more work and each update will require additional compile time. It is my hope the FreeBSD team is able to restore the pkg-ng repository to its former glory as its binary packages are a big time and energy saver for the project's users.
|Miscellaneous News (by Jesse Smith and Ladislav Bodnar)
Web server statistics, Ubuntu enhanced search, Anaconda, PC-BSD updates, GNOME developments
The number of users each Linux distribution has is a famously difficult statistic to nail down, however that fact doesn't prevent people from trying. The website W3Techs has put together some numbers and graphs in an attempt to judge the market share of popular Linux distributions on web servers. The graphs show the current leader in web server installs is the community-run Debian GNU/Linux distribution. Another community project, CentOS, takes second place while two commercial distributions, Ubuntu and Red Hat Enterprise Linux (RHEL), take third and forth places, respectively. It is perhaps interesting to note that, according to W3Tech's statistics, both Debian and Ubuntu (two closely related projects) are increasing in market share while Red Hat and CentOS (two other closely related projects) have dropped in popularity over the past twelve months.
* * * * *
In recent months the Ubuntu developers have placed an increasing emphasis on search with the Unity Dash being the focal point of their efforts. Going forward the Dash is going to receive more attention which will not only provide users with more search lenses (now called "master scopes"), but the search system will gather feedback about which scopes return desired results and learn to tailor its results to the user's preferences. Ubuntu Community member Alan Bell writes, "This means that your client might have 100 or more locally installed search scopes, but the server will advise it which are likely to give good results. Now for the scary bit, once you have looked at the results and perhaps clicked on something then your client pings the server again to tell it which scope produced the most relevant result. This means that the server can learn from this feedback about which scopes produce high quality results for that keyword, and perhaps rank that one a bit higher in future recommendations lists." The new, smart master scopes feature is expected to be included in the upcoming release of Ubuntu 13.04.
The Ubuntu community also learned this past week that the popular Linux distribution will be coming to mobile devices in the final months of 2013. Michael Hickins of The Wall Street Journal reports Ubuntu may begin shipping on smart phones in October. "Smart phones running the open source Ubuntu operating system will be available to customers beginning in October 2013, according to Mark Shuttleworth, founder and CEO of Canonical Ltd. Canonical provides services for corporate customers using Ubuntu open source software. Application developers will have access to the smart phone operating system, which is optimized for the Galaxy Nexus handset manufactured by Samsung Electronics Co., in late February."
* * * * *
Fedora's new system installer, the revamped Anaconda, has come under heavy criticism from many quarters, including reviewers and even some well-known Linux developers, many of whom questioned the reason behind the radical redesign of a well-established tool that has been around for years. But as explained by Will Woods, one of the developers of the new Anaconda, the rewrite of the ageing installer was long overdue: "Back in August 2009 we were trying to redesign the storage UI to handle modern storage needs. This turned out to require rewriting a lot of the storage backend code (again) because the existing Anaconda code was basically all duct tape and bubble gum, creaking under the strain of modern demands. You might think I’m exaggerating, but keep in mind that Anaconda was originally written in 1999, for Red Hat Linux 6.1. It was designed to run off a 1.44 MB floppy disk, using the still-newish Linux 2.2.x kernel. In 2009 it still had its own custom initrd init system called 'loader' written entirely in C. So Anaconda had its own copy of stuff like mount, losetup and mknod, but no Bash before the GUI started. Good luck trying to debug anything!"
* * * * *
Dru Lavigne, a well-known FreeBSD and PC-BSD developer, has written an interesting post in which she quotes Kris Moore, the founder of PC-BSD, voicing his dissatisfaction with the PC-BSD release process. To take the project into the future, he believes, it needs to switch to a rolling-release style of OS updates: "First of all, I want to let you know, that I’ve personally not been satisfied with the frequency of PC-BSD releases and updates. With us tracking the upstream FreeBSD releases, it has really tied our hands getting new releases out to the public. The past couple of releases had a delay of almost a year between them, which is WAY too long in my opinion. To further compound the problem, our build system wasn’t designed to do frequent updates of packages and our utilities, which made getting updates out to the community a long and tedious process. This is all going to change. What we are looking at going to now is more of a “Rolling-Release” model, first for our utilities and system packages, and eventually for the FreeBSD base itself." Exciting times ahead for those who prefer to run FreeBSD on their desktops.
* * * * *
In other GNOME-related news, The H reports GNOME developers will soon begin work on a new distribution independent sandbox model for applications. This should allow third-party applications to be bundled with all of their dependencies in a single file and installed on the user's computer just by clicking on the application archive. The application would be installed in an isolated area of the file system for added security. "GNOME developer Alexander Larsson writes that the entire concept is to go hand in hand with efforts to improve app isolation. For example, the developers plan to use techniques that are also used for containers to mount each app image in a separate area. Only the programming interfaces that are listed in the manifest will be available in these areas. The apps are not planned to have direct access to a user's home directory."
* * * * *
Over the years more and more businesses have turned to open source software to help them run their infrastructure. The low cost, the ability to audit the source code and the extendability provided by open source products are great features for enterprises. However, giving away one's source code raises certain challenges when it comes to turning a profit. Last week Katherne Noyes wrote a blog post in which she talks with the CTO, CEO and a Vice President of the successful ownCloud project. They discuss the problems ownCloud tries to solve and why they feel it has been successful as a business. Frank Karlitschek says ownCloud got its start when, "`Three years ago I had an opportunity to keynote at a KDE event in San Diego, and I thought, let's look a bit into the future,' he recalled. `I could already see the trend of things moving to Dropbox, which was pretty much the only solution for cloud at the time. I thought this was interesting, but I also saw problems.' Specifically, Karlitschek identified privacy and cost issues for home users, and was inspired to launch an open source project to help solve those problems."
|Questions and Answers (by Jesse Smith)
Broken packages and possible solutions
Recently I have been receiving e-mails with a common theme from several Linux users. The common characteristics of these e-mails are that the person writing has been using a piece of software (perhaps a network service, perhaps a game) and, following an update, the software has stopped working. In every case either no error message appears on the user's screen or the error that appears on the user's terminal is cryptic and may indicate a segmentation fault or perhaps a missing library function. A Google search of the error message doesn't reveal any obvious causes or solutions. The final thing each of these e-mails have in common is that the person writing to me is running Arch Linux. Having had the chance to help several people through this situation I would like to share the solutions we have found that fixed the problem.
The most common cause of a program or service no longer working properly after an upgrade appears to be out of sync repositories. It takes time for packages to get replicated across all repositories and some repositories fall behind in their updates. This puts the repository out of sync with the rest of the Arch community. When this happens check the package manager's mirror list and try pulling from a mirror in a different region. There are plenty of Arch repository mirrors out there from which to choose. Once you have updated your mirror list, try updating your malfunctioning package and its dependencies.
In some cases it seems that simply removing and re-installing the program which is malfunctioning can correct the issue. I suspect this also means the local system is out of sync with the main Arch repositories and the user simply needs to let time pass before attempting to update their system again.
It may be that you have uncovered a bug. Sometimes packages are broken when they are upgraded. Be sure to check the Arch Linux forums to see if anyone has experienced the problem or has found a solution. If no one else has reported the problem, be sure to file a bug report so the developers can look into the matter.
Should you be in a hurry for a fix and no one is coming to your aid, consider building the malfunctioning package from its source code. Most open source projects include details on their website or in their source code archives on how to compile their software. This can be of great help to people looking to fix their own problems. Building a package from its source and linking it to the libraries on your own system may correct the problem or at least give you a better place from which to trouble-shoot the problem.
I hope the above suggestions will prove useful, both to Arch users and to anyone else who has run into problems following an upgrade.
|Released Last Week
Parsix GNU/Linux 4.0r2
Alan Baghumian has announced the availability of an updated build of Parsix GNU/Linux 4.0, a desktop distribution and live DVD based on Debian's "testing" branch: "To celebrate our 8th anniversary, we decided to release an updated version of Parsix GNU/Linux 4.0 code name 'Gloria'. This version ships with a brand-new kernel based on Linux 3.2.37 and merges Debian testing updates as of January 30, 2013. Parsix 'Gloria' is the project's first release with the GNOME 3 series and it ships with LibreOffice productivity suit by default. Gloria has a brand-new software package manager. Highlights: GNOME 3.4.2, X.Org 7.7, GRUB 2, GNU Iceweasel 18.0.1, GParted 0.12.1, Empathy 18.104.22.168, LibreOffice 3.5.4, VirtualBox 4.1.18. The live DVD has been compressed using Squashfs and xz." Read the rest of the release notes where you can find more information and upgrade instructions.
Frugalware Linux 1.8
James Buren has announced the release of Frugalware Linux 1.8, a general-purpose distribution for intermediate and advanced Linux users: "The Frugalware developer team is pleased to announce the immediate availability of Frugalware Linux 1.8, our eighteenth stable release. No new features have been added since 1.8rc2, but 157 changes have been made to fix minor bugs. If you didn't follow the changes during the pre-releases, here are the most important changes since 1.7 in no particular order: updated packages - Linux kernel 3.7.5, X.Org Server 1.13.2, GNOME 3.6, KDE 4.9, LibreOffice 3.6.3, Mozilla Firefox 18.0.1 to name a few major components; video decoding acceleration is now enabled in most multimedia applications; CPU scaling should now work out of the box on i686 and x86_64; Mesa 7.11 drivers revived to support hardware that Mesa upstream dropped support for...." Here is the brief release announcement.
Kai Hendry has announced the release of Webconverger 17.0, a specialist distribution designed for web kiosks - now based on Debian's "testing" branch: "Webconverger 17.0 is exciting for two reasons: new installer allowing you the choice to install to a USB stick and whole base is upgraded from 'Squeeze' to 'Wheezy'. The 'install' term can be misinterpreted as a straight copy of image. Install in Webconverger parlance means you are creating a read/write store. When you follow the USB guide you are: downloading the ISO; 'dd-ing', that is plonking the image upon the USB stick, without partitioning the USB stick (this is tricky); the new installer allows you to partition (tricky bit solved) the USB stick and use it as a read/write store." Read the full release announcement for more information and to see a photo of the installation screen.
Linpus Linux 1.9 "Lite"
Linpus Linux 1.9 "Lite", a desktop Linux distribution featuring a customised GNOME 3 desktop with HTML 5 widgets and support for touch screens, has been released: "Linpus, a leader in the field of open-source software in the consumer space, announced the release of the latest version of their Linux distro, Linpus Lite. Linpus Lite has both full touch-based and mouse and keyboard-style launchers that can be easily swapped between through a menu item on the top bar or a touchpad gesture. Both look and user experience are designed to match whether you want to interact with the device through touch or through your keyboard. In addition, for key applications multi-touch behavior has also been added. Linpus has also worked very hard on web app integration in several ways. Anyone with a Chrome webstore account can login and automatically sync their Chrome applications to the launcher." See the press release for more information.
Linpus Linux 1.9 "Lite" - a live CD with a customised GNOME 3 desktop
(full image size: 482kB, screen resolution 1280x1024 pixels)
Chakra GNU/Linux 2013.02
Anke Boersma has announced the release of Chakra GNU/Linux 2013.02, the project's brand-new series featuring the KDE 4.10 desktop: "Chakra 2013.02 'Benz' (a code name that will follow the KDE 4.10 series) has been released. KDE 4.10 is about the most polished release KDE has put out to date; one feature that stands out is the fast improvements of Nepomuk. Our tools have gotten a lot of attention too, the live image has switched to using GFXboot - this will give many more options for language and keyboard settings and it adds a few hardware checking tools in a visually pleasing way. Tribe has now a dedicated keyboard page - this will avoid issues with setting the desired keyboard. The 'Dharma' artwork theme is fully updated and integration is set for all parts of the live image, GRUB bootloader, KDM and the installed desktop." See the release announcement for further details and screenshots.
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
|Around the Web
* * * * *
* * * * *
New distributions added to database|
* * * * *
New distributions added to waiting list
- CoreSec Linux. CoreSec Linux is an Ubuntu-based distribution for penetrating security holes online and offline.
- GOVOnix. GOVOnix is a project based on the Xubuntu distribution where the Xfce desktop has been replaced with MATE.
- IprediaOS. IprediaOS is a Fedora-based Linux distribution that provides an anonymous environment. All network traffic is automatically and transparently encrypted and anonymised.
- RhinoLinux. RhinoLinux is an Ubuntu-based desktop-oriented distribution which aims to provide many different desktop environments, including GNOME, KDE, MATE, Unity and Xfce.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 18 February 2013. 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 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|
|• 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|
|• Full list of all issues|
|Random Distribution |
Vyatta software was a complete, ready-to-use, Debian-based distribution that was designed to transform standard x86 hardware into an enterprise-class router / firewall. Vyatta software includes support for commonly used network interfaces, and industry-standard routing protocols and management protocols. Unlike previous open-source routing projects, all these features are configurable via a single command-line interface (CLI) or web-based graphical user interface (GUI). Vyatta software was available as a free Community Edition as well as tiered Software Subscriptions that include maintenance, upgrades and support.