| DistroWatch Weekly
|DistroWatch Weekly, Issue 676, 29 August 2016
Welcome to this year's 35th issue of DistroWatch Weekly!
The Linux kernel hit a significant milestone this past week. It was just over 25 years ago Linus Torvalds announced his then-new kernel on Usenet. Since then Linux has spread wide and far, finding homes in mobile phones, servers, desktops and super computers. In our News section we tip our hats to this large, flexible and highly useful software project. This happy news is followed by darker tidings as we mark the passing of Gentoo member Jonathan Portnoy. We also discuss PC-BSD changing its name to TrueOS and we talk about Wayland becoming the default display software for the upcoming release of Fedora 25. Before Fedora 25 arrives, we decided to look at Korora 24, a Fedora-based distribution which places a stronger emphasis on desktop computing. Read out Feature Story for all the details on Korora. In our Questions and Answers section we talk about how to find software licensing information and licenses are also the subject of our Opinion Poll. As usual, we share a list of the torrents we are seeding and provide a list of the projects released last week. We are also pleased to announce Uruk GNU/Linux has been added to our database. We wish you all a wonderful week and happy reading!
- Reviews: Korora 24
- News: Fedora to run Wayland by default, PC-BSD becomes TrueOS, Gentoo loses long-term member and Linux turns 25
- Questions and answers: Finding software licensing information
- Torrent corner: BlackArch Linux, MidnightBSD, SparkyLinux
- Released last week: LinuxConsole 2.5, ConnochaetOS 14.2, Q4OS 1.6.1
- Opinion poll: How important are software licenses to you?
- Upcoming releases: Fedora 25 Alpha, openSUSE 42.2 Beta 1, OpenBSD 6.0
- New additions: Uruk GNU/Linux
- New distributions: Raspberry Slideshow, Enchantment OS, FastComputer Linux, Petu
- Reader comments
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (24MB) and MP3 (34MB) formats
|Feature Story (by Jesse Smith)
The Korora distribution is based on Fedora and provides users with several desktop editions. Each edition of Korora ships with multimedia support and with several third-party repositories enabled. This gives Korora access to a wider range of software with its default configuration.
The latest release of Korora, version 24, is based on Fedora 24 and includes the same changes and technology as its parent. The Korora release is available in four flavours (Cinnamon, GNOME, MATE and Xfce). A fifth edition featuring KDE's Plasma desktop is planned, but was not available when I began this review. The new release media is available for the 64-bit x86 architecture exclusively, however existing Korora 23 users who run 32-bit systems can perform live upgrades to Korora 24. The Pharlap driver manager has been removed from this release.
I decided to try the MATE edition of Korora 24 which is available as a 2GB download. The live media boots to the MATE desktop. At the top of the display we find the Applications, Places and System menus along with the system tray. Down the left side we find a quick-launch bar and there is a task switcher at the bottom of the screen. On the desktop is a single icon for launching the system installer. Shortly after the desktop loads, a welcome screen appears. The welcome screen offers us quick access to various resources, including a document on finding additional software and community support. The welcome screen provides us with a list of new features available in Korora 24 (such as version 6 of the GNU Compiler Collection). Other buttons on the welcome screen launch the system installer and open a web browser to the project's support forum.
Korora uses the same graphical system installer Fedora uses. We begin by selecting our preferred language from a list. Then we are brought to a hub screen where we can access various configuration modules. These modules, which we can run in any order, help us set our keyboard's layout, partition the hard disk and set up networking. I find the installer's partitioning screen oddly awkward to use, the controls are not clear and the partition manager has some odd quirks. For example, the only way I have found to get it to use up the available space on a disk is to leave the size field of a new partition blank. At any rate, we next move on to a second hub screen where we are asked to create a password for the root account. We can optionally set up a regular user account on this second hub page while the installer copies its file in the background. When the installer is finished we can return to Korora's live desktop environment and continue to explore until we are ready to reboot and try our new copy of the distribution.
Korora 24 -- Using the on-screen keyboard
(full image size: 692kB, resolution: 1280x1024 pixels)
Our locally installed copy of Korora boots to a graphical login screen decorated with the project's logo. From there we can sign into our user account, bringing us back to the MATE desktop. The first time we login, the welcome screen appears, giving us access to the distribution's documentation and support resources. Earlier I mentioned the general two-panel (and a launch bar) layout of the MATE edition. I would also like the share the observation that Korora uses a changing background, giving us a variety of wallpapers. The distribution uses a high contrast theme with round icons, which I find fairly pleasant. However, there were aspects to the default theme I found troublesome. For example, some application windows could be resized from the bottom corners of the window while other applications had to be resized from the top corners of the window. This meant I regularly switched back and forth between resizing methods and there did not seem to be any easy way to tell which applications used which behaviour. I also found the default theme made it difficult to tell when a button or widget had been selected by a keyboard action. This made navigating applications using the keyboard unusually challenging.
Digging through Korora's application menu we find the Firefox web browser (without Adobe's Flash plugin), the Thunderbird e-mail client, the HexChat IRC software, the Liferea RSS feed reader, the Pidgin messaging software and the Ekiga softphone. LibreOffice is available as are the FBReader e-book reader and the Atril document viewer. The Darktable and Shotwell photo managers are included along with the GNU Image Manipulation Program, the Inkscape application and a scanning tool. The
Asunder audio CD ripper is available along with the Audacious audio player, the Audacity audio editor and the Handbrake media transcoder. I found a copy of the Pitivi video editing software, the VLC multimedia player and the Xfburn disc burning software. Attempting to play video files would cause the VLC player to launch and successfully play the given video. However, when I tried to play audio files the Audacious player would launch and report it was missing the necessary codecs. Opening the same audio files with VLC would cause the audio files to play. Exploring the application menu further we find the Caja file manager, the GParted disk partitioning tool, a system monitor and a policy generator for SELInux. Korora ships with an on screen keyboard, an ownCloud desktop client, a text editor, calculator and archive manager. In the background we find Java, the GNU Compiler Collection and systemd version 229. Network Manager is available to help us get on-line. Korora ships with version 4.6.3 of the Linux kernel.
Korora 24 -- Getting news updates with Liferea
(full image size: 785kB, resolution: 1280x1024 pixels)
I ran Korora in a VirtualBox virtual machine and on a desktop computer. Korora worked well on the physical desktop machine. The system was responsive and my hardware was properly detected. The distribution worked fairly well in the VirtualBox environment too, but by default could not handle displaying the desktop using my screen's full resolution. VirtualBox guest modules can be found in the default set of software repositories and installing them allowed the distribution to make full use of my display. In either environment Korora tended to use about 370MB of memory when logged into the MATE desktop. Korora was generally stable during my experiment. The system locked up just once while I was trying to logout, forcing a hard reboot.
After using Korora for a while I realized I had not been notified of any new software updates. I opened the distribution's software manager, Yum Extender, which acts as a front-end to the DNF package manager. Yum Extender provides us with tools to perform searches for packages and we can see lists of installed packages and software available for download. Packages are listed in simple text format with the name of each package and a description. We can check a box next to a package to mark it for installation or removal. Yum Extender can also enable/disable repositories with recognized repositories including Google, VirtualBox and RPMFusion.
Korora 24 -- Managing packages with Yum Extender
(full image size: 663kB, resolution: 1280x1024 pixels)
Yum Extender tends to be a bit on the slow side, taking a long time to refresh its repository information. Though I do think the current release operates faster than past versions of the software manager. I also found it odd Yum Extender displays both 32-bit and 64-bit versions of packages on a 64-bit system, greatly padding the number of packages available.
The first day I was running Korora there were 164 updates available, totalling 369MB in size. I tried to install these new packages using Yum Extender and the software manager failed, reporting it could not proceed due to dependency issues. I immediately switched to a virtual terminal and tried to install the waiting updates with the DNF command line program. DNF was able to successfully download and install all available updates. As using DNF was faster and more reliable, I tended to stick with using the command line program for managing software. The one issue with DNF I ran into was it kept asking me to confirm it could import security keys for third-party repositories. This in itself is not bad, but DNF should probably recognize the keys to the default repositories without bothering the user with key management.
Korora's MATE edition ships with a control panel which provides many modules for managing the desktop and underlying operating system. There are modules for changing the desktop's appearance, working with user accounts, configuring the firewall and managing background services. We can find modules to select which applications should run when we sign in, configure our preferred applications, set up the screensaver and manage printers. Korora's firewall utility supports working with different zones, which means we can create one set of firewall rules for home, another for work and a third for public spaces. The different zones mean we can block network traffic depending on our location, a nice feature to have when working on a portable device.
Korora 24 -- Adjusting system settings
(full image size: 659kB, resolution: 1280x1024 pixels)
The modules included in the control panel worked well for me. There is a great deal of power and flexibility to be had. Most of the modules do a good job of supplying a lot of options while still being fairly straight forward to use. I did find the control panel would sometimes use a lot of my CPU cycles, bringing my desktop to a crawl. This happened rarely, but when it did the panel's process would eat all available CPU resources, even when no configuration modules were open. Killing the process or logging out appeared to be the only solution.
I find it difficult to talk about Korora without comparing the distribution to its parent, Fedora. Modern versions of Fedora tend to be relatively minimal for a desktop distribution. With Fedora's Workstation edition, we are given the desktop, some essentials and adding the specific tools we want is left to the user. This often involves tracking down third-party software repositories and spending a few minutes to a few hours installing the applications we plan to use. Fedora errs on the side of caution when it comes to software licensing and is careful not to package non-free or patent encumbered software. This limits multimedia support on Fedora.
Korora essentially takes Fedora Workstation and tries to set it up with the media support, applications and third-party repositories people are likely to want. This makes Korora a larger download (2.0GB vs 1.4GB for Fedora), but it means we have many of the applications we will probably want immediately following the installation. We also have lots of neatly organized configuration tools by default with Korora and that is a feature I appreciate. Personally, I like Korora's approach to including more software. Even without the extra software installed for us, I think Korora would be worth the extra download size just for having several third-party repositories configured for us.
Apart from the default software and repositories, Korora stays very close to its parent. At its heart Korora is still Fedora, so almost all of the differences boil down to what is set up for us out of the box.
Looking at Korora by itself, ignoring its parentage for a moment, I think the distribution is a fairly solid desktop operating system. Korora ships with fairly modern packages and users have access to a lot of software through Korora's many default repositories. The system was responsive and I like Korora's default theme. The MATE edition is relatively light on memory and the distribution worked well with my hardware. I have said before one of Korora's few weaknesses is package management. Yum Extender is not a bad software front-end, but it is a bit slow and it had trouble installing the first wave of upgrades post-installation. These problems can be worked around by using the command line DNF package manager. I did run into a few glitches while using Korora, but nothing that consistently gave me trouble, so all-in-all, I was happy with my experiences this week.
* * * * *
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)
Fedora to run Wayland by default, PC-BSD becomes TrueOS, Gentoo loses long-term member and Linux turns 25
The Fedora project has been one of the more active proponents of the new Wayland display technology. Wayland is intended to eventually replace the aging X display software for graphical applications and desktop environments. Running GNOME on Wayland has been an available session option on the past few versions of Fedora, but now it looks like Wayland is going to be the default display session in Fedora 25. One Fedora issue report reads: "There are still some bugs that are important to solve. However, there is still time to work on them. And the legacy Xorg session option will not be removed, and will be clearly documented how to fallback in cases where users need it, such as a11y users. It is likely there will be additional bugs/issues to solve during F26 development and beyond, but it's unlikely we can get the level of exposure and testing desired without keeping Wayland as the default. The WG would like FESCo to consider granting an exception that allows the WG to continue on with Wayland as the default, rather than reverting to Xorg as default for the F25 release." At the moment, it looks as though this plan will be followed, making Wayland the default for Fedora 25, due to launch in November.
* * * * *
The PC-BSD project is undergoing a name change. The FreeBSD-based operating system was previously comprised of two editions which were listed under separate names. The original PC-BSD edition was the project's desktop flavour while the server edition was called TrueOS. The project is changing its labelling and will refer to both editions as TrueOS going forward. The project's founder, Kris Moore, explained the need for the change: "We've already been using TrueOS for the server side of PC-BSD, and it made sense to unify the names. PC-BSD doesn't reflect server or embedded well. TrueOS Desktop/Server/Embedded can be real products, avoids some of the alphabet soup, and gives us a more catchy name."
* * * * *
The Gentoo project has shared sad news this week. Long time Gentoo member Jonathan "avenj" Portnoy has passed away. Portnoy was with the project for many years. A post on the Gentoo website marks his passing: "Jon was an active member of the International Gentoo community, almost since its founding in 1999. He was still active until his last day. His passing has struck us deeply and with disbelief. We all remember him as a vivid and enjoyable person, easy to reach out to and energetic in all his endeavours. On behalf of the entire Gentoo Community, all over the world, we would like to convey our deepest sympathy for his family and friends. As per his wishes, the Gentoo Foundation has made a donation in his memory to the Perl Foundation."
* * * * *
The Linux kernel has passed another milestone, turning 25 years old on August 25, 2016. Linus Torvalds, the founder and lead developer on Linux, posted on Usenet back in 1991: "I'm doing a (free) operating system (just a hobby, won't be big and professional like GNU) for 386(486) AT clones. This has been brewing since April, and is starting to get ready. I'd like any feedback on things people like/dislike in MINIX, as my OS resembles it somewhat (same physical layout of the file system (due to practical reasons) among other things). I've currently ported bash(1.08) and gcc(1.40), and things seem to work. This implies that I'll get something practical within a few months, and I'd like to know what features most people would want. Any suggestions are welcome, but I won't promise I'll implement them." Now, 25 years later, Linux is one of the most widely used operating system kernels. Linux sits at the heart of most of the world's fastest super computers, runs the majority of smart phones and can be found on a significant number of servers and desktop computers.
* * * * *
These and other news stories can be found on our Headlines page.
|Questions and Answers (by Jesse Smith)
Finding software licensing information
Confirming-freedom asks: I assume most of the software bundled with my Linux distribution is free software, but how do I check? Is there a package manager function I can use to see what license (ex. GPL) is being used?
DistroWatch answers: Some package managers do provide a way to view licensing information, others do not. Most Linux distributions do provide a method for finding out which software license was applied to a given package. For instance, if you are running Debian or one of the many distributions based on Debian (Ubuntu and Linux Mint, for example) then licensing information for each package is in the /usr/share/doc directory in a file called copyright. The license information for the VLC media player is available in the file /usr/share/doc/vlc/copyright. The licensing information for the vim text editor can be found in /usr/share/doc/vim/copyright.
People who are running a member of the Fedora/Red Hat/CentOS family of distributions can find licensing information using the rpm command line package manager. Passing rpm the "-qi" flag and a package name will display a full page of information, including the name of the license. For example, the following will display information on the LibreOffice package:
rpm -qi libreoffice
To filter out all the information except the licensing field, we can use grep to only show the name of the license.
rpm -qi libreoffice | grep License
People using distributions that feature the pacman package manager, such as Arch Linux and Manjaro, can find licensing information by running pacman with the "-Qi" flag.
pacman -Qi vlc
When running Arch Linux and its derivatives, the pacman utility will often report a package's license is "custom". This means licensing information on the package can be found in the /usr/share/licenses directory. For instance, the license for the zip package can be found in /usr/share/licenses/zip/LICENSE and the license for sudo package can be found in the /usr/share/licenses/sudo/LICENSE file.
Different operating systems provide other ways to view licensing information. For example, on FreeBSD the pkg command will display details about a package, including its license. The following command will display the license of the Transmission command line utility on a FreeBSD system:
pkg info transmission-cli
If the distribution you are running does not provide licensing details you can usually find the information you want in one of three ways. Desktop applications usually have an "About" menu option which will show licensing or copyright information. Command line utilities will often display licensing information if you run them with the "--help" or "--version" parameters. When all else fails, check the upstream project's website. Licensing information will often be displayed on the project's About or FAQ pages or in the top level of their source code repository.
* * * * *
For more questions and answers, visit our Questions and Answers archive.
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.
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: 229
- Total data uploaded: 42.8TB
|Released Last Week
Yann Le Doare has announced a new release of LinuxConsole. a lightweight, independent distribution whose editions feature the LXDE and MATE desktop environments. The new release, LinuxConsole 2.5, features version 4.1 of the Linux kernel, offers support for booting on UEFI-enabled hardware and includes many games. The 32-bit build runs the LXDE desktop while the 64-bit build runs MATE as the default desktop. "This release is designed to be used with children and kids : It's easy to install it on old computers with the Windows Installer , a lot of games and music software are available for use Both releases boots with Busybox 1.24.2. Core software and libraries are stored into a squashfs file system." Screen shots, along with a complete list of featured games, tools and educational software that can be found in the distribution is featured in the release announcement on the project's front page.
LinuxConsole 2.5 -- Running the LXDE desktop
(full image size: 483kB, resolution: 1024x768 pixels)
Henry Jensen has announced the release of a new version of the Slackware-based ConnochaetOS distribution. ConnochaetOS ships with free software (as defined by the Free Software Foundation) exclusively, stripping out binary blobs and replacing proprietary components where possible with freely licensed packages. "I am proudly announcing ConnochaetOS 14.2, based on Slackware and Salix 14.2. As always it contains only free/libre software as defined by the Free Software Foundation (FSF). We are now using our own deblobbed Linux kernel, named 'kernel-free' based on the de-blobbing mechanism done by Debian GNU/Linux. ConnochaetOS contains: The de-blobbed Kernel Linux 4.4.19, IceWM 1.3.12, Iceweasel 45.3.0. In our slack-n-free repo we provide the current versions of Iceape and Icedove, the brand-new qt5-webengine based web browsers Qupzilla and Otter-browser and LibreOffice 5.1.4 as provided by Eric 'Alien' Hameleers." ConnochaetOS strives to maintain backward compatibility with Slackware and Salix. The full announcement can be found in the project's release announcement.
The Q4OS team has announced the release of a new version of their lightweight, Debian-based distribution. The new version, Q4OS 1.6, ships with an updated version of the Trinity (formally KDE 3) desktop environment. "The significant Q4OS 1.6 'Orion' release receives the most recent Trinity R14.0.3 stable version. Trinity R14.0.3 is the third maintenance release of the R14 series, it is intended to promptly bring bug fixes to users, while preserving overall stability. The complete list and release notes you will find on the Trinity desktop environment website. New Q4OS 1.6 release includes set of new features and fixes. The default desktop look has been slightly changed, Q4OS 'Bourbon' start menu and taskbar has been polished a bit and has got a few enhancements, for example the icons size varies proportionally to the system panel. Native Desktop profiler tool has got new, optimized 'software to install' list." The full release announcement can be found on the project's blog page.
* * * * *
Development, unannounced and minor bug-fix releases
|Upcoming Releases and Announcements
Summary of expected upcoming releases
How important are software licenses to you?
Software licensing tends to be a hot topic among developers. The details and permissiveness of a software license can attract new developers and businesses or drive them away, causing many projects to choose their licensing carefully. Other projects, particularly small ones, may simply stamp whichever license the author is most comfortable with on the code.
This week we would like to hear from the non-developers among our readers to find out whether a project's license influences whether you use the software. Do you go out of your way to use software licensed under the GPL, BSD or MIT licenses? Do licenses play a part at all in which distributions and applications you install?
You can see the results of our previous poll on what is holding people back from using Linux here. All previous poll results can be found in our poll archives.
How important are software licenses to you?
|I install software which matches my preferred licenses exclusively: ||58 (4%)|
| I tend to install software which uses my preferred license: ||506 (33%)|
| I rarely factor in the license in my consideration: ||465 (31%)|
| I do not consider the license when I install software: ||487 (32%)|
New distributions added to database
Uruk GNU/Linux is a free software desktop distribution based on Trisquel. It follows the licensing guidelines of the Free Software Foundation. Uruk primarily uses .deb package files, but strives to support a wide range of package formats, including .rpm files.
Uruk GNU/Linux 1.0 -- Running the MATE desktop
(full image size: 292kB, resolution: 1280x1024 pixels)
* * * * *
Distributions added to waiting list
- Raspberry Slideshow. Raspberry Slideshow is focused on quick-to-set-up image and video slideshows for the Raspberry Pi. Insert a USB key with image/video files or text files and reboot. The documents will be displayed on the Pi's screen.
- Enchantment OS. Enchantment OS is a Linux distribution which is based on Xubuntu LTS and designed with less technical users in mind.
- FastComputer Linux. FastComputer Linux is an openSUSE-based distribution which ships with a great deal of software pre-installed.
- Petu. Petu is a user friendly distribution based on openSUSE 13.2. It supports the English, Russian, French, Hungarian, German, Portuguese, Spanish and Italian languages.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 5 September 2016. 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
|Reader Comments • Jump to last comment
1 • PC-BSD ---> TrueOS ? (by JD on 2016-08-29 04:08:49 GMT from North America) |
I always thought PC-BSD was a fricken awesome name. I don't get or like "TrueOS". Maybe it will take some getting used to. But again PC-BSD was a awesome name. It meant BSD you can run on your PC Desktop. Anyway not trying to be a negative nelly or anything just my thoughts. I know it was not a easy decision. maybe iXSystems told Kris he had to change it idk.
2 • @1 PC-BSD ---> TrueOS ? (by Paraquat on 2016-08-29 05:56:38 GMT from Asia)
"I always thought PC-BSD was a fricken awesome name."
I couldn't agree more. If nothing else, it was at least very descriptive - the name made it immediately obvious that this was a BSD-based operating system, as opposed to a Linux distro or even a proprietary OS. From this point forward, newbies in search of a BSD flavor are going to have to figure out for themselves what TrueOS is. I suppose we should be grateful they still include "OS" in the name, and didn't choose "The-One-True-Path" or something like that.
3 • korora 24 (by enrico on 2016-08-29 07:20:41 GMT from Europe)
i like korora, as i like fedora, that is my first linux distro, but i point out some details:
software management, apart from workstation, which is gnome, is a bit intimidating in fedora distro and derivatives, only yum extender can perform such task, and it has few glitches, but it's ok if you can go with the console,.
the first time you made upgrades, fedora ask you to confirm importing keys, in both cases, via console or via package manager, i think it's a security feature, and not a bug or a glitch.
i like korora because is an effort to make fedora simpler to install and live with, but if you have more time to set up and configure, and you know how to do the most important settings,, then fedora itself is better
4 • PC-BSD -> TrueOS (by SuperOscar on 2016-08-29 08:28:30 GMT from Europe)
Looks like the announcement of the name change PC-BSD -> TrueOS hasn’t quite reached their web admins yet. PC-BSD website http://www.pcbsd.org/ is still there and there’s not a word of anything changing. The new URL http://www.trueos.org/ exists but there’s nothing to denote that this is what used to be called PC-BSD in days past. Not very smart marketing, that.
5 • Fedora (by Ron on 2016-08-29 08:32:45 GMT from North America)
Every time Fedora is mentioned or reviewed it gets a poor review because Fedora does not provide codecs installed or the repositories for them. Has anyone ever heard of Easylife at Distrowatch? Just download and install it and then run it and check off the boxes of stuff you want and you have all the codecs for music and dvds and even flash plus lots of other stuff that many find too difficult to search for and install manually. It has all the restricted stuff you need. How hard is that? How nice is it that you have the choice of what you want?
6 • DistroWatch Weekly (by Andy Mender on 2016-08-29 09:08:12 GMT from Europe)
I also don't agree the name "PC-BSD" should be changed. I understand the developers' concerns regarding naming conventions, but I feel PC-BSD was already a strongly established trademark. For so long it was fine to produce 2 separate distributions. Why merge the names now? :(
There were talks about RPM Fusion and why it should be provided as an initial install option. The bigger problem, though is that many media programs don't have support for those codecs compiled in. OpenSUSE suffers from similar issues.
7 • Finding software licensing information (by solt87 on 2016-08-29 09:44:42 GMT from Europe)
On Debian (and it's descendants) one can also use the Virtual Richard Stallman (vrms) program to report installed non-free software. =)
8 • @4 (by e ludolf on 2016-08-29 10:13:39 GMT from Europe)
Please read the website they clearly explain everything.
Its hard to read nowedays by some people (if not most of them)
9 • PC-BSD -> TrueOS (by Paraquat on 2016-08-29 11:12:12 GMT from Asia)
Just thought I'd add that there's no reason why there couldn't be a "PC-BSD Desktop" and "PC-BSD Server" edition. It's a common naming convention among Linux distros (ie Fedora, Ubuntu, Debian, etc). I suppose the only reason why that practice hasn't been adopted by BSD developers is because until PC-BSD came along, there really weren't any actual desktop versions. PC-BSD was the first to tap into that market, and they gained well-deserved name recognition for it, though now it seems they are about to blow it off...which is sad since PC-BSD 11 is only weeks away from being released, and I'm planning to give it a test drive myself.
10 • Korora/Fedora (by kc1di on 2016-08-29 11:20:13 GMT from North America)
I Tried Korora and Fedora when the newest were released, found the to be capable and good distros, but I don't care for the quick release cycle. I know they have an upgrade option but have never had much success with that. If they would opt for a stable branch for those of us who like it that way I would most likely us it. Some have suggested using centos instead but that is not really designedfor desktop use and is too much work to make it work, just my 2 cents worth :)
11 • PC-BSD > TrueOS (by Anamezon on 2016-08-29 11:36:32 GMT from Europe)
IMHO (and it seems by the comments so far I am not the only one thinking this) quite an unfortunate change - with "PC-BSD" it was so easy to comprehend what OS it is and what is the target system, while these True/Perfect/Ultimate/Top/(insert similar here) boasts always had me thinking "yeah, right! I'll drop my good-working but still-fake/ordinary OS for the sake of some marketing idiot somewhere" ... please come to your senses and reverse this renaming decision, and trust me - "TrueOS ...gives us a more catchy name" couldn't be further from the truth!!!
12 • @10 Upgrading Korora (by Hoos on 2016-08-29 12:02:03 GMT from Asia)
I have upgraded my Korora installation from 21 to 22, then 22 to 23 without any issue, following the instructions on the Korora website.
I will be upgrading to ver 24 soon when 23 is closer to its end of life date, namely around Oct 2016.
13 • PC-BSD > TrueOS (by starskeptic on 2016-08-29 12:33:35 GMT from North America)
e ludolf @8
"Please read the website they clearly explain everything."
where exactly - the site says nothing...
14 • PC-BSD (by Scrumtime on 2016-08-29 12:41:44 GMT from North America)
Don't like that name change at all.. PC-BSD was clear and straight to the point True OS could be anything !!!
Always bothers me when people title something or quote something as being True or Honest..as it usually isnt....
Korora ... I keep trying it and always seem to get problems ....though it does seem to improve maybe ill give it another go after jessies review...
Sad to hear of the passing of Jonathan "avenj" Portnoy from the Gentoo fold....
15 • PC-BSD to TrueOS (by G Savage on 2016-08-29 13:43:08 GMT from North America)
That's asinine. This was the fastest OS I ever ran, It ran so fast I thought I broke the machine. I drive stick, I prefer bolt actions, I like total control over everything that goes on in my machines. BSD does that. And PC-BSD rhymes - it's a marketers dream. Why would they throw that away?
16 • Software Licenses (by cykodrone on 2016-08-29 13:56:10 GMT from North America)
Licenses are not an issue with me, but the reputation of the corporation backing the software is. If they're known for predatory behaviour or spyware, I will NOT use the software.
17 • TrueOS is a 64-bit OS (by David Walser on 2016-08-29 14:09:33 GMT from North America)
I just hope that Hewlett Compaqard doesn't object to their Tru(e) naming of their 64-bit UNIX OS...
18 • Package License Information (by John Doe on 2016-08-29 14:19:12 GMT from Asia)
Another way to quickly determine whether a software package is licensed under a Free Software license or a proprietary one is by quering it's repo info:
In Debian, packages fall under three sections: main, contrib and non-free.
main: Free Software only;
contrib: Free Software that has dependencies on proprietary software, and software which has some issues with it's license;
non-free: Proprietary software only.
In Ubuntu, packages fall under four sections:
main & universe: Free Software only;
restricted & multiverse: Free Software with dependencies on proprietary software, software with licensing issues and completely proprietary software packages.
19 • Dropping "PC" from distro names is only a good thing (by zhaich on 2016-08-29 14:28:21 GMT from North America)
I'm the exact opposite of course. Never liked the name PC-BSD, just as how I feel PCLinuxOS is one of the worst names for a distro I've ever come across. If you're gonna name something, at least put some creativity into it. "BSDComputerOS" doesn't cut it. Having to brand every BSD OS with "BSD" at the end just to say "We're not Linux!" is a convention that I feel needs to die. True OS is okay, it markets their server OS which was less noticeable than before, but I do agree that not tying the former name with the new is marketing failure. However, considering the PC-BSD site hasn't been updated yet, this marketing probably hasn't rolled out yet.
It's also clear they want to make use of their server OS more often, which might be a bit worrying for their desktop users.
20 • Package licensing (by Andy Mender on 2016-08-29 14:33:12 GMT from Europe)
Arch Linux and derivatives also have a "nonfree" repository, which is enabled by default, but can easily be disabled by the user :).
I think a non-free repo should be available too all distributions on install. Toggling it ON would of course trigger an inquiry from the user, whether he/she agrees with the licensing restrictions. However, forcing the user to go through some gimmicks post-install is a no-go to me.
21 • Licences (by a on 2016-08-29 15:09:33 GMT from Europe)
Well hard to answer this poll (again). I care about licences: I will not use proprietary communication software for security reasons. But for the rest, I don’t care.
22 • PC-BSD (by win2linconvert on 2016-08-29 15:11:00 GMT from North America)
I agree the PC-BSD name chance is a bad idea. If a name change is absolutely necessary, just add OS. True OS is a non starter. PC-BSD or PC-BSD OS are more catchy, and accurately descriptive. Just my humble opinion.
23 • TrueOS (by hce.humphrey.chimpden.earwicke on 2016-08-29 15:23:54 GMT from North America)
Reminds me of when DEC renamed Digital Unix as Tru64 Unix.
We laughed, and laughed...
It was actually a good product, for its time, but not many folks took it seriously after the name change.
24 • TrueOS? (by Andy Mender on 2016-08-29 15:35:50 GMT from Europe)
Reading through various comments I'm starting to have doubts whether "TrueOS" is a good software product name even for a server operating system. Unlike "PC-BSD", TrueOS doesn't say anything about the product and feels like making too much of a statement. An alternative to "PC-BSD" could've been "SERVER-BSD" or something similar. To balance it against the PC-BSD name, but not sound too corny.
Having a look at American day to day products helps. The names usually mean something and have a lot to do with the use of the product. For instance, "Poo Away" kitty litter, "Glide" dish washing liquid, etc.
25 • TrueOS (by Andrew on 2016-08-29 15:44:58 GMT from Europe)
PC-BSD was not a very good name but "True" OS is ridiculous, it sounds like bad cheap marketing for some scam product.
26 • PC-BSD → TrueOS, cont’d (by SuperOscar on 2016-08-29 16:31:01 GMT from Europe)
> "Please read the website they clearly explain everything."
> where exactly - the site says nothing...
My point exactly. No doubt there might be something down there somewhere deep, but at least the front pages of both the old and the new site didn’t even whisper of what’s going on.
27 • Naming, licenses... (by Vukota on 2016-08-29 17:01:11 GMT from Europe)
I couldn't agree more. Microsoft experimented at the time with "code" names (probably as their PR folks were bored with regular brand names) and learned through debacle that it was a worst thing they ever tried (now they do it only until the release as it sticks well with geeks that jumps the ship first).
28 • Name Change (by Jose on 2016-08-29 17:19:09 GMT from North America)
I liked the name PC-BSD. I always thought of BSD as strictly a server OS. PC-BSD makes it clear, this one is for PC's!
Likewise, PCLinuxOS tells everyone, this distro is tuned for PC's.
TrueOS sounds like Troll bait. MAC/Windows users are going to say it's their OS that is the one and only TrueOS.
29 • PC-BSD -> TrueOS (-> TrueBSD) (by Svajunas on 2016-08-29 18:17:19 GMT from Europe)
TrueOS sounds terrible, couse it's not informative name! TrueBSD (or smthg?) I think is better choice...
30 • Learn More button (by Doug on 2016-08-29 19:40:55 GMT from North America)
@26 The learn more button isn't deep at all.
I looked at TrueOS.org to see if there was any info on the name change, saw a "Learn More" button, right on the front page.
As for the licensing, I just want my pc to work and be able to do stuff, so I voted the last option.
31 • License? (by Alexi on 2016-08-29 20:11:21 GMT from Europe)
I rarely factor in the license in my consideration. I don't like licenses. I also don't like autoplaying video ads too, the ones Distrowatch has.,
32 • PC-BSD (by Justin on 2016-08-29 20:16:51 GMT from North America)
I'll jump on the bandwagon. While all the BSD names seem a little too similar/much for me (like the K applications from KDE), at least it was functional. I liked the idea of SERVER-BSD. TrueBSD isn't bad either.
TrueOS sounds gimmicky and sets yourself up to be a joke. I remember similar marketing stuff from my earlier days for low-level features. It became the butt of many jokes because the name implied it was way better than it really was. I hope this doesn't end up that way.
PCLinuxOS is a mouthful and I always mixed it up with Linux PC OS. That one needs a rename as well.
33 • poll (by Jordan on 2016-08-29 20:35:03 GMT from North America)
Licenses? We don't need to $%^&*^! licenses. (countdown to post removal)
34 • PC-BSD (by M.Z. on 2016-08-29 21:18:48 GMT from North America)
I have to agree with the general consensus on the name change for PC-BSD. The name PC-BSD has a lot of virtues, it's simple, straight forward, and genuine/authentic (& like #15 said the fact that it rhymes is a big plus). TrueOS could mean anything & I tend to agree with those that said it sounds gimmicky. If I had to pick a name for their project I would definitely stick with PC-BSD for the desktop & perhaps True-BSD or iX-BSD for the server. Or maybe System-BSD or Sys-BSD for the end part of iXSystems. At any rate I think there are a lot of other good options for names, but the one they planed seems like a bad idea to me.
I always liked the current name from the first time I ran across it here of DW several years back. I've tried it a few times since version PC-BSD 7.1, but could never find hardware that it liked.
Us PCLinuxOS users also call it PCLOS (I pronounce it P.C. low-ce). I rather like PCLinuxOS/PCLOS as a name, though it is certainly a bit more cumbersome than PC-BSD. Given how long PCLOS has been building their solid reputation I think losing that name would be bad, though not as as bad as the PC-BSD name change.
35 • What's all that PC-BSD/TrueOS stuff all about, anyway? (by Carlos on 2016-08-29 21:41:56 GMT from Europe)
36 • TrueOs@4@8 (by gee7 on 2016-08-29 22:25:43 GMT from Europe)
> "Please read the website they clearly explain everything."
> where exactly - the site says nothing...
The information on the name change is at:
It is not on the Main page (Home page) of the web site probably because they wanted to keep the main page clean and clear of excess verbiage, but the link to "more-on-trueos" is there at the top of the Home page.
37 • FreeBSD (by Bill on 2016-08-30 00:36:14 GMT from North America)
Call it what you like. Changing the name will not get more people interested in BSD. Grub issues have always been it's major nemesis. Tried on three different computers, but could never get it to even begin an install process. There is some good things that BSD is capable of but unless people can do an easy install it will not get anywhere in the top of Open Source Software Systems. For those who like the unix type of OS, there will always be some avid followers, but will there be enough followers to keep it going?
Just my two-bits.
38 • BSDs (by M.Z. on 2016-08-30 02:09:25 GMT from North America)
DesktopBSD is not a particularly good suggestion, it was already an actual project & died several years back.
I certainly agree that there are problems with BSD on the desktop & I've had lots of hardware problems that have kept me from using BSD there. That being said the BSDs are fairly successful open source projects in their own right & I have had a great deal of luck with other BSD based OSs like the FreeBSD based pfSense firewall distro. I've generally found it to be extremely stable & robust and have very few issues with it. To my recollection I only ever had on significant issue with the OS directly & that was due so some unusual old hardware.
At any rate I've had lots of troubles with BSD on the desktop & lots of luck with it as a firewall. To my understanding the FreeBSD foundation had been doing very well for it's self over the past few years and takes in hundreds of thousands of US $s per year and BSDs are still the backbone of lots of major websites like Netflix. It may be some time before BSDs do as well on the desktop as Linux, but there is a big future there & FreeBSD in particular will be around for a long time to come.
PS they already raised over $250k this year:
39 • BSD, BFD (by imnotrich on 2016-08-30 04:24:02 GMT from North America)
Why not just call is Desktop-BFD or Server-BFD and be done with it?
40 • PCBSD (by billc on 2016-08-30 04:48:07 GMT from Oceania)
I agree with most of the above, I don't like the name change.
This is not the first questionable decision made by the PCBSD developers - the dropping of the Warden (GUI for Jails management) was equally crazy.
Still it is an amazing OS with incredible tools and the awesome ZFS. Well worth watching. Still a bit rough around the edges but it could be a very strong alternative to Linux on the desktop in the near future.
41 • PC-BSD and FreeBSD (by AndyMender on 2016-08-30 07:25:26 GMT from Europe)
The main reason is probably that FreeBSD is not desktop-oriented in the sense people understand what a desktop computer really is. It has some super powerful features, works great even without X11 and handles network traffic with grace. It can be made to work as a GUI-driven OS, requiring a similar level of expertise as Arch Linux or perhaps Devuan. On laptops it's much easier with all-Intel hardware - at most a 4th gen processor (core i + Intel HD Graphics up to 4400). The current limitation is Intel and ATI/AMD iGPU support and wireless.
PC-BSD plays a pivotal role in lowering the boundary for less computer-savvy people to accept BSD :). Whether it's "true" or not, the "PC" in the name is crucial.
42 • TrueOS vs PC-BSD (by Koroshiya Itchy on 2016-08-30 08:56:55 GMT from Europe)
Desktop computers (PCs) are less relevant now than they were a few years ago and they are getting less and less relevant every year, fast and steadily. This is not to say that they are going to disappear any time soon, as some people used to claim, but they are no longer the largest market. The market right now is on the mobile devices and therefore if you want to make your living out of developing an OS you better make sure it is well positioned to jump into that market. You can, of course, use the desktop to promote your OS, as Canonical tried to do (late and clumsily), but that is not THE market any more.
This is to say that PC-BSD is no longer a good name. I do not know if TrueOS is, but you do not want to have "PC" or "desktop" on the name of your OS.
43 • @38 (by JJ on 2016-08-30 14:36:45 GMT from North America)
I'm glad to hear the FreeBSD foundation is doing well. While that seems like a lot of money, in a way that isn't. That will pay for maybe 2-4 developers full time, really less when they have to cover infrastructure costs. They can get more people by paying "bonuses" for working on the project.
I'm happy for choice, and I'm glad people are working on BSDs.
44 • TrueOS (by aary on 2016-08-30 14:59:50 GMT from Asia)
Isn't PC BSD too straight ball?
No problem with the new name TrueOS. It sounds cool for me.
I would love to run it, if it will allow my hardware :P
45 • Desktops less relevant? (by Andy Mender on 2016-08-30 15:23:03 GMT from Europe)
I wouldn't say desktop computers are becoming irrelevant quickly. I think they still have a significant presence in various money-making quarters like game development or as computing workstations in sciences and company offices. They're not relevant for mobile computing, true. That's sort of obvious, though, with the sharp improvement of tablets and smartphones in terms of both software and hardware. However, having a stable, long-term job and an apartment, a desktop tower + smartphone is the combo to go for. Most of the mobile stuff you can do on your smartphone, while a solid desktop is a must-have if you want to store any kind of data and do some actual computer work at home.
46 • Desktops (by curious on 2016-08-30 15:31:54 GMT from Europe)
And don't forget that from a user interface perspective, notebooks (especially the larger ones) are also desktops. They are still very relevant for professional users.
47 • BSD or whatever (by David on 2016-08-30 16:59:51 GMT from Europe)
A quick check shows 1-2% of webservers using BSD (according to whom you ask), while at Stack Overflow the percentage of BSD users was too small to show up in the survey. So, does it really matter what you call BSD? EndangeredOS, perhaps?
48 • Renaming BSD (by Greycoat on 2016-08-30 17:20:24 GMT from North America)
@47 - Maybe they should call it Ball-Less BSD since it's based on Eunuchs. :)
Seriously, I like PC-BSD more than TrueOS.
49 • TrueOS: Not just a name change (by Ken Moore on 2016-08-30 21:00:48 GMT from North America)
Distrowatch jumped the gun on announcing TrueOS - but they are also wrong by declaring it *just* a rename of PC-BSD. TrueOS is the next evolution of the PC-BSD project and an official announcement of it is scheduled for later this week.
*spoilers*: There is a *lot* that is different!!
~~ PC-BSD & TrueOS developer
50 • @ 49 • TrueOS: Not just a name change by Ken Moore (by Alexi on 2016-08-30 21:31:10 GMT from Europe)
If yours is THE TrueOS, then what are the others here? Non-True OSs? Or Untruthful OSs, Ken?
51 • software licenses (by argent on 2016-08-30 22:40:41 GMT from North America)
Always use the bare minimum of software to get the job done, agree with #16 cykodrone regarding compromised software.
Concerning non-free in particular, this is where donating plays a most important role. Someone is paying for the non-free, donations helps sustain and promote it's developement.
52 • PC-BSD new name and new future (by TUXBSDSOLARISUSER on 2016-08-30 23:26:38 GMT from North America)
The PC-BSD name change has been discussion since last 2 years on the forum.
With such as name, the challenge is big. I hope that future releases will match with the new BIG name TrueOS. Imagine a new Distro called: THE ONE OS !!!! WOW Imagine the sarcasm of every competitor in case of failure.
Since the release of version 10, there has been much change at several levels in PC-BSD. The Lumina came, the complete overhaul of AppCafe, adding several small system utility. The installation system has also been modified and improved. All these changes came with lot of instability on desktop user experience. Many, many, many instability oh my god.
The website change from Joomla to Wordpress, the forums redesign etc ... I must say not always for the better. Sometimens hard to follow...
I think, PC-BSD was more change in the last two years than in all existence of PC-BSD.
Version 10 of PC-BSD has been one of change with what it brings in instability. In my book the user experience on Desktop has been the worst of all versions.
Maybe the team want clean the table and start a new fresh name in version 11.
Many hard work development has been done and it will bring happiness users verison 11.
I hope more stability.....
this is just my opinion
53 • Marketspeak Autobot Translator (by Arch Watcher 402563 on 2016-08-31 00:48:55 GMT from North America)
What a boatload of comments rebranding inspired. I doubt there are five PC-BSD users here. I have installed it a few times.
What's more interesting about the project is the Lumina desktop, LibreSSL, absence of system D-, and PersonaCrypt.
Where TrueOS loses me is conjoining "Safe and Secure" claims with "SysAdm™ Remote Management." I hope SARM has an off switch.
FreeBSD I call KernelGeekOS because you get new kernel featurettes today, your next app version mañana. FreeBSD news covers kernel and filesystems to the nth degree. It reads like LKML. There's nada on improvements to packaging speed and efficiency for upstream apps. You would think clang might have helped. I can't even find a chart of which ports BSD considers out of date with upstream. If Ken or anyone else forks FreeBSD with a buildbot.net farm to front-run ports with upstream version tracking that works, I will move in.
54 • BSD future (by M.Z. on 2016-08-31 07:10:46 GMT from North America)
@haters (mostly #47)
If you dig into the profit & loss statements for the past 2 years (or just look @ the bottom of page 3 of the pdfs) the FreeBSD foundation lost $312k in 2015, but made a net of over 1.6 million US $s in 2014. If they can generate income anywhere near that & do basic housekeeping/budgeting it seems to me that anyone who thinks BSDs will all disappear anytime soon is totally clueless. Their current goal of $1.25 million seems lofty, but again net income from a couple years earlier was even higher & regardless of whether they make that goal or not they seem to have a good deal of resources.
I would like to see it do better on my desktop hardware, but I'm keeping BSD for a firewall OS & I'm confident that I will have the option to do so for years to come.
55 • FreeBSD and BSD future (by Andy Mender on 2016-08-31 10:15:39 GMT from Europe)
FreeBSD offers many ports and tries to track what upstream projects are doing. This is mostly an automated process. Of course, from time to time intervention on the part of the maintainer(s) is required. This is handled deftly with the Bugzilla system in the form of Problem Reports.
One may claim that many ports are not maintained by FreeBSD developers, but seriously how many of them are not even maintained upstream? For instance, I use Window Maker as my day-to-day window manager/desktop environment. Its development halted years ago and it's flagged in the FreeBSD ports tree as lacking maintainers. However, since it still builds on the build farms and the interest of hackers is negligible, it's fine. Contrary, how many GNU/Linux distributions inform the user directly (for instance, via repositories) that a specific program/library is not maintained anymore?
I believe infrastructure organization is one of the strong points of both FreeBSD and PC-BSD/TrueOS, and for that matter they're a great example to learn from :).
56 • BSD (by Scrumtime on 2016-08-31 11:44:07 GMT from North America)
I Dont think most people are PC- BSD or Any BSD haters just that the name change made little sense, that coupled with the fact that most people can't get BSD to work.......I know i tried many times it was one of the first Unix type OSs that i tried many moons ago
Personally PC-BSD never worked then it suddenly dropped 32bit distros when i was starting to make ground with it on a 32bit machine....never really tried it more than a couple of times on a 64bit but still had same problems..
Ghost BSD on the other hand has been a lot easier to work with..
we had a BSD server which worked great though...
57 • BSD (by Andy Mender on 2016-08-31 12:32:40 GMT from Europe)
I think BSDs require some getting used to, much like the simpler GNU/Linux distributions :). There are similarities with CRUX, Arch Linux, Slackware and Devuan/Debian in terms of software management and process supervision, though of course many differences also.
Per personal experience, my initial trials with FreeBSD were largely unsuccessful. I couldn't even get it to boot from a USB stick on a relatively standard 32-bit desktop. With 10.3-RELEASE many improvements came about. Nowadays, it's fairly trivial to make it boot even on UEFI-based netbooks.
Of course, this is mainly a GNU/Linux community so I expect people to have doubts, issues or feel reluctant towards BSDs :).
58 • the value of BSDs (by M.Z. on 2016-08-31 19:52:27 GMT from North America)
If you look at the context I was addressing the negativity of comments like #47 that implied that BSDs don't matter &/or are doomed to disappear due to small market share. I don't like the name change either & I've been frustrated by desktop oriented BSDs due to bad hardware support myself; however, the BSD projects are still very useful & I expect them to be around a good long while because of it.
I do admit that my main direct use of BSD is a firewall with pfSense, but then I rather like the idea that I have a FreeBSD based firewall OS shielding my Linux machines/LAN. I feel that having a different OS with a different security profile adds real value to my personal security setup on my computers. I personally find the BSDs to be very valuable & rely on them everyday both personally via pfSense & via streaming from Netflix.
Of course millions of people stream video from the BSD based servers at Netflix everyday, so on the basis of streaming video content alone BSDs are very important. In fact given the volume of data streamed by Netflix I'd guess the BSDs move huge amounts of data across the web everyday & are pushing a far larger % of the data on the web than the clueless negative types that think BSD will disappear could ever imagine.
59 • PC-BSD (by Alexi on 2016-08-31 20:25:06 GMT from Europe)
PC-BSD was a known distro.
But, once it becomes the TrueOS, some other dev would be releasing the OnlyTrueOS, another the AbsolutelyTrue OS, another the TrulyTrueOS...
60 • BSD moves 1/3 of all data across the web (by M.Z. on 2016-08-31 21:05:51 GMT from North America)
To those saying BSD does nothing I found a couple of articles on Ars Technica that say that BSD moves at least 1/3 of all data across the Internet during peak data usage hours. That is at least if you can read between the lines of what they say about Netflix. An article from 2015 confirms that Netflix uses BSD for all their 'OCA' streaming servers & another from 2014 shows that Netflix is responsible for 9.5% of uploads & over 1/3 of all downloads in North America during peak data usage hours.
And the second paragraph here:
61 • Dam Upstream, Blame Dry Riverbed on Climate Change (by Arch Watcher 402563 on 2016-09-01 03:32:44 GMT from North America)
@55 Andy Mender
I like FreeBSD. I have no problems using it as a server. I want it for my desktop. I've said so many times here.
The remark "many ports...are not even maintained upstream" is highly misleading. So misleading, I am thinking WTF, is this the FreeBSD party line?
It isn't a question of a lazy upstream. What I see all the time is an upstream project released a fresh stable version already, but FreeBSD still offers the one from two years back, and you must wait forever to see it bumped a minor increment. If you have a URL for my desired chart of stale ports, by all means post it.
Arch Linux lets one click a package page to flag its shipping Arch version out of date. I cannot believe FreeBSD needs a Bugzilla to handle such simple notice.
I myself remain puzzled why all the fine infrastructure, the tortuous shift to clang, and many people involved with FreeBSD do not understand this problem. I suspect they are all running MacOS desktops and FreeBSD servers.
Release notes for Linux distros tend to say "We've updated LibreOffice to version X.Y.Z and mpv got a boost to version A.B.C." Equivalent FreeBSD notes trumpet that "The kernel now has a flag IF_GOOF_THEN_TWERK and our scheduler was redesigned from scratch while we fiddled with compiler intermediate code." There is nada information on what ports got an update.
I have watched desktop packages expecting a maintainter to ship the latest stable upstream version, then watched a few months more, then asked, only to be told, I'll see when I can get around to it. FreeBSD is unholy that way. I think any package more than 6 months out of date needs an automatic red flashing light to dance on the FreeBSD foundation's desk.
62 • @61 (by Andy Mender on 2016-09-01 08:04:03 GMT from Europe)
1. How is saying "many ports are not even maintained upstream" misleading? This is a generalization, which has no deeper meaning. It just means that some projects were abandoned upstream, nothing more. It's not a "party line" of any sort.
2. "FreeBSD still offers the one from two years back". Which programs do you mean specifically? I haven't noticed a single port that's 2 years behind GNU/Linux distros. The programs I typically use are perfectly up to date. Also, here is a list of ports without an official maintainer: http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports%40FreeBSD.org. They still get updated properly as long as no breaking changes were introduced upstream and the ports still build.
3. Bugzilla is used to report issues with ports or claim maintainership of a port.
4. Clang vs GCC is a "red herring", you know? Some binaries run faster, some slower. There is not a single "across the board" proof that Clang is bad as a compiler. If that's the case, why would anyone use it then?
5. Be aware that in FreeBSD ports and the base system are separated. Therefore, most news per system updates will be about the core utilities, the kernel, etc. On the other hand, how is version bumping in GNU/Linux distros informative? What does "we've updated Firefox to version X.Y.Z" really tell you?
I would rather read about distro-specific infrastructures that were introduced to make users' lives easier.
6. Again, which specific packages do you find to be out-of-date and you simply cannot live without them being the most current release?
Many people, me included, use FreeBSD as a desktop operating system successfully. Not sure what do you expect from FreeBSD so that it would satisfy your vision of a desktop operating system, which has not been touched by GhostBSD or PC-BSD/TrueOS already.
63 • @62 (by billc on 2016-09-01 09:31:05 GMT from Oceania)
Some people cannot be helped, Andy. I thought of responding to @61 but I would not have been as tactful as you.
Arch Watcher, are you having a bad day? Most of your comments in previous weeks have been so sensible and worth reading. Why suddenly the FreeBSD hate? If you want it for your desktop so much then why not join the team and help instead of just ranting?
btw GhostBSD 10.3 is awesome.
64 • @ 59 • PC-BSD -- Trueos (by Len on 2016-09-01 09:31:59 GMT from Africa)
What would be the TruestOS in the Distrowatch's Hit list? Mint, Debian, Ubuntu or OpenSuse, or maybe Fedora and RedHat?
65 • Deadwood in the Riverbed (by Arch Watcher 402563 on 2016-09-01 09:44:42 GMT from North America)
It's misleading as an excuse for FreeBSD to allow stale ports for apps alive and well upstream. Abandoned projects shouldn't exist in a well-maintained source tree. Such deadwood just enlarges my critique of ports.
What "we've updated Firefox to version X.Y.Z" really tells me is that the distro cares about desktop apps.
Ports and base aren't separated. They are more integrated than for Linux equivalents. That's even a BSD marketing bullet, namely, overall integration. If you mean that BSD org honchos don't pay much attention to actual ports, I agree, and that's the problem.
Look, I don't want a dust storm, but must we "prove" easy homework. Contrast FreshPorts.org with any upstream official release.
LibreOffice on FreeBSD is now sitting at version 5.0.6, behind BOTH "fresh" and "still" upstream. I can have the current "fresh" 5.2 on Gentoo, Void, Manjaro, Alpine, etc. Upstream 5.1 shipped half a year ago (Feb 2016). So 5.0.6 is officially half a year stale. Of course FreshPorts.org does not tell you so. Arch Linux shows red-letter text saying "out of date" when that's the status.
RetroShare took maybe half to a full year for the maintainer to act on upstream stable release 0.6.X. The major new stuff in 0.6 even included more help for BSD builds. It should have been easier for him than 0.5.
I could go on.
I am not saying anything about clang. I am saying FreeBSD did a major tooling overhaul instead of getting its maintainers in line. It's how FreeBSD rolls: kernel hacking, compilers, filesystems, server infrastructure, firewalls, throughput studies, conferences, etc. Apps are an afterthought left to maintainer discretion. My dashed hope was that clang would somehow benefit app updates.
Apparently, according to you, then given commit privs, I can even post an abandoned dead project from some lost upstream to ports, and no one will discipline me or even ask questions. The BSD kernel gets treated with far more respect.
66 • My Meds Are All Current (by Arch Watcher 402563 on 2016-09-01 10:17:34 GMT from North America)
Dear billc, thank you for the concern but no, not today.
I had a bad day when for no good reason, FreeBSD 9 failed to boot a stock PC that was then ten years old. So I waited for the next big release and kept taking my meds.
The next big release booted. But I had another bad day realizing how out-of-date its desktop software would be. Debian flashbacks gave me seizures so I switched my meds to a Linux distro that keeps apps current. Then my bad days stopped. I could sleep again.
Until the distro forced System D- medicine on me. After that caused seizures and insomnia, I switched to Linux distros that use less dangerous chemicals. Then my bad days stopped once more, and I found calm again.
Do I today read FreshPorts correctly, that KDE on FreeBSD is still version 4, two years after KDE 5 shipped? Save me, I'm drowning in proofs. Oh the flashbacks, oh they hurt...
Call me for the apocalypse, BSD ports might be current by then.
67 • @66 (by billc on 2016-09-01 11:17:45 GMT from Oceania)
"My Meds Are All Current" - Good to hear, LOL. Personally I will put up with a 6-month old word processor if it is on top of the stability and security of FreeBSD. Remember that FreeBSD gives us incredible technologies such as jails and the ZFS.
You could also edit the port so that it downloads a more current version of the software you want. That might not work with LibreOffice as it is so big and complex but it will often work with other packages.
Like you I am allergic to systemd. I am a long-time Slackware, BSD and Gentoo user but I keep an eye on Void and Alpine. I like Manjaro but I don't like the petty bickering that goes on in Arch.
68 • BSD (by Koroshiya Itchy on 2016-09-01 15:20:50 GMT from Europe)
A problem with BSD, be it on the workstation or the server, it is its inability to profit from CUDA GPU accelerators.
69 • OpenOffice vs LibreOffice (by James Glaser on 2016-09-01 19:16:09 GMT from North America)
My choice of OO due mostly to the Apache licence.
70 • Windows-only RemixOS (by OstroL on 2016-09-01 20:01:18 GMT from Europe)
Don't know, whether this is the first time Distrowatch is giving links to a "distro" that only works with Windows. But now that Distrowatch had done that, you'd want to download it and try it. If you guys are those, who use Linux only, you have a problem of checking it out. Have a look here to find out how to try it out.
http://distrowatch.com/weekly.php?issue=20160822&mode=67 post 97
Distrowatch should've first try the distro out in its Linux-only computers, before anouncing the Windows-only "distro" in its home page. Now, we might even have a "hit-ranking" for a Windows-only "distro."
71 • Remix OS (by Jesse on 2016-09-01 20:33:21 GMT from North America)
>> "Don't know, whether this is the first time Distrowatch is giving links to a "distro" that only works with Windows. But now that Distrowatch had done that, you'd want to download it and try it."
I am not sure where someone would get such a strange idea. I did run Remix OS, downloading it and setting it up from my Linux-only workstation. That's how I got software and screen shot information. There is nothing Windows-only about Remix OS, anyone running a Linux-only environment can run Remix OS.
I try all new operating systems I add to the database, including Remix OS and I always do so from a pure Linux environment.
72 • @71 Jessie (by OstroL on 2016-09-01 20:55:17 GMT from Europe)
Tell us how you set it up in your Linux-only workstation?
Remix OS Installation Tool works only in Windows, so how did you start the .exe file in your Linux-only workstation?
73 • Remix OS (by Jesse on 2016-09-01 21:40:17 GMT from North America)
>> "Remix OS Installation Tool works only in Windows, so how did you start the .exe file in your Linux-only workstation?"
You don't run the .exe when you're installing from Linux. It's not needed. There are two ways to install Remix OS from Linux. The USB-drive option is decribed in the Remix OS documentation. To install to a hard drive instead, you can create a FAT partition, mount the Remix ISO file and copy the contents of the ISO to the new partition. You may need to run GRUB's update script (or manually add a GRUB entry for Remix). Then reboot.
I suspect the reason there is an .exe launcher is because Windows users do not have the same partitioning and boot loader tools Linux users usually have pre-installed. It's not because Remix is Windows-only,
74 • @ 73 • Remix OS by Jesse (by Alexi on 2016-09-01 21:56:14 GMT from Europe)
Oh, so read the read me file. It took sometime for you to reply. So, you created a FAT partition on your Linux-only workstation and installed it the way the Remix OS documentation told you. So, how much storage does your Remix OS has in your FAT partition? 8GB or more?
That guy gave a how-to last week. There are many ways to install Remix OS on a Linux-only computer. You can install it in your Ubuntu root. But, just by mounting the Remix OS iso file and copying the contents of the ISO to the new partition, it won't run. You didn't install RemixOS in your Linux-only workstation. I've used it since the beta days, so I know.
75 • RE: 70 - 74 Remix OS (by lb on 2016-09-01 22:06:26 GMT from Asia)
I have no idea what you guys mean by this "Windows-only", "Linux-only" talk. Remix OS provides a regular ISO image which you burn on a DVD, then you use that DVD to boot up any x86 computer, irrespective of which OS it runs (or whether it runs an OS at all). Just like any of the hundreds of other live Live distributions and operating systems we report on.
Or am I missing something?
76 • Remix (by mandog on 2016-09-02 00:42:15 GMT from South America)
I had it running on my notebook with grub2 it will run on ntfs,fat,ext4 with no problems but it really is not that good android-x86-6.0-rc2.iso is far better and has a dedicated installer
77 • Fedora_25_alpha_with_default_Wayland (by k on 2016-09-02 05:54:01 GMT from North America)
Seems to be for more expert users/developers, and not older hardware?
Installer took an extraordinary time to complete, and then final result would
not startup beyond user login. Lucky to have stable Debian on separate disk
in same machine, cleared away all the "debris" from that "learning experience".
The installer does start from Fedora's usual warning about the release being
really infested with "bugs", so other beginners beware. :)
78 • @75 Am I missing something? (by Alex on 2016-09-02 06:52:22 GMT from Europe)
Yes, you are.
Jessie "installed" this Remix OS to a usb stick. Then, he started it in the guest mode. That's how the "screenshot" came by. https://distrowatch.com/images/slinks/remixos.png and here is the screnshot of Jessie's screenshot https://s15.postimg.io/4wd9ksizt/Screenshot_11.png
You may notice the words Guest Mode on the top right corner.
When asked how he "set it up in his Linux-only workstation," Jessie became evasive. He knows that we know he didn't install it. Aha, btw it won't install into a DVD, because it has to create the 'data' folder, but maybe you might try with a rewritable DVD.
79 • RE: 78 Remix OS (by ladislav on 2016-09-02 09:27:17 GMT from Asia)
I was reacting to comment 70 where the poster talks about Remix OS being "Windows-only". We have also received an email or two accusing us of listing a "Windows-only" system on DistroWatch.
You won't find a single Windows machine anywhere at my place. Yet I was able to boot Remix OS, use it, install applications, take a screenshot. You can even become root and do whatever you want with it.
So if there is any other post saying that Remix OS is a "Windows-only" system, then his/her post will quickly find itself in /dev/null. It's just complete rubbish.
80 • @78 top left corner not right corner (by Jordan on 2016-09-02 15:01:47 GMT from North America)
No big deal but what's missing is giving a crap about this "Windows only" huff contest.
81 • Remix OS (by Jesse on 2016-09-02 16:34:21 GMT from North America)
>> "When asked how he "set it up in his Linux-only workstation," Jessie became evasive. He knows that we know he didn't install it."
@78: I didn't become evasive, I clearly answered all the question you asked. I don't know what else you really expect. I mean, do you want a step-by-step guide on how to install Remix OS from a Linux system? If so there are plenty of guides out there. And, despite your claims, I have installed Remix OS to a hard drive. The screen shot was from a live USB device, but I also put Remix OS on a hard drive too to confirm it can be done.
If you want to e-mail me, I'll even send you the steps I took to install Remix OS on a drive, pulled from my bash history file. Maybe then you'll stop making baseless claims about the distribution?
82 • Apache OpenOffice (by M.Z. on 2016-09-02 17:31:28 GMT from North America)
I actually prefer the OpenOffice name (just as a subjective like the way it sounds sort of thing) & think it still has good name recognition & branding, but the project has been troubled for a long time now. Even if you just look at the amount of releases you can tell that AOO has been falling behind LibreOffice for some time & some in the project are even questioning whether the project has a future.
Here are some grizzly details a ran into today:
I think its fairly sad as the old pre-Oracle OpenOffice helped me & I imagine many others see a world without propriety software as a serious possibility. At some point after switching to OpenOffice & Firefox & developing a certain affection for what such projects were doing I started looking into Linux & other open OS alternatives. I installed my first copy of Mint in 2008 & ditched Windows for PCLinuxOS completely 3 years later. Of course that may not have happened for me if I hadn't had such a positive experience with OpenOffice & other open source projects first.
83 • @82 (by billc on 2016-09-02 19:45:32 GMT from Oceania)
The problem is that Oracle is far less friendly towards open source than was Sun Microsystems. Recall that Oracle "acquired" Sun after the GFC. Sun had developed Solaris, Java, OpenOffice and MySQL - all four have since been forked by the open source community, not trusting Oracle, to become OpenIndiana, OpenJDK, LibreOffice and MariaDB respectively.
84 • Devuan (by Koroshiya Itchy on 2016-09-03 12:03:08 GMT from Europe)
After being a Debian user for many years, I migrated to Lubuntu 14.04 when Debian imposed systemd upon us offering no alternative. This week I decided to give Devuan 1.0-beta a try on my old Lenovo S10-3s netbook (RAM upgraded to 2GB and SSD). I used the netinstall image in non-graphical expert mode. The installation experience has not changed since Debian 7. This enabled me to choose a non-PAE 586 kernel of the 3 series. I have also activated the backports, which resulted in the kernel being updated to 4.6.0 686, which, I believe, it is also non-PAE. I installed LXDE instead of the default XFCE.
The desktop experience is clearly better with Lubuntu.Devuan, as Debian, does not configure the DE for you. Using lxappearance was flawless in Lubuntu but has glitches in Devuan/Debian and you need to log out for certain changes to take effect. The Synaptics touchpad did not work well with Lubuntu but it is somehow worse in Devuan and requires manual configuration in both cases.
Other than that, Devuan feels a lot crispier than Lubuntu. It boots faster (really fast!) and switching it off takes just a couple of seconds. Firefox still feels heavy on this hardware, same as Chromium, but better with Devuan than with Lubuntu (maybe due to the non-PAE kernel?). Opening applications is also faster. The backported version of Midori is very buggy, but QupZilla works just fine.
In summary, so far Devuan seems like a keep for this netbook. I would like to profit to thank the Devuan developers for giving us our freedom back.
85 • Lumina DE, 64-bit only? (by Linux Apocalypsis on 2016-09-04 08:49:10 GMT from Europe)
I have tried to build the Lumina DE in Devuan 32-bit by following the instructions on the Lumina website.
The compilation fails after a long while with a very generic Qt5-related error. Has anyone succeeded compiling this thing in a 32-bit environment.
Number of Comments: 85
Display mode: DWW Only • Comments Only • Both DWW and Comments
|• 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|
|• Issue 716 (2017-06-12): Slackel 7.0, Ubuntu working with GNOME on HiDPI, openSUSE 42.3 using rolling development model, exploring kernel blobs|
|• Issue 715 (2017-06-05): Devuan 1.0.0, answering questions on systemd, Linux Mint plans 18.2 beta, Yunit/Unity 8 ported to Debian|
|• Issue 714 (2017-05-29): Void, enabling Wake-on-LAN, Solus packages KDE, Debian 9 release date, Ubuntu automated bug reports|
|• Issue 713 (2017-05-22): ROSA Fresh R9, Fedora's new networking features, FreeBSD's Quarterly Report, UBports opens app store, Parsix to shut down, SELinux overview|
|• Issue 712 (2017-05-15): NixOS 17.03, Alpha Litebook running elementary OS, Canonical considers going public, Solus improves Bluetooth support|
|• Issue 711 (2017-05-08): 4MLinux 21.0, checking file system fragmentation, new Mint and Haiku features, pfSense roadmap, OpenBSD offers first syspatch updates|
|• Issue 710 (2017-05-01): TrueOS 2017-02-22, Debian ported to RISC-V, Halium to unify mobile GNU/Linux, Anbox runs Android apps on GNU/Linux, using ZFS on the root file system|
|• Issue 709 (2017-04-24): Ubuntu 17.04, Korora testing new software manager, Ubuntu migrates to Wayland, running Nix package manager on alternative distributions|
|• Issue 708 (2017-04-17): Maui Linux 17.03, Snaps run on Fedora, Void adopts Flatpak, running Android apps on GNU/Linux, Debian elects Project Leader|
|• Issue 707 (2017-04-10): PCLinuxOS 2017.03, Canonical stops Unity development, OpenBSD on a Raspberry Pi, setting up a VPN for privacy|
|• Issue 706 (2017-04-03): Super Grub2 Disk, Snap packages of deepin applications, Subgraph OS routes network traffic for one application, announcements from Linux Mint|
|• Issue 705 (2017-03-27): Minimal Linux Live, sharing control of the operating system, new KaOS features, Uplos32 provides 32-bit fork of PCLinuxOS|
|• Issue 704 (2017-03-20): ToarusOS 1.0.4, Linux Mint's security record, Debian starts Project Leader election, Ubuntu 12.04 reaches end-of-life|
|• Issue 703 (2017-03-13): SolydXK 201701, CloudReady, Solus announces new features, KDE Connect sends text messages from desktop, openSUSE's YaST module for Let's Encrypt|
|• Issue 702 (2017-03-06): Fatdog64 Linux, elementary OS bundled with new netbook, Haiku announces new features, security and the size of a distro's development team|
|• Issue 701 (2017-02-27): OBRevenge 2017.02, Mageia 6 delays, NetBSD reproducible builds, questions about swap space, trying to steam video on a Raspberry Pi|
|• Issue 700 (2017-02-20): RaspBSD, Debian replaces Icedove with Thunderbird, Fedora's licensing guidlines, tips for switching shells, finding battery charge, getting IP address and killing processes|
|• Issue 699 (2017-02-13): Clear Linux, GhostBSD network utility ported to FreeBSD, Ubuntu coming to Fairphone, elementary OS crowd funding an app store|
|• Issue 698 (2017-02-06): Solus 2017.01.01, comparing containers with portable applicatins, Tails dropping 32-bit support, Debian Stretch enters freeze|
|• Issue 697 (2017-01-30): Subgraph OS 2016.12.30, running Ubuntu on an Android phone, Arch Linux phasing out 32-bit support, Linux Mint testing updated LMDE media|
|• Issue 696 (2017-01-23): GoboLinux 016, remotely running desktop applications, Solus adopting Flatpak, KDE neon using Calamares, TrueOS tests OpenRC|
|• Issue 695 (2017-01-16): Zorin OS 12, Peppermint team fixes installer bug, Debian refreshes Jessie media, Ubuntu improves low graphics mode, Exciting things coming in 2017|
|• Issue 694 (2017-01-09): MX Linux 16, Fedora considers systemd security features, DragonFly BSD to support massive swap space, Ubuntu Touch roadmap, Puppy's newsletter, sudo's password prompt|
|• Issue 693 (2017-01-02): Comparing small distros, fig language, video driver comparsion, Debian+PIXEL, Wayland on FreeBSD|
|• Issue 692 (2016-12-19): Bodhi Linux 4.0.0, Cappsule containers, Calculate's new Utilities package, Solus and Ubuntu MATE build new application menu|
|• Issue 691 (2016-12-12): SalentOS 1.0, openSUSE improves YaST, Fedora considers slower release cycle, KDE neon gets LTS branch|
|• Issue 690 (2016-12-05): Fedora 25, Ubuntu adopts rolling HWE kernel, running Android apps on GNU/Linux, Haiku working toward EFI support|
|• Issue 689 (2016-11-28): openSUSE 42.2, Fedora's upgrade path, plans for Korora 25, transitioning from PC-BSD to TrueOS, Webconverger's reproducible builds|
|• Issue 688 (2016-11-21): Endless OS 3.0.5, KDE neon fixes security hole, FreeBSD's Quarterly Status Report, Rolling release trial #2 concludes|
|• Issue 687 (2016-11-14): NAS4Free 10.3.0.3, Fedora gains MP3 playback, budgie-remix becomes Ubuntu Budgie, Ubuntu flavours compared, Rolling release trial #2|
|• Issue 686 (2016-11-07): FreeBSD 11.0, rolling release trial #2, Debian announces supported architectures, Simplicity switching to antiX base, farewell to Mythbuntu|
|• Issue 685 (2016-10-31): elementary OS 0.4, SUSE gains ARM support, Mint improves language support, Dirty COW explained, Rolling release trial #2|
|• Issue 684 (2016-10-24): Ubuntu 16.10, Linux popularity in different markets, Fedora runs on Raspberry Pi, Ubuntu features live kernel patching|
|• Issue 683 (2016-10-17): Refracta 8.0, making packages for distributions, Alpine switches to LibreSSL, 386BSD website publishes classic code|
|• Issue 682 (2016-10-10): KDE neon 20160915, Android-x86 6.0, Fedora warns of update bug, HandyLinux drops English translation, LXQt benchmarks|
|• Issue 681 (2016-10-03): OpenBSD 6.0, DragonFly BSD to support LibreSSL in ports, systemd denial of service bug, upgraded Mintbox Mini|
|• Issue 680 (2016-09-26): Uruk GNU/Linux 1.0, blocking applications at the firewall, Lenovo controversy, Ubuntu running on the Nextcloud Box|
|• Issue 679 (2016-09-19): OpenMandriva 3.0, 32-bit vs 64-bit performance, openSUSE updates, KaOS unveils first run wizard|
|• Issue 678 (2016-09-12): Apricity 07.2016, Mageia adopts DNF, KDE neon to use Wayland, FreeBSD updates Linux compatibility, creating cron jobs|
|• Issue 677 (2016-09-05): Peppermint OS 7, Manjaro updates leadership, TrueOS becomes rolling release, organizing files, creating torrents|
|• Issue 676 (2016-08-29): Korora 24, Fedora 25 to use Wayland by default, Linux turns 25, PC-BSD becomes TrueOS, finding software licensing information|
|• Issue 675 (2016-08-22): Gentoo LiveDVD "Choice Edition", moreutils, Ubuntu improves terminal convergence, MATE packaged for Openindiana, FreeBSD improves video support|
|• Issue 674 (2016-08-15): Zenwalk Linux 8.0, Ubuntu phone follow-up, Lubuntu transitioning to LXQt, Steam running on FreeBSD|
|• Issue 673 (2016-08-03): noop linux and EasyNAS, Debian's GnuPG switch, Fedora "Flock", using "nice"|
|• Issue 672 (2016-08-01): Ubuntu Phone 15.04, Solus embraces rolling release model, interview with Jane Silber, FreeBSD Quarterly Report|
|• Issue 671 (2016-07-25): Slackware 14.2, Point Linux 3.2, OpenBSD disables usermount, KaOS releases significant changes, Fedora 22 reaches end of life.|
|• Issue 670 (2016-07-18): Linux Lite 3.0, Bodhi team plans 4.0.0, pfSense changes licensing, running software across distributions, Linux Mint upgrade path|
|• Full list of all issues|