DistroWatch Weekly, Issue 664, 6 June 2016

Feature Story (by Jesse Smith)

Sabayon 16.05



Sabayon is a Linux distribution that is based on Gentoo. Sabayon takes on some of the characteristics of its parent, providing users with a rolling release distribution that can make use of both binary and source software packages. Recent snapshots of Sabayon offer support for computers running on 64-bit x86 processors along with Raspberry Pi 2 & 3 computers. Perhaps the biggest new feature of Sabayon though is the launch of Sabayon Community Repositories (SCR). These new repositories provide a way for community members to build and distribute software for Sabayon without the necessity of getting their software into Sabayon's official repositories.



There are seven editions of Sabayon, including the builds for Raspberry Pi computers. There are several desktop editions, a Server edition and a small Minimal edition. I decided to begin my trial with Sabayon's KDE edition which is a 2.7GB download. Booting from the distribution's media brings up a menu asking if we would like to run Sabayon's live desktop, perform an installation, boot to a text console, check the installation media for defects or perform a memory check. Taking the live desktop option loads the KDE desktop. The wallpaper shows a gravel road passing through farmland while a moon rises with the Sabayon logo on it. Icons on the desktop invite us to donate to the distribution, get on-line help and launch the system installer. At the bottom of the display we find the application menu, a task switcher and the system tray.



I found clicking the on-line help icon would open the Chrome web browser and bring me to a page where I could sign into a Sabayon chat room. Clicking the icon for the system installer would launch Calamares, a distribution-independent installer.



Calamares is a graphical system installer that begins by asking us to select our preferred language. On this initial screen we find buttons that link us to the Sabayon FAQ page and the distribution's release notes. These pages open in the Chrome web browser. When Chrome is launched from the Calamares installer it displays a warning letting us know the browser is being run as the root user and cautions us against doing this. The next few pages of the Calamares installer get us to select our time zone from a map of the world and select our keyboard's layout from a list. The partitioning section comes next and we can choose to either manually divide up our hard drive or wipe the disk and allow the installer to set up its own partitions. I quite like how Calamares handles manual partitioning. The disk partitioning screen is easy to navigate, responds quickly and gives us the chance to work with ext2/3/4, JFS, XFS and Reiser file systems. The disk partitioning screen also gives us the chance to decide where to place the boot loader, or to skip installing the GRUB boot loader altogether. The final step gets us to create a user account for ourselves. By default I noticed the user creation screen assumes we want to be able to log into Sabayon without providing a password, but we can click a box to disable this feature. The installer then sets up Sabayon on our disk and concludes by giving us the chance to reboot the computer or return to the live desktop environment.



I ran into a problem when I rebooted the computer and tried to explore my new copy of Sabayon. The system would boot, display a graphical splash screen for a few seconds and then switch to a text console with a login prompt. Switching to other terminals all showed the same text screen, there was no graphical login screen. I could sign into my user account and run startx to access a minimal graphical environment (the TWM window manager) which would display three virtual terminals and nothing else. This was clearly not the experience I was expecting and I did some poking through settings and log files.



I found that systemd (Sabayon's init software) was set up to boot to a graphical environment and, from my tests with startx and the live disc I knew my video card was supported. I believe the issue which caused the lack of graphical interface came from a configuration problem with the display manager services. Sabayon's KDE edition ships with three display managers (SDDM, LightDM and XDM). The SDDM service, when launched, would fail with the error "Two services allocated for the same bus name." LightDM would simply fail to start. The XDM software would run and launch a graphical login screen, but any attempt to login would immediately fail and return me to the XDM login screen.



At this point I gave up playing with Sabayon's KDE edition and downloaded the project's MATE media to see how the experience would compare. I found the MATE media was a lot smaller than Sabayon's KDE download. The KDE ISO is 2.7GB in size while MATE's is approximately 1.8GB.





Sabayon 16.05 -- MATE's Applications menu

(full image size: 1.5MB, resolution: 1280x1024 pixels)



Despite the large difference in the size of the two editions, exploring the two installation discs provided nearly identical experiences. The MATE edition provides us with a similar desktop theme, similar controls and the same system installer. When I finished installing the MATE edition and rebooted I was brought to a graphical login screen. Signing into my account brought up the MATE 1.10.2 desktop environment. MATE provides us with two panels, one at the top of the screen and the other at the bottom. The top panel features the system tray and the Applications, Places and System menus. The bottom panel provides us with a task switcher.



Shortly after I got signed into MATE for the first time, a notification appeared by the system tray telling me all of my software was up to date and there were no packages to upgrade. This struck me as odd since I installed Sabayon 16.05 several weeks after it was released. Clicking on the update icon in the system tray gives us the option of opening the distribution's package manager. When I opened the package manager there was a warning at the top of the window letting me know my repository information was out of date. This message was replaced after a few seconds with two new messages. The first reported there were 30 updates available in Sabayon's repositories. Buttons in the message window gave me the options: Show, Update, Ignore and "srsly ignore". The Show option shows a list of available updates, with the version and size of each new package. We can click on specific packages to update them one-by-one or click the aforementioned Update button to grab all new software updates.



The second note that appeared in the software manager reported there was important news I should read on the Sabayon website. Opting to read these messages showed me two news items. The first was from February 2014 and told me OpenRC was no longer a supported init option. The second message, from September 2015, told me the KDM display manager was being replaced with SDDM. Given my experience with the SDDM software and the KDE edition of Sabayon, I'm not sure the switch was a beneficial one.





Sabayon 16.05 -- Installing updated packages with Rigo

(full image size: 1.2MB, resolution: 1280x1024 pixels)



The software manager, which is called Rigo, not only installs software updates, it can be used to perform a wide range of tasks. Rigo's top level menu provides access to tools which help us browse alternative versions of Linux kernels, refresh our repository information, show installed applications and manage repositories. We can also browse categories of software to install. Each category displays a list of available software in alphabetical order and clicking an item gives us the option of installing it or bringing up a description of the software. I generally found Rigo worked well and I had no trouble installing and removing packages.



I had hoped Rigo would allow me to access the Sabayon Community Repositories (SCR), but this was not an option. I did some looking around the SCR website and found a tutorial for accessing the software in the SCR. At this point, the process for enabling the SCR on Sabayon is unusually long and requires adding a separate repository manager (called enman). I did walk through the process of adding one community repository (as the name implies, SCR is a collection of repositories rather than one unified collection of third-party software). I was able to install software from the repository and get it running. This requires a little command line work, but the steps required to install each package are clearly explained on the SCR website.





Sabayon 16.05 -- Installing new software packages with Rigo

(full image size: 1.2MB, resolution: 1280x1024 pixels)



Sabayon ships with lots of useful software. Looking through MATE's application menu I found the Chrome web browser, the HexChat IRC software and the Transmission bittorrent client. LibreOffice and the Gnumeric spreadsheet application are included. The Atril document viewer, MATE Dictionary and Eye of MATE image viewer are featured too. Digging further we find a calculator, archive manager and the Pluma text editor. The Audacious music player and the VLC multimedia player are included. The mpv player is included too and Sabayon ships with a full range of media codecs. The MATE edition of the distribution provides us with plenty of tools for adjusting the look and behaviour of the desktop environment. We can also make use of the Caja file manager and a system monitor. Network Manager is available to help us get on-line. Sabayon ships with the Clang compiler, Java and systemd 226. In the background we find version 4.5 of the Linux kernel. Sabayon uses a rolling release model so version numbers will trend upward over time.





Sabayon 16.05 -- The MATE Control Centre

(full image size: 722kB, resolution: 1280x1024 pixels)



While exploring the distribution I noted a few things I feel worth mentioning. One is that the application menu features entries offering to take us to key pages of Sabayon's website. This makes finding documentation and support a bit easier. I found that applications were listed in the application menu by name rather than by function. At first it seemed like no description was available for the various applications, but I found hovering my mouse over menu entries would provide an explanation of what the software did. I like this feature as otherwise new users are unlikely to know what Caja or Audacious are.



One feature I disliked was that the Chrome browser prompted for a key-ring password every time it launched. This is a semi-common feature across distributions and one I would like to see disabled.



At one point I went into the settings panel to set up my printer and found there was no Printer module. A search through the Applications menu did turn up a Manage Printers entry (it's under the System sub-menu). Clicking this module opened my web browser to a local web-based CUPS interface. This method of managing printers is a good deal more complex than the usual graphical CUPS printer manager. Unfortunately, I was unable to locate the appropriate printer with the web-based interface while the native CUPS module usually locates any nearby printers automatically.





Sabayon 16.05 -- Running various desktop applications

(full image size: 534kB, resolution: 1280x1024 pixels)



I tried running Sabayon in two test environments. I began with VirtualBox and found Sabayon worked well in the virtual environment. When running in VirtualBox, Sabayon performed smoothly, the distribution was able to automatically integrate into the virtual environment and make use of my screen's full resolution. When running on my desktop test machine Sabayon got off to a good start. A network connection was set up automatically and my display was set to its maximum resolution. I did run into one problem when running Sabayon on the desktop computer. I found when playing videos on YouTube in the Chrome web browser the video was not visible. I could hear the audio playing, but the video box remained blank. One quirk of the distribution was that, in either environment, Sabayon muted audio by default. I actually like this feature as it avoids the unexpected blast of sound some distributions play when the user logs in.



In both test environments, Sabayon's MATE edition used approximately 270MB of memory. The distribution tended to be a little slow when booting, but once the system was up and running, desktop performance was solid.



Conclusions



Sabayon is a distribution which tends to do a lot of interesting things and it does enough things differently to keep me intrigued. The rolling-release, hybrid source/binary approach is something I find unusual enough to keep me coming back, for example. Sabayon has an unusual software manager, Rigo, which works pretty well and I like that it provides news headlines along with software updates. Sabayon offers lots of different editions, giving just about everyone something they like.



I was enthusiastic this time around to explore the SCR. This community effort seems to be in its early stages and I think there should be an easier (or automated) way to enable community repositories. Despite the configuration steps required, the SCR will provide a wider ranger of software to Sabayon's users and I think it's a welcome feature.



The problem I tend to have with Sabayon (both in the past and again this week) is the project feels like it has been stretched too thin. There are lots of interesting ideas and a huge selection of options to be had, but I feel the quality of the features suffer. Being unable to get a desktop environment running on the KDE edition was the strongest example. Little glitches in the package manager, which kept showing me "news" from years ago, were another. The patchy printer support was something most users probably will not be able to navigate on their own.



All in all, I think Sabayon is doing good things and I think the distribution will appeal to people who like rolling releases. There are a few rough spots in the distribution, but I think working through those is generally worth the experience Sabayon offers. * * * * * 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)

Debian releases updated media, FreeBSD adds ZFS daemon, Qubes explains security practises and a new educational resource



The Debian project has released updated media for both Debian 7 "Wheezy" and Debian 8 "Jessie". The new installation images are not distinct versions of Debian, but provide security updates and fixes to the existing versions. " The Debian project is pleased to announce the fifth update of its stable distribution Debian 8 (codename Jessie). This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems. Security advisories were already published separately and are referenced where available. Please note that this update does not constitute a new version of Debian 8 but only updates some of the packages included. There is no need to throw away old Jessie CDs or DVDs but only to update via an up-to-date Debian mirror after an installation, to cause any out of date packages to be updated. " * * * * * The FreeBSD operating system has gained a new feature to improve disk handling and manage faults in ZFS storage pools. The new feature is provided by the ZFS fault management daemon (zfsd) and should be included in the upcoming release of FreeBSD 11.0. The zfsd service " Deals with hard drive faults in ZFS pools. It manages hot spares and replacements in drive slots that publish physical paths. " The new service is not managed directly, but rather operates automatically based on a pre-set configuration provided by the system administrator. * * * * * Most of us tend to consider the security of the packages we run. We want to make sure they come from trusted sources, such as a distribution's repository, and that the software is up to date. Few of us pause to consider whether the server which originally built the software, or the developer's computer where the source code was written, might be compromised. Joanna Rutkowska of the Qubes OS project does think about such avenues of attack and has written about the steps Qubes takes to keep their build processes secure. One example of the measures the Qubes project takes involves not trusting remote servers: " We have always built all the official Qubes packages and ISO images on our private computers, i.e. ones whose physical security we can reasonably guarantee. This is because we have always assumed all external infrastructure (aka 'the cloud') to be untrusted. Indeed, because datacenter personnel can always (stealthily) read/write the memory of systems or VMs running in their datacenters, allowing the build process to run there would always make it possible for external parties to either tamper with the build process and/or steal the release signing keys, if these were also uploaded, as many projects do. " * * * * * Learning a new operating system can be difficult. Everyone, at some point, needs to start with the basics and learn how the system works. In an effort to help Linux newcomers, a new website has been created which teaches people what Linux is, how to use it, how to work with packages and how to use the command line. The website, called Linux Journey, takes an on-line classroom approach to learning, providing exercises the reader can try and questions which test knowledge. For people who are new to Linux or who wish to brush up on a specific topic, Linux Journey is well worth a look. * * * * * These and other news stories can be found on our Headlines page.





Opinion (by Jesse Smith)

The cost of free software



In early May, a blog post appeared on the Slax website which read: " Build server machine (where Slax modules are compiled) is down since I'm reducing costs. From now on, I will be running the module builds only locally in virtual machine, occasionally, manually, few times per week. "



The change from using a dedicated build server to running builds in a virtual machine probably will not change much for Slax users, but the post does highlight a common thread I have been seeing in recent years. Many open source projects are regularly in need of funding. Back in 2009, the OpenBSD project reported it was in "dire need" of infrastructure upgrades and needed funds. This call for donations was echoed by the OpenBSD team again around the end of 2013 which resulted in a lot of public attention and, ultimately, more money flowing into the project. More recently, the HardenedBSD project has asked for help maintaining the infrastructure of the security-oriented project. Last year the NTPD project, a critical piece of software for most Internet-connected computers, was almost abandoned due to a lack of funding. The previous year, OpenSSL's Heartbleed bug highlighted how little support the critical security software had been receiving from its many users.



I could go on, the open source graveyard is littered with tombstones (or final blog posts) which indicate projects were ultimately discontinued due to a lack of funding. And I believe this highlights an important blind spot in the open source community: We tend to assume that because these projects give away their software without cost, the software can also be developed without cost. This is simply not the case.



Small projects can sometimes be created and maintained in a person's spare time and hosted on free services such as SourceForge, but any non-trivial project requires a heavy investment in time and, often, money. Domain names, download servers, computer equipment, even the electricity to run a developer's workstation ultimately requires funding. In the end, the creators of successful open source projects often end up paying the costs of developing and giving away their software for free. This means other, less expensive commitments tend to take priority over their open source projects.



In fact, while writing my first draft of this column, the Webconverger project posted the following message on their website: " Webconverger will always be open source, meaning you can check out the source code and fork Webconverger. Unconfigured it's still the best operating system to surf privately in my opinion. But there is no such thing as free of cost software. Since 2007 I've been working on Webconverger, mostly part time alongside my full time employment. However my circumstances have changed, I have a newborn sucking up all my spare time and I need this to be full time and enough to meet a Singaporean Employment Pass. "



As a result of these "real life" changes, the Webconverger distribution now charges for installations that are configured. The software can still be downloaded for free and the source code is still available, but to get the most out of Webconverger now requires a payment. A similar message was posted later the same day by the lead developer of Pinguy OS: " Thinking about killing off Pinguy OS. It is costing me more to run than I get from the project. The project is a sink hole. For the last 12 months I have been personally financing the project to keep it afloat. The project isn't self-financing anymore. "



Another example comes in the wake of the release of gNewSense 4.0, which is based on Debian 7. Debian 7 "Wheezy" is a few years old now and transitioned from full security support to limited long term support just before gNewSense 4.0 was released. This raised some security concerns on the gNewSense mailing list, to which gNewSense's lead developer, Sam Geeraerts, replied: " I agree that gNewSense lags too much. I do my best to keep it going while finding a balance with other commitments. I want to get started on version 5 as soon as possible. I'll gladly accept offers for help and I'm happy to mentor new volunteers. "



The unfortunate truth is, most software developers need to work other jobs in order to develop software they give away for free. Donations and volunteers can help reduce the cost of an open source project, but it is rare to find an open source project that actually makes more money in donations or sales than it costs to maintain the software.



Some people will, perhaps correctly, point out that open source software projects that cannot raise funds are simply being rejected by the market. Projects that are worthwhile and valuable will gain funding while projects people do not value will not receive donations due to a digital form of natural selection. I believe there is some truth to that. Many Linux distributions ask for donations, but chances are only the more popular ones will be able to attract enough users to support their infrastructure.



However, I also think relying on popularity for funding means critical, behind-the-scenes software will never be funded. While many of us directly use our web browser or media player, most of us do not work directly with OpenSSL, the network time protocol or our operating system's C library. Yet these are critical pieces of our operating system and we need them to work properly, ideally even securely. Someone, perhaps several someones, are needed to maintain these projects, patch their security flaws and keep them up to date with changing dependencies. Those people need support if we, the community, are going to reap the benefits of their hard work.



Luckily, the open source community seems to be waking up to the fact that critical pieces of infrastructure need to be actively maintained and funded. The Core Infrastructure Initiative was created by many organizations which rely on and recognize the importance of a healthy open source ecosystem. This is a step in the right direction, but it is still rare to find open source projects and distributions which are successfully supported by their users. At the same time, it is all too common to see project's like Slax get scaled back due to expenses.



I think it is wonderful we live in a world in which people tinker with software they find interesting and I think it is even better that people are so willing to give away their creations for free. Open source software, given away freely, is a gift. Unfortunately, I think it is a gift that we, as a community, are taking for granted. I hope, in the future, we see fewer projects being shut down due to a lack of funds and more projects thriving with the support of their users.





Torrent Corner

Weekly Torrents



Bittorrent is a great way to transfer large files, particularly open source operating system images, from one place to another. Most bittorrent clients recover from dropped connections automatically, check the integrity of files and can re-download corrupted bits of data without starting a download over from scratch. These characteristics make bittorrent well suited for distributing open source operating systems, particularly to regions where Internet connections are slow or unstable.



Many Linux and BSD projects offer bittorrent as a download option, partly for the reasons listed above and partly because bittorrent's peer-to-peer nature takes some of the strain off the project's servers. However, some projects do not offer bittorrent as a download option. There can be several reasons for excluding bittorrent as an option. Some projects do not have enough time or volunteers, some may be restricted by their web host provider's terms of service. Whatever the reason, the lack of a bittorrent option puts more strain on a distribution's bandwidth and may prevent some people from downloading their preferred open source operating system.



With this in mind, DistroWatch plans to give back to the open source community by hosting and seeding bittorrent files. For now, we are hosting a small number of distribution torrents, listed below. The list of torrents offered will be updated each week and we invite readers to e-mail us with suggestions as to which distributions we should be hosting. When you message us, please place the word "Torrent" in the subject line, make sure to include a link to the ISO file you want us to seed. To help us maintain and grow this free service, please consider making a donation.



The table below provides a list of torrents we currently host. If you do not currently have a bittorrent client capable of handling the linked files, we suggest installing either the Transmission or KTorrent bittorrent clients.



Operating System Torrent MD5 checksum Alpine Linux 3.4.0 alpine-3.4.0-x86_64.iso 624fcba785475c5105af5e89732151b7 Slackel 6.0.6 "Openbox" slackellive64-openbox-6.0.6.iso fba0c2fd833ec5fa235ff538c17c5195



Archives of our previously seeded torrents may be found here. All torrents we make available here are also listed on the very useful Linux Tracker website. Thanks to Linux Tracker we are able to share the following torrent statistics.



Torrent Corner statistics:

Total torrents seeded: 200

Total data uploaded: 36.8TB

Released Last Week

Porteus Kiosk 4.0.0



Tomasz Jokiel has announced the release of Porteus Kiosk 4.0.0, a major new release of the project's Gentoo-based distribution of Linux designed for web kiosks. The biggest change is a switch to the x86_64 architecture following Google's decision to drop support for the 32-bit Chrome browser on the Linux platform: " I'm pleased to announce that Porteus Kiosk 4.0.0 is now available for download. The Linux kernel has been updated to version 4.4.11, Mozilla Firefox to version 45.1.1 ESR and Google Chrome to version 50.0.2661.102. Packages from the userland are upgraded to the Portage snapshot tagged on 20160528. Here is an overview of the most notable features introduced in this release: added support for setting default microphone in case you have multiple capture devices in the system; it's now possible to download screensaver slideshow ZIP archive every X minutes; import certificates function has been extended to also support Citrix Receiver certificates.... " Read the release announcement and the changelog for further information.



Clonezilla Live 2.4.6-25



Steven Shiau has announced the release of a new version of the Clonezilla Live disk cloning software. The new release, Clonezilla Live 2.4.6-25, is based on Debian's Unstable (Sid) branch and features version 4.5.4 of the Linux kernel. " This release of Clonezilla Live (2.4.6-25) includes minor enhancements and bug fixes. Enhancements and changes: The underlying GNU/Linux operating system was upgraded. This release is based on the Debian Sid repository (as of 2016/May/29).Linux kernel was updated to 4.5.4-1. Partclone was updated to 0.2.88. Some segfault issues have been fixed. Add support for boot parameter ocs_preload*. It can be used to fetch tarall/zip/sh files from http(s), ftp, tftp, and local URL then extract to /opt/. Thanks to Aaron Burling (aaron_burling _at_ lkstevens wednet edu) for this idea and providing sample codes. Add package dos2unix... " A full list of changes and bug fixes can be found in the release announcement.



Linux Lite 3.0



Jerry Bezencon has announced the availability of a new release of Linux Lite, a lightweight distribution based on Ubuntu. The new version, Linux Lite 3.0, features a number of significant changes, including an overhaul of the graphical software manager. " Linux Lite 3.0 Final is now available for download. A lot has changed since Series 2. We have a new Login Manager, new boot theme, Lite Software has had an overhaul, new system theme (Arc), we've added Share Hardware Configuration (Lite Info), Folder access from the menu and upgrades are now automated and seamless in Series 3. In addition, there has been a lot of bug fixes and adjustments since the Beta release, thanks again for your feedback. Default Wallpaper - the default Final wallpaper represents the colors of our gem codename - Citrine accompanied by the Linux Lite logo. Lite Software - Lite Software has had an overhaul. We've added icons where there were Select boxes (thank you Misko). This helps people who identify with images and branding to easily locate their favorite software. You can select multiple programs to install by holding down Ctrl or Shift. We've also added Audacity (audio editor), Calibre (eBook reader and manager) and Pinta (Windows Paint.Net look-a-like) thanks to your suggestions. " Additional details and several screen shots can be found in the project's release announcement.





Linux Lite 3.0 -- The default desktop environment

(full image size: 517kB, resolution: 1280x1024 pixels)



Alpine Linux 3.4.0



Natanael Copa has announced the launch of Alpine Linux 3.4.0. Alpine Linux is a lightweight distribution which uses the musl C library and the BusyBox userland utilities. The latest version of the distribution supplies users with version 1.14 of the MATE desktop and version 4.4 of the Linux kernel along with LibreOffice 5.1. " Noteworthy changes when upgrading: The PHP packages got renamed from php to php5. The service cron got renamed to crond. BusyBox ping now use unprivileged ICMP sockets so binary does not need to be suid root. This means you need to be in group with gid 999-59999 for being allowed to send pings. Most ruby-* packages were removed. Use gem instead. " The release announcement has further details.



deepin 15.2



Melody Zou has announced the release of deepin 15.2, an updated version of the desktop-oriented, Debian-based distribution with a custom desktop environment called Deepin. This version delivers a new screen for launching applications and many updated packages, including the latest LTS Linux kernel: " deepin 15.2 adopts a new Launcher interface and intuitive search, adds safe boot support, and uses the 4.4 LTS kernel optimized and compiled by the deepin kernel team. System performance and resource allocation have been significantly improved. Also, this version comes pre-installed with the more stable CrossOver 15. The Launcher interface is more friendly and the search box is placed at the top of Launcher. The classification of applications is simple and clear and users can customize icon locations using the free sorting mode. Remote Assistance is an independent application now, deeply integrated with the distribution. No matter where you are, your friends or engineers can connect to your PC and to solve the problems you've encountered. " Here is the full release announcement with screenshots.



Slackel 6.0.6 "Openbox"



Dimitris Tzemos has announced the release of Slackel 6.0.6 "Openbox" edition, a new version of the project's lightweight Slackware and Salix-based distribution that is available both as a live or an installation image: " Slackel 6.0.6 Openbox has been released. Slackel is based on Slackware and Salix. It includes the Linux kernel 4.4.11 and the latest updates from Slackware's 'Current' tree. The 64-bit ISO image supports booting on UEFI systems. The 32-bit flavor supports both i686 PAE SMP and i486, non-PAE capable systems. Many improvements in Slackel-live-installer have been done. In 'Basic' installation, wicd is fully functional as is PCManFM in browsing network shares. Full multimedia support without having to install multimedia codecs while on live environment. Of course it is suggested that you install multimedia codecs to your system after installation. Slackel 6.0.6 Openbox includes the Midori 0.5.11 web browser, Claws-Mail 3.9.2, SMPlayer 16.4.0, Transmission 2.84.... " Visit the distribution's user forum to read the release announcement (includes videos). * * * * * Development, unannounced and minor bug-fix releases

ExTiX 16.3

Univention Corporate Server 3.3-0

NethServer 6.8-beta1

Whonix 13.0.0.1.1

NAS4Free 10.3.0.3-beta

Parabola GNU/Linux-libre 2016.06.01

Arch Linux 2016.06.01

SystemRescueCd 4.7.3

Q4OS 1.4.11

Upcoming Releases and Announcements

Opinion Poll

How can open source projects best raise funds?



As we mentioned in our Opinion column this week, open source projects such as Linux distributions, often struggle to raise funds to support development. This tends to be a common problem for all community projects and results in many open source projects being discontinued.



This week we would like to know what you think is the best way for open source projects to raise money to support their development and infrastructure. Do you think fundraising campaigns via Kickstarter make sense, or perhaps offering commercial support options? Should developers offer multiple editions under different licenses to encourage the purchase of commercial options? Please leave us a comment with your thoughts on the subject.



You can see the results of our previous poll on hardware support life times here. All previous poll results can be found in our poll archives. How can open source projects best raise funds?



Fundraising campaigns (Kickstarter or Indiegogo): 200 (18%) Commercial support: 153 (14%) Commercial/non-free editions: 96 (9%) More clear/flexible donation options: 415 (37%) Other: 45 (4%) I do not know: 210 (19%)