| DistroWatch Weekly
|DistroWatch Weekly, Issue 699, 13 February 2017
Welcome to this year's 7th issue of DistroWatch Weekly!
Open source is virtually everywhere these days. Open source operating systems power many of the world's servers, run many of our media players and run on most of our smart phones. This week we explore several niche projects and distributions, starting with the OpenELEC and Clear Linux projects. OpenELEC is a distribution dedicated to running the Kodi media software on a variety of devices and Clear Linux is a fast, minimal server operating system. We also talk about Ubuntu's mobile operating system running on the modifiable Fairphone, GhostBSD's network configuration utility being ported to FreeBSD and the elementary OS team working on a pay-what-you-want app store. Plus we talk about the benefits and drawbacks to different types of file compression in our Tips and Tricks column and ask people about their preferred archive formats in our Opinion Poll. We are happy to provide a list of last week's releases and share the torrents we are seeding. Plus we have a new distribution, SLG OS, on our waiting list. We wish you all a terrific week and happy reading!
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (43MB) and MP3 (28MB) formats.
|Feature Story (by Jesse Smith)
OpenELEC is a Linux-based distribution designed to act as a media hub and, in particular, to run the Kodi media software. (Kodi was previously named XBMC.) The Kodi software essentially turns the computer into a dedicated media centre which can either play media directly or through an attached television. The OpenELEC distribution provides a range of builds for x86-powered computers, Raspberry Pi and WeTek devices, along with a few other platforms.
The installation images we download from OpenELEC are compressed disk images which can be written to USB thumb drives or SD cards. There do not appear to be any ISO images which would be suitable for writing to a CD or DVD.
Since I had previously experimented with OpenELEC on my Raspberry Pi computer which features an ARM processor, I decided to shift focus and run OpenELEC 7.0.0 on a laptop computer, running on a 64-bit x86 processor. I downloaded the 221MB compressed disk image which, when unpacked, expanded to 548MB. I then copied this image file to a USB thumb drive and used it to boot my laptop.
Booting from the OpenELEC media brought up a series of text menus which asked if I would like to install a fresh copy of the distribution or upgrade an existing installation. Selecting the fresh install option brought up a menu asking me to select which hard drive would host my new copy of OpenELEC. I selected my hard drive and a warning appeared letting me know any data on the disk would be lost when OpenELEC was installed.
I opted to proceed and, a minute later, the installer announced it was finished. From there I removed my thumb drive and rebooted the computer. At this point I ran into a wall as OpenELEC failed to boot. I was a little disappointed as my past experimented with OpenELEC 5.0.8 had gone well.
OpenELEC's latest version looks enticing and I've had good luck with the distribution before, but this time around the system did not play well with my laptop so I moved on to a new project I had not tried before.
* * * * *
I next turned my attention to a distribution which has only recently been added to the DistroWatch database: Clear Linux. The Clear Linux distribution is unusual in a few ways. For one, the project is not designed to be a full featured or general purpose operating system; Clear Linux focuses on performance more than features. The distribution is fairly minimal and is designed with cloud computing in mind, though it may also be used in other areas, particularly on servers. The project's website states:
The Clear Linux Project for Intel Architecture is a distribution built for various cloud use cases. We want to showcase the best of Intel Architecture technology and performance, from low-level kernel features to complex applications that span across the entire OS stack. We're putting emphasis on power and performance optimizations throughout the operating system as a whole... Our aim was not to make yet another general-purpose Linux distribution; sometimes lean-and-fast is better than big-and-universal.
Another aspect of Clear Linux which sets it apart is the distribution does not handle software the same way most other Linux distributions do. Instead of upgrading thousands of individual packages, the Clear Linux operating system gets upgraded as a whole. We do not upgrade the desktop or our text editor individually, with Clear Linux we upgrade the entire operating system from one version to the next. This makes Clear Linux a sort of unified rolling release operating system. We can add or remove software, but these components (called "bundles" rather than "packages") encapsulate a piece of software and its dependencies. Again, the project's website explains:
We do not deploy software through packages as many distributions do. Instead, we provide "bundles" that each contain a set of functionality for the system administrator -- functionality that is enabled by composing all the required upstream open source projects into one logical unit: a bundle.... There is another notable difference between package-based distributions and the Clear Linux OS for Intel Architecture. On a package-based OS, a system administrator can update each individual package or piece of software to a newer (or older!) version. In the Clear Linux OS for Intel Architecture, an update translates to an entirely new OS version, containing one or many updates; it is not possible to update a piece of the system while remaining on the same version of Clear Linux.
Clear Linux is available in several builds for various virtual environments, including KVM, Azure and Hyper-V. However, the build I wanted to try on my laptop was the "Live" edition which can be run from a USB thumb drive. I feel it worth mentioning the Live edition collects and sends telemetry data back to the project's developers.
The Live edition of Clear Linux was a 211MB download which gave me a compressed image file. Unpacking the downloaded file resulted in a 5,185MB (approximately 5GB) image file which I could then transfer to a USB thumb drive. I plugged the drive into my laptop and attempted to boot Clear Linux. I found the distribution failed to boot when my laptop was run in legacy BIOS mode, but Clear Linux booted without issue when running in UEFI mode.
Clear Linux's Live edition boots very quickly, taking just a few seconds to bring us to a text console with a login prompt. From here we can sign into the root account without a password. The system insists on getting us to create a password for the root account and we cannot complete logging in until a suitable password is provided. This caused me a little frustration as Clear Linux insisted on a long password that was not based on a dictionary word, it had to be complex and not based on any recognizable pattern. It took me more than a few tries to come up with something the distribution would accept.
Once we get signed in we find ourselves in a very minimal environment. Clear Linux basically just runs a few systemd background services and the login terminal. There are only about a dozen processes running in total, using about 51MB of memory. The distribution features the GNU command line utilities, the OpenSSH secure shell service and Python. I intentionally downloaded a version of Clear Linux which was a few versions out of date to test the upgrade functionality. Version 12100 of the operating system used systemd 231 and version 4.8.12 of the Linux kernel. There are no manual pages or compiler and there is no graphical environment. The distribution takes up about 914MB of disk space.
At first, the root account is the only user on the system. There are not even any other accounts for background services as is common on other distributions. We can add other users to the system using the useradd command line program.
When running on my laptop, I noticed Clear Linux did not recognize my wireless network card, but I was able to plug into a wired connection and use the Ethernet port. Clear Linux automatically sets up a wired network connection and uses Google's DNS servers to resolve hostnames.
Since Clear Linux starts us off with a minimal environment, we will likely want to install new software (bundles) from the distribution's software repository. Installing new bundles, removing unwanted bundles and upgrading the operating system are all tasks handled by a command line program called swupd. To check for new versions of the operating system we can run swupd check-update. This will display the version of the operating system we are using (12100 in my case) and display the version number of the latest release, such as 12400. We can then run swupd update to grab the next version. There is no prompt to confirm the action, swupd simply proceeds. I found upgrades happened fairly quickly, requiring just a few minutes.
To find new bundles we may want to install we can run swupd bundle-add --list. This shows us a simple list of available bundles. The names of these bundles can be short and a bit cryptic and there are no detailed descriptions of bundles so far as I could find. Some item names are fairly straight forward, like the php bundle installs the PHP development language. But I wasn't sure what bat was, or what the differences were between the iot, iot-base and iot-extras bundles.
I noticed there was a bundle for the Xfce desktop. This package does install the components of the Xfce desktop environment, but I was unsuccessful in getting the desktop environment to launch on my laptop.
The swupd software manager works quickly and with very little output. This can make it look like the software manager has locked up, but it always successfully completed its tasks while I was experimenting with it. I was able to install a few tools and experiment with them and found Clear Linux to be stable and fast, as advertised.
I was pleased to note changes to the operating system are persistent across reboots with the changes and upgrades I made being written to the USB thumb drive. All in all, I felt like Clear Linux was a cousin to RancherOS which I explored in my article on small Linux distributions. Like RancherOS, Clear Linux focuses on being a small platform on which we can add new bundles, containers or services. It's probably not an operating system a person would run at home, at least not on a desktop computer, but Clear Linux's performance and simplified software management does make it an appealing option for cloud and server deployments. If you are interested in squeezing more performance out of a server system, I recommend looking through the distribution's documentation as it has several helpful hints and tutorials for setting up services.
* * * * *
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
|Miscellaneous News (by Jesse Smith)
GhostBSD's network utility ported to FreeBSD, Ubuntu coming to the Fairphone, elementary OS crowd funding an app store
For a while now people running the GhostBSD operating system have been able to use a graphical desktop utility to connect to nearby networks. The tool, called NetworkMgr, has a similar interface and purpose as the Network Manager program that is used by most Linux distributions. The easy point-n-click nature of the GhostBSD networking tool has made it an attractive option to many FreeBSD users and the NetworkMgr program has recently been added to FreeBSD's port collection. Detailed information on the NetworkMgr port can be found on the FreshPorts website.
* * * * *
Canonical, the company behind the popular Ubuntu operating system, will be showcasing an interesting device at Mobile World Congress in Barcelona at the end of February. The Canonical booth will be featuring the Fairphone 2 mobile device running Ubuntu Touch as its operating system. "The Ubuntu Community UBports has one mission: to have the open source software Ubuntu on every device, starting with smart phones. UBports' actions are based on collaborative development where developers are putting Ubuntu on different smart phones. During the Mobile World Congress in Barcelona end of February UBports will show a very special combination: Ubuntu on the Fairphone 2. With this successfully working device two worlds come together: sustainability and open source." The Fairphone is a development effort to create a modular phone where individual pieces of the phone can be repaired or upgraded. This allows the owner of the Fairphone to upgrade or modify their phone rather than regularly purchasing a new device. The Fairphone 2 can run both the Android and Ubuntu Touch operating systems, mostly due to porting work done by the UBports project. Further information on the phone and UBports can be found on this Ubuntu Insights page.
* * * * *
The elementary OS team is trying to entice more developers to create software for Linux by creating a pay-what-you-want app store. The specifications for the elementary app store outline a portal where Linux users will be able to download third-party software that is DRM-free and pay what they want. This approach to providing software to Linux users on a pay-what-you-want basis has worked well for Humble Bundle sales. "If the Humble Indie Bundle has shown us anything, it's that people place varying amounts of value on indie content and you can still be wildly successful while letting people vote with their wallets. We believe that pay-what-you-want both allows indie developers to get paid for their time and ensures that apps are available to the widest audience possible. We've built our company on pay-what-you-want by making every release of elementary OS available with this model. We're excited to bring this unique model to our users and third party developers by making AppCenter 100% pay-what-you-want." The elementary OS team is running a crowd funding campaign in order to try to raise the money to develop their AppCenter.
* * * * *
These and other news stories can be found on our Headlines page.
|Tips and Tricks (by Jesse Smith)
Package compression compared
These days people move a lot of data over the Internet. We load web pages, view videos, stream music and download software over our network connections. Ideally, we would like the things we download to use as little bandwidth as possible. Reducing bandwidth means finding a form of data compression which will keep our downloads small and, hopefully, not use up too much of our processor's time.
This past week I decided to try out five different compression technologies to see how they compare in terms of the time required to compress (or decompress) a package archive. I also measured how much each compression method was able to shrink the size of the archive and listed these statistics in the chart below.
I selected these five compression methods (bzip2, gzip, lzip, LZOP and xz/LZMA) because they are the options listed in the tar manual page and therefore most likely to be used when creating package archives. To test each compression method, I put together a package archive which included several text files, some images and some binary data (system libraries). I then compressed and unpacked the archive multiple times and recorded the average time it took to create and unpack the compressed archive.
The results of my test are listed below with the best results marked in bold. In each field, lower values are better.
||Average time to compress (s)
||Average time to unpack (s)
||Compressed size (%)
As you can see from the above chart, the xz/LZMA compression option (as offered through tar) provided strong compression, though relatively slow performance. The gzip method, which is probably the most commonly used way to compress tarballs, offers a great deal of speed and pretty good compression. The LZOP approach worked so quickly I was not sure at first it had done anything at all. LZOP did well when considering how quickly it worked, but the trade-off was the lowest compression ratio of the trial.
Looking at the above statistics, I think it becomes more clear why packagers tend to favour the compression methods (typically bzip2, gzip and xz) they use. The gzip approach is very quick, bzip2 offers a pretty good balance between performance and compression while xz trades off performance for better compression.
* * * * *
For more questions and answers, visit our Questions and Answers archive.
|Released Last Week
Alessio Fattorini has announced the release of NethServer 7.3. The NethServer distribution is a CentOS-based project for servers and features a modular design along with web-based administrative controls. The new version can use Samba to replace Microsoft Active Directory domain controllers and features centralized account management. "NethServer is now able to act as a Samba Active Directory Controller. NethServer can replace a Microsoft Active Directory Domain Controller Native MS-Windows management tools, like RSAT tools and AD PowerShell are compatible with NethServer Group policies can be deployed through native MS-Windows tools Windows workstations can seamlessly join the AD Domain, no more registry tweaks are needed. NethServer 7 brings a centralized account management (so-called 'multi-site') supporting authentication and authorization against either a local or remote accounts provider." Additional details can be found in the NethServer release announcement.
Juergen Daubert has announced the release of CRUX 3.3, a new version of the project's lightweight (and systemd-free) Linux distribution designed for experienced Linux users (or users willing to follow a detailed handbook). This is the distribution's first stable release in nearly 15 months. "The CRUX team is happy to announce the release of CRUX 3.3. CRUX 3.3 comes with a multilib toolchain which includes glibc 2.24, GCC 6.3.0 and Binutils 2.27. Kernel - Linux 4.9.6. CRUX 3.3 ships with X.Org 7.7 and X.Org Server 1.19.1. The ISO image is processed with isohybrid and is suitable for burning on a CD and putting on a USB drive. UEFI support is available during installation with dosfstools, efibootmgr, and grub2-efi added to the image. Important libraries have been updated to new major versions which are not ABI compatible with the old versions. We strongly advise against manually updating to CRUX 3.3 via ports, since these changes will temporarily break the system." Here is the brief release announcement, with further details provided in the release notes.
* * * * *
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. Thanks to Linux Tracker we are able to share the following torrent statistics.
Torrent Corner statistics:
- Total torrents seeded: 295
- Total data uploaded: 56.5TB
|Upcoming Releases and Announcements
Summary of expected upcoming releases
There are a lot of archive formats out there, each with a different set of strengths and weaknesses. Some formats are designed to be fast, others are portable and some strive to produce very small archives. This week we would like to find out if you have a preferred format to work with. You can leave us a comment with your reasons below.
You can see the results of our previous poll on portable packages, virtual machines and containers here. All previous poll results can be found in our poll archives.
Favourite archive format
|BZIP2: ||98 (5%)|
| GZIP: ||280 (15%)|
| LZIP: ||67 (4%)|
| LZOP: ||10 (1%)|
| RAR: ||159 (8%)|
| XZ: ||263 (14%)|
| ZIP: ||394 (21%)|
| Other: ||178 (9%)|
| No strong preference: ||458 (24%)|
Testing searches for language support
This past week we introduced a new search feature: finding distributions based on multi-language support. It is now possible to filter search results based on which languages a distribution supports out of the box.
At the moment our information on which languages each project includes is somewhat limited and there are gaps in our data. We mostly have just a project's website or wiki to use for confirmation of multilingual support. For this reason, some of the projects in our database simply have "Yes/Other" listed in the multi-language field and other projects may have an incomplete listing of included language codes. If you spot a gap our information, please help us correct it by e-mailing us with a link to where the distribution has listed their supported languages. Together we can make the language search function more useful.
We have also added a page which lists the torrents we are seeding and have seeded in the past. The new Torrent Archive can display torrents listed alphabetically (if you want to look for a specific distribution) or by date (if you want to find a recent upload).
* * * * *
Distributions added to waiting list
- SLG OS. SLG OS stands for the Security Learning Group Operating System. The distribution is a Persian-language operating system based on Ubuntu and featuring the Budgie desktop environment.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 20 February 2017. 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)
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 |
DigAnTel was a free digital / analog VoIP telephone system based on CentOS and using Asterisk, FreePBX with VoicePulse module, Openfire, vtigerCRM, Postfix, OpenVPN, and automated Polycom Phone support. DigAnTel was the glue to bind these technologies, thus creating a unified telephony system for a home or small business. The installation was completely automated and doesn't require a working knowledge of Linux or Asterisk.