 DistroWatch Weekly |
| DistroWatch Weekly, Issue 760, 23 April 2018 |
|
Welcome to this year's 17th issue of DistroWatch Weekly!
When choosing a distribution it is sometimes difficult to find a good balance between cutting edge software and stability. This week we begin with a look at Chakra GNU/Linux which strives to offer both a stable operating system and the latest desktop applications through a semi-rolling release policy. Jesse Smith has more details on the Chakra distribution in our Feature Story. In our News section we talk about Debian's roadmap for Debian 10 "Buster" and the results of the Debian Project Leader election. Plus we report on Netrunner introducing a new ARM-based edition and Slackware initiating a massive rebuild of the venerable distribution's software packages. Plus we talk about Microsoft developing a new operating system based on a modified version of the Linux kernel. In our Questions and Answers column we explore hiding files using a special systemd security feature. As usual, we share the releases of the past week and list the torrents we are seeding. Finally, our Opinion Poll asks whether our readers dual boot or use virtual machines in order to run multiple operating systems on the same computer. We wish you all a fantastic week and happy reading!
Content:
|
| Feature Story (by Jesse Smith) |
Chakra GNU/Linux 2017.10
Chakra GNU/Linux is a 64-bit, desktop operating system which originally grew out of Arch Linux, but is now maintained as an independent fork. Chakra places a focus on running KDE/Qt software and its sole edition runs the KDE Plasma desktop environment. Chakra bills itself as a semi-rolling or "half-rolling" release distribution. This means that desktop software tends to be updated right away while core system components are held back for additional testing before being released to end users. In theory, this allows Chakra to remain stable while also keeping users up to date so that the operating system never needs to be reinstalled. This semi-rolling approach also means we can install from older media and then bring our system up to date once it is on-line, which is what I intended to do this week.
I downloaded the most recent (as of the time of writing) snapshot of Chakra's ISO which was published back in October of 2017. The ISO was 1.9GB in size. Originally I tried to download the ISO through its torrent, but there were no seeders and I had to download a copy of the distribution from one of its mirrors.
Booting from the ISO brings up the Plasma 5.10 desktop environment. At the bottom of the screen is a panel containing the application menu and system tray. On the desktop a welcome screen is displayed. This welcome screen provides links to the distribution's website, beginner's guide and system installer. There is a tab in the welcome window which will display the latest news and developments coming out of the Chakra project.
Installing
Chakra uses the Calamares system installer. Calamares is a graphical installer which has been adopted by several distributions due to its streamlined nature and easy partitioning options. The installer quickly walked me through selecting my language, time zone and keyboard layout. When it came to disk partitioning, Calamares offered to let me manually divide up the disk or wipe my drive and place Chakra on one partition with another partition set aside for swap space. Then we are asked to create a username and password. The installer worked quickly and without fault, soon announcing it was finished all its tasks and offering to reboot the computer. I like the Calamares installer, its interface is easy to navigate and it provides a consistent, cross-distro approach to setting up Linux-based systems.
Early impressions
Chakra boots to a graphical login screen and signing into our account brings up the Plasma desktop. Plasma is presented with a dark theme which I find pleasant to look at. There are folder icons on the desktop which open the Dolphin file manager. At first, one of the icons overlapped with the Plasma action/widget menu and it was a toss-up which one I would activate if I clicked on that part of the screen. I was able to pull these widgets apart by dragging them with the mouse.
The default Plasma application menu uses a single-pane layout, which I find awkward to use because of the extra clicks required to browse into categories and back out. The menu can be swapped out for alternative menu layouts by right-clicking on the menu's button.
Chakra GNU/Linux 2017.10 -- The application menu and settings panel
(full image size: 412kB, resolution: 1280x1024 pixels)
Initially I found Chakra's default fonts to be smaller than I liked. A quick trip into the distribution's settings panel allowed me to set the size and style of the fonts. I do want to give the developers credit though for the high contrast in the default desktop theme. Some distributions like to display text in low-contrast shades of grey or use transparent backgrounds which make it difficult to read what is on the screen. Chakra was more forgiving in its use of solid colours and white-on-black (or black-on-white) text.
Chakra GNU/Linux 2017.10 -- Adjusting fonts
(full image size: 431kB, resolution: 1280x1024 pixels)
After a while I realized Chakra was not going to let me know if there were software updates available, and I was pretty sure there would be since the installation media was over five months old. I located the Octopi package manager in the application menu and launched it. Octopi presents a simple list of software packages available in Chakra's repositories and can perform searches for package names. Octopi's upgrade feature let me know there were 532 new packages available, totalling 986MB in size. For comparison's sake, there are 900 packages installed by default, meaning over half the packages on my system needed to be replaced. Despite the massive queue of new packages, Octopi (and its underlying Pacman package manager) downloaded and installed all of the new items successfully. After the upgrade was completed there were very few new updates presented during the rest of the week, with new packages trickling in at a rate of about one per day.
Octopi proved to be a handy and fast tool for tracking down and installing new applications too. The package manager has a fairly simple approach and does not really have recognizable categories the way most modern software managers do, but it worked without running into issues.
Chakra GNU/Linux 2017.10 -- The Octopi package manager
(full image size: 433kB, resolution: 1280x1024 pixels)
Applications
Chakra places a strong emphasis on using KDE software and most of the applications included are either related to KDE or are built using the Qt development toolkit. The distribution ships with the QupZilla web browser, KMail, the Konversation IRC client, the Akregator RSS feed reader and the KGet download manager. The Calligra productivity suite is featured rather than the more commonly used LibreOffice. Karbon is available to work with scalable graphics and the KolourPaint simple drawing tool is included. We also have access to the K3b disc burning software, the Okular document viewer and the Dolphin file manager.
Chakra features a handful of multimedia applications, including the bomi video player, the Kdenlive video editor and the Clementine music player. The distribution includes media codecs by default. Rounding out the application menu there is a category dedicated to providing links to Chakra's on-line resources such as the source code repository, bug reports, documentation and the community forums.
Chakra GNU/Linux 2017.10 -- Running Falkon and Calligra Sheets
(full image size: 394kB, resolution: 1280x1024 pixels)
The first wave of package upgrades I installed bumped several key packages up a version or two. The Linux kernel jumped from version 4.12 to 4.14 and the Plasma desktop leaped from 5.10 to 5.12. Following the upgrade the Plasma desktop took a lot longer to login (over 30 seconds) and the desktop performed slower after its upgrade. I was hoping Plasma 5.12 would offer me access to the Plasma Vaults encrypted volumes feature. However, I could not find any way to access Vaults following the upgrade. Some other key packages had their version numbers jump, for example systemd went from version 231 to 235 and the GNU compiler was bumped from 6.3 to 7.3.
Hardware
Chakra worked well in both of my test environments. When running on my laptop computer, Chakra worked smoothly and detected my hardware, including the wireless card. The distribution's performance was middle range, neither notably fast or slow on the laptop. When running in VirtualBox, Chakra was a little on the slow side, especially after installing the first large wave of updates. Plasma always lagged a bit, even after I disabled file indexing and most visual effects.
Chakra GNU/Linux 2017.10 -- Monitoring processes
(full image size: 255kB, resolution: 1280x1024 pixels)
In either environment, a fresh install of Chakra used about 5.5GB of disk space and 390MB of RAM. I noticed after a while that my cache of downloaded packages was getting large, using over 1GB of disk space. I tried using the Octopi Cache Cleaner tool to remove old packages, but it was unable to identify any cached software. I was able to manually remove old packages from under the /var directory.
Conclusions
Chakra is an unusual distribution for a few reasons. It is a rare semi-rolling project, which tries to maintain a fairly stable base system while providing up to date applications. This is an interesting compromise between full rolling and static operating systems. The semi-rolling concept is an idea I like and I was curious to see how well the approach would work dealing with around six months of updates. I was pleased to find Chakra handled the massive upgrade well.
Chakra was once also considered unusual for being very KDE-focused. There are more KDE distribution these days (KaOS, Kubuntu and KDE neon come readily to mind) and I think Chakra may have lost some of its appeal as more competition has established itself in the KDE-centric arena.
Chakra GNU/Linux 2017.10 -- Running Calligra Words
(full image size: 316kB, resolution: 1280x1024 pixels)
I found the distribution to be easy to set up and pretty straight forward to use, but there were a few characteristics which bothered me during my trial with Chakra. One was that while updates installed cleanly, once Plasma 5.12 was installed, I experienced slow login times and reduced performance on the desktop. It could be argued that this is a Plasma problem, not a Chakra problem, but the distribution's rolling release nature means any regressions in new versions of software end up in the user's lap.
Something that tends to bother me about distributions which focus on one desktop toolkit or another is that this approach to selecting software means we are sometimes using less capable tools in the name of toolkit purity. This is not a trade-off I like as I'd rather be using more polished applications over ones which a particular affiliation.
Finally, Chakra includes a number of command line aliases which got in my way. This seems to be a problem I have been running into more often recently. Developers are trying to be helpful by aliasing common commands, but it means that for some tasks I need to change my habits or undefine the provided aliases and the feature ends up being a nuisance instead of a convenience.
Chakra seems to be a capable and useful distribution and I am sure there are people who will appreciate the rolling release nature. Many people will likely also like having lots of KDE applications, and I can see the appeal of this combination. However, one thing which makes me hesitate to recommend Chakra is that the distribution does not appear to bring any special features to the ecosystem. It's a useful operating system and, to be completely fair, users can install non-KDE alternatives if they want to use LibreOffice instead of Calligra or GIMP instead of KolourPaint. But I'm not sure Chakra brings anything unique which makes it stand apart from openSUSE's Tumbleweed or KaOS's polished Plasma offering. Chakra used to be special in its semi-rolling, KDE-focused niche, but these days the distribution has a more competition and I'm not sure the project has any special sauce to set it apart from the crowd.
* * * * *
Hardware used in this review
My physical test equipment for this review was a de-branded HP laptop with the following
specifications:
- Processor: Intel i3 2.5GHz CPU
- Display: Intel integrated video
- Storage: Western Digital 700GB hard drive
- Memory: 6GB of RAM
- Wired network device: Realtek RTL8101E/RTL8102E PCI Express Fast
- Wireless network device: Realtek RTL8188EE Wireless network card
* * * * *
Visitor supplied rating
Chakra GNU/Linux has a visitor supplied average rating of: 9/10 from 22 review(s).
Have you used Chakra GNU/Linux? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
The Debian 10 roadmap and Project Leader election, Netrunner publishes ARM edition, Slackware kicks off package rebuild and Microsoft develops its own Linux-based system for IoT
The Debian Release Team has published information on the current development work going into Debian 10 "Buster". The project is about halfway through the development cycle for Buster with a final release expected around the middle of 2019. "In order to minimize the freeze length, we have shortened the transition freeze by one month. In any case, if you are planning a transition, don't leave it until the last moment, or else it may not make it in time for Buster. The larger the transition is, the earlier it should happen. We do not have a fixed release date, but given the cadence of previous releases it is likely that the release date will be some time mid 2019." Further information can be found in this mailing list post from the Debian Release Team.
The Debian project held its vote for the position of Project Leader this month. The process was streamlined by there being just one candidate running in 2018. Chris Lamb, the current Project Leader and only candidate in this election, has been voted in to serve at the helm of the Debian community for another year. Details on the vote can be found on the project's election page.
* * * * *
Netrunner is a Debian-based distribution which features the KDE Plasma desktop environment. The Netrunner project has published a new edition of the distribution which runs on ARM processors, allowing the distribution to work on ARM-powered laptops like the Pinebook. "The Netrunner team is excited to announce the immediate availability of Netrunner 18.03 on the Pinebook. This release brings the powerful KDE Plasma desktop to low end ARM devices such as the Pinebook, while retaining the performance you’ve come to expect out of Plasma. Features: KDE Plasma 5.12.2; Calamares to aid with post-setup like SD-card resizing and personal user creation; accelerated X11 acceleration with OpenGLES; accelerated video playback with VDPAU; preloaded Firefox for super quick start." Further details are available on the Netrunner website and a separate page has been set up to provide download options for ARM computers.
* * * * *
Slackware is well known as a conservative distribution which rarely introduces sweeping changes. However, the world's oldest surviving Linux distribution introduced some significant changes this week which required a rebuild of the project's software packages: "Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the longest ChangeLog entry in project history). There were two primary motivations for rebuilding everything in the main tree. The first was to switch to the new C++ ABI. The second was to get rid of all the .la files in the LD_LIBRARY_PATH. Really, having .la files installed has been mostly obsolete since things began to use pkg-config instead, but it's not easy to get rid of them unless you do it all at once. If you just take them out of one package, any other packages containing .la files that refer to the removed ones will be broken." How this rebuild will affect users and how to handle the change is covered in Slackware's changelog.
* * * * *
Over the years Microsoft's position on Linux has evolved quite a bit. The company has gone from declaring Linux "a cancer" to supporting Linux server distributions on Microsoft's Azure cloud platform to making it possible to install Linux programs on Windows through a compatibility layer. The software company is now taking another step into the Linux world and creating a new operating system for Internet of Things (IoT) devices using a modified version of the Linux kernel. "Azure Sphere OS: This OS is purpose-built to offer unequaled security and agility. Unlike the RTOSes common to MCUs today, our defense-in-depth IoT OS offers multiple layers of security. It combines security innovations pioneered in Windows, a security monitor, and a custom Linux kernel to create a highly-secured software environment and a trustworthy platform for new IoT experiences." More information on the Linux-powered device can be found in the company's blog post.
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
|
Using systemd to hide files
Hiding-files-with-systemd asks: The systemd 238 release has a new "Temporary File System" feature:
A new TemporaryFileSystem= option to msk [sic] parts of a real file-system tree with tmpfs mounts. This can be used for hiding files/directories not relevant to the unity [sic] or where you don't want any rogue units to potentially access. This also allows for ProtectHome=tmpfs to hide the user's home and runtime directories from units.
What can this do for data security? Would it be useful to prevent another user on the same computer from accessing your private data? Would it also be useful in preventing network intruders from accessing your private data?
DistroWatch answers: I had trouble finding information on the TemporaryFileSystem feature in my quest to answer this question. It didn't turn up when I searched systemd 238's release notes or show up in a search of the systemd site. All searches for an explanation kept taking me back to the the Phoronix article where the above quote originated.
Eventually I was able to track down a copy of this manual page which talks about TemporaryFileSystem and related options for systemd unit files. This is the explanation for the TemporaryFileSystem variable:
Takes a space-separated list of mount points for temporary file systems (tmpfs). If set, a new file system namespace is set up for executed processes, and a temporary file system is mounted on each mount point. This option may be specified more than once, in which case temporary file systems are mounted on all listed mount points. If the empty string is assigned to this option, the list is reset, and all prior assignments have no effect. Each mount point may optionally be suffixed with a colon (":") and mount options such as "size=10%" or "ro". By default, each temporary file system is mounted with "nodev,strictatime,mode=0755". These can be disabled by explicitly specifying the corresponding mount options, e.g., "dev" or "nostrictatime". This is useful to hide files or directories not relevant to the processes invoked by the unit, while necessary files or directories can be still accessed by combining with BindPaths= or BindReadOnlyPaths=.
Put another way, when you specify the name of a directory in the TemporaryFileSystem variable, the program or service started by that unit file cannot see the contents of the given directory. The directory should just look empty to the service. This can be useful if you do not want a daemon to be able to browse through your data or get information about your system's configuration. Using the TemporaryFileSystem variable you can hide the usually accessible /etc or /var directories, for instance, to hide information from the service.
This feature could help you if you wanted to grant users access to certain files on your system through a web or file sharing service, but wanted to make sure they could not access the rest of your file system. If your program does not have a chroot function or you think it could be compromised, then this systemd feature, and related features, offer a level of protection.
However, these systemd features only hide directories and files from the service started by that specific unit file. Other users and programs running on the system are not affected, they can still see your files. If you are sharing a computer with other people who can login directly or you are worried about attackers breaking into your system through means other than a service run with this systemd variable, then this feature does not protect you.
If you want to protect private data, then I recommend looking at directory permissions and encryption. Setting your home directory to block other users' access is a good place to start. Set chmod 0700 permissions on your home directory to keep users other than administrators out of your files. To protect yourself from remote attackers, make sure your system is up to date and disable any unnecessary network services. Consider running web-facing programs, like web browsers, in a Firejail sandbox to isolate these vulnerable programs from your files.
If you are concerned about other users with administrator access or persistent remote attackers, then you can set up an encryption vault. Both the GNOME and Plasma desktops have tools which makes setting up encrypted folders that require a password to access, a simple point-n-click experience.
* * * * *
More answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Oracle Linux 7.5
Avi Miller has announced the release of Oracle Linux 7 Update 5, the latest version of the company's enterprise-class Linux distribution built from the source code of Red Hat Enterprise Linux (RHEL) 7.5: "Oracle is pleased to announce the general availability of Oracle Linux 7 Update 5 for the x86_64 architecture. Notable security-related features in this release: support for Memory Protection Keys on recent Intel processors - CPUs provide this support through a new user-accessible register (PKRU) that contains two separate bits; ability to unlock encrypted devices connected to a network during the boot process; SSLv3 disabled in mod_ssl, this change also restricts the use of certain cryptographic cipher suites; KASLR (kernel address-space layout randomization) for KVM guests added. Btrfs continues to be fully supported in Oracle Linux 7.5 with Unbreakable Enterprise Kernel (UEK). Btrfs support is deprecated in the Red Hat Compatible Kernel." See the release announcement and the release notes for further information.
Trisquel GNU/Linux 8.0
Trisquel GNU/Linux is an Ubuntu-based desktop distribution which features free and open source software exclusively. The project's latest release, Trisquel 8.0 "Flidas", is based on Ubuntu 16.04 and includes support through to the year 2021. "The biggest internal change to the default edition is the switch from GNOME to MATE 1.12. The main reason for this change was that GNOME dropped support for their legacy desktop, which retained the GNOME 2.x user experience and didn't require 3D composition -- a feature that in many computers would still need non-free software to run at full speed. MATE provides a perfect drop-in replacement, it is very light and stable and it retains all the user experience design that we are used to from previous Trisquel releases. The next most important component is Abrowser 59 (based on Mozilla Firefox), which is not only fully-featured and quite faster than before, it has also been audited and tweaked to maximize the user's privacy without compromising on usability." Additional information can be found in the project's release announcement.
Trisquel GNU/Linux 8.0 -- Running the MATE desktop
(full image size: 1.2MB, resolution: 1280x1024 pixels)
AV Linux 2018.4.12
A new version of AV Linux, a Debian-based distribution featuring a collection of audio and video applications, has been released. Version 2018.4.12 comes with various bug fixes, software updates and firmware additions: "AV Linux 2018.4.12 has been released. Bug fixes: updated 4.9.76 real-time kernel with KPTI 'Meltdown' security patch; KPTI can be disabled at boot; numerous important fixes to compatibility with KXStudio repositories; updated and fixed outdated Cin 5.1 and Spotify repositories; WineASIO now works properly; removed GRUB Customizer because it doesn't work on UEFI installations. New additions: ISO files now have accompanying MD5 and SHA256 files; optional 'lowlatency' kernels (required for proprietary video drivers); optional 'SGFXI' proprietary video driver install; UEFI install; Wine-Staging replaces Debian's Wine packages, WineHQ repositories have been added; added firmware for Echo audio devices; dynamic CPU frequency adjustment (in 'Settings' menu); real-time quick configuration scan to check system tuning...." Read the rest of the release announcement for a full changelog.
Smoothwall Express 3.1 SP4
Smoothwall Express, is a specialist Linux distribution for firewalls and routers, featuring a custom web-based configuration interface. The project's origins date back to the year 2000 and it still continues to evolve today - the developers have just announced an update to their 3.1 product line: "The Smoothwall Express team announce the release of Update9/SP4. This update and service pack should address most of the problems you encountered with Update8/SP3. We resolved a number of bugs, updated a number of packages, and re-released all of the Update8 packages. Of particular note, we made a number of improvements in the UI, added packages that will allow you to use a wireless IF for RED (manual only; not yet integrated into the system), and switched from Openswan to Libreswan. We also locked the kernel headers (used for glibc, klibc and a few other packages) to those of 3.4.104 to ensure a consistent Linux API going forward. Update8 switched to 3.16 kernel headers for some packages; this may have been the source of inexplicable problems some people reported after applying Update8." Here is the full release announcement as published on the distribution's user forums.
* * * * *
Development, unannounced and minor bug-fix releases
|
| Torrent Corner |
Weekly Torrents
The table below provides a list of torrents DistroWatch is currently seeding. If you do not have a bittorrent client capable of handling the linked files, we suggest installing either the Transmission or KTorrent bittorrent clients.
Archives of our previously seeded torrents may be found in our Torrent Archive. We also maintain a Torrents RSS feed for people who wish to have open source torrents delivered to them. To share your own open source torrents of Linux and BSD projects, please visit our Upload Torrents page.
Torrent Corner statistics:
- Total torrents seeded: 814
- Total data uploaded: 19.1TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll |
Dual booting versus virtual machines
Many of our readers run multiple operating systems. In a past poll, 49% reported they dual boot open source and a proprietary operating systems. This week we would like to find out, from people who run multiple operating systems, do you prefer to dual boot or run one platform in a virtual machine? Do you ever take advantage of compatibility software such as DOSbox, WINE or WSL in place of running a complete separate operating system? Let us know your preferred set up in the comments.
You can see the results of our previous poll on the minimum length of long term support in last week's edition. All previous poll results can be found in our poll archives.
|
Dual booting versus virtual machines
| I dual boot: | 890 (29%) |
| I use virtual machines: | 600 (20%) |
| I use compatibility software (WINE/DOSbox/WSL): | 123 (4%) |
| I use a combination of the above: | 829 (27%) |
| I run one operating system: | 589 (19%) |
|
|
| DistroWatch.com News |
Finding long term support (LTS) operating systems
This week we added a new feature to our Search page which allows visitors to more easily find long term support (LTS) releases. When selecting "Fixed (LTS)" from the Release model field, a list of projects which offer long term support will be displayed.
In this case, LTS has a fairly strict definition. For a distribution to be considered LTS in our database it must A) have a declared support cycle and B) that support cycle must be at least five years long. Five years was chosen by our readers in a poll. Projects which either do not declare the length of their support cycle on their website or provide fewer than five years of support are not included in our search results.
* * * * *
Distributions added to waiting list
- Arcticy Linux. Arcticy Linux is a distribution based on Arch Linux which features the Xfce desktop environment. It ships with desktop applications and multimedia support included.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 30 April 2018. Past articles and reviews can be found through our Article Search page. To contact the authors please send e-mail to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews/submissions, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, donations, comments)
- Bruce Patterson (podcast)
|
|
| Tip Jar |
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 2, value: US$109.17) |
  1J5s35r7v8L3k2zmr3JmUfydzvdnsiNXm2 |
|
|
| Linux Foundation Training |
|
|
| Archives |
| • Issue 793 (2018-12-10): openSUSE Tumbleweed, finding non-free packages, Debian migrates to usrmerge, Hyperbola gets FSF approval |
| • Issue 792 (2018-1203): GhostBSD 18.10, when to use swap space, DragonFly BSD's wireless support, Fedora planning to pause development schedule |
| • Issue 791 (2018-11-26): Haiku R1 Beta1, default passwords on live media, Slax and Kodachi update their media, dual booting DragonFly BSD on EFI |
| • Issue 790 (2018-11-19): NetBSD 8.0, Bash tips and short-cuts, Fedora's networking benchmarked with FreeBSD, Ubuntu 18.04 to get ten years of support |
| • Issue 789 (2018-11-12): Fedora 29 Workstation and Silverblue, Haiku recovering from server outage, Fedora turns 15, Debian publishes updated media |
| • Issue 788 (2018-11-05): Clu Linux Live 6.0, examining RAM consumpion, finding support for older CPUs, more Steam support for running Windows games on Linux, update from Solus team |
| • Issue 787 (2018-10-29): Lubuntu 18.10, limiting application access to specific users, Haiku hardware compatibility list, IBM purchasing Red Hat |
| • Issue 786 (2018-10-22): elementary OS 5.0, why init keeps running, DragonFly BSD enables virtual machine memory resizing, KDE neon plans to drop older base |
| • Issue 785 (2018-10-15): Reborn OS 2018.09, Nitrux 1.0.15, swapping hard drives between computers, feren OS tries KDE spin, power savings coming to Linux |
| • Issue 784 (2018-10-08): Hamara 2.1, improving manual pages, UBports gets VoIP app, Fedora testing power saving feature |
| • Issue 783 (2018-10-01): Quirky 8.6, setting up dual booting with Ubuntu and FreeBSD, Lubuntu switching to LXQt, Mint works on performance improvements |
| • Issue 782 (2018-09-24): Bodhi Linux 5.0.0, Elive 3.0.0, Solus publishes ISO refresh, UBports invites feedback, Linux Torvalds plans temporary vacation |
| • Issue 781 (2018-09-17): Linux Mint 3 "Debian Edition", file systems for SSDs, MX makes installing Flatpaks easier, Arch team answers questions, Mageia reaches EOL |
| • Issue 780 (2018-09-10): Netrunner 2018.08 Rolling, Fedora improves language support, how to customize Kali Linux, finding the right video drivers |
| • Issue 779 (2018-09-03): Redcore 1806, keeping ISO downloads safe from tampering, Lubuntu makes Calamares more flexible, Ubuntu improves GNOME performance |
| • Issue 778 (2018-08-27): GuixSD 0.15.0, ReactOS 0.4.9, Steam supports Windows games on Linux, Haiku plans for beta, merging disk partitions |
| • Issue 777 (2018-08-20): YunoHost 3.0.0.1, limiting process resource usage, converting file systems on Fedora, Debian turns 25, Lubuntu migrating to Wayland |
| • Issue 776 (2018-08-13): NomadBSD 1.1, Maximum storage limits on Linux, openSUSE extends life for 42.3, updates to the Librem 5 phone interface |
| • Issue 775 (2018-08-06): Secure-K OS 18.5, Linux is about choice, Korora tests community spin, elementary OS hires developer, ReactOS boots on Btrfs |
| • Issue 774 (2018-07-30): Ubuntu MATE & Ubuntu Budgie 18.04, upgrading software from source, Lubuntu shifts focus, NetBSD changes support policy |
| • Issue 773 (2018-07-23): Peppermint OS 9, types of security used by different projects, Mint reacts to bugs in core packages, Slackware turns 25 |
| • Issue 772 (2018-07-16): Hyperbola GNU/Linux-libre 0.2.4, UBports running desktop applications, OpenBSD auto-joins wi-fi networks, boot environments and zedenv |
| • Issue 771 (2018-07-09): Linux Lite 4.0, checking CPUs for bugs, configuring GRUB, Mint upgrade instructions, SUSE acquired by EQT |
| • Issue 770 (2018-07-02): Linux Mint 19, Solus polishes desktop experience, MintBox Mini 2, changes to Fedora's installer |
| • Issue 769 (2018-06-25): BunsenLabs Helium, counting Ubuntu users, UBports upgrading to 16.04, Fedora CoreOS, FreeBSD turns 25 |
| • Issue 768 (2018-06-18): Devuan 2.0.0, using pkgsrc to manage software, the NOVA filesystem, OpenBSD handles successful cron output |
| • Issue 767 (2018-06-11): Android-x86 7.1-r1, transferring files over OpenSSH with pipes, LFS with Debian package management, Haiku ports LibreOffice |
| • Issue 766 (2018-06-04): openSUSE 15, overview of file system links, Manjaro updates Pamac, ReactOS builds itself, Bodhi closes forums |
| • Issue 765 (2018-05-28): Pop!_OS 18.04, gathering system information, Haiku unifying ARM builds, Solus resumes control of Budgie |
| • Issue 764 (2018-05-21): DragonFly BSD 5.2.0, Tails works on persistent packages, Ubuntu plans new features, finding services affected by an update |
| • Issue 763 (2018-05-14): Fedora 28, Debian compatibility coming to Chrome OS, malware found in some Snaps, Debian's many flavours |
| • Issue 762 (2018-05-07): TrueOS 18.03, live upgrading Raspbian, Mint plans future releases, HardenedBSD to switch back to OpenSSL |
| • Issue 761 (2018-04-30): Ubuntu 18.04, accessing ZFS snapshots, UBports to run on Librem 5 phones, Slackware makes PulseAudio optional |
| • Issue 760 (2018-04-23): Chakra 2017.10, using systemd to hide files, Netrunner's ARM edition, Debian 10 roadmap, Microsoft develops Linux-based OS |
| • Issue 759 (2018-04-16): Neptune 5.0, building containers with Red Hat, antiX introduces Sid edition, fixing filenames on the command line |
| • Issue 758 (2018-04-09): Sortix 1.0, openSUSE's Transactional Updates, Fedora phasing out Python 2, locating portable packages |
| • Issue 757 (2018-04-02): Gatter Linux 0.8, the UNIX and Linux System Administration Handbook, Red Hat turns 25, super long term support kernels |
| • Issue 756 (2018-03-26): NuTyX 10.0, Neptune supplies Debian users with Plasma 5.12, SolydXK on a Raspberry Pi, SysV init development |
| • Issue 755 (2018-03-19): Learning with ArchMerge and Linux Academy, Librem 5 runs Plasma Mobile, Cinnamon gets performance boost |
| • Issue 754 (2018-03-12): Reviewing Sabayon and Antergos, the growing Linux kernel, BSDs getting CPU bug fixes, Manjaro builds for ARM devices |
| • Issue 753 (2018-03-05): Enso OS 0.2, KDE Plasma 5.12 features, MX Linux prepares new features, interview with MidnightBSD's founder |
| • Issue 752 (2018-02-26): OviOS 2.31, performing off-line upgrades, elementary OS's new installer, UBports gets test devices, Redcore team improves security |
| • Issue 751 (2018-02-19): DietPi 6.1, testing KDE's Plasma Mobile, Nitrux packages AppImage in default install, Solus experiments with Wayland |
| • Issue 750 (2018-02-12): Solus 3, getting Deb packages upstream to Debian, NetBSD security update, elementary OS explores AppCentre changes |
| • Issue 749 (2018-02-05): Freespire 3 and Linspire 7.0, misunderstandings about Wayland, Xorg and Mir, Korora slows release schedule, Red Hat purchases CoreOS |
| • Issue 748 (2018-01-29): siduction 2018.1.0, SolydXK 32-bit editions, building an Ubuntu robot, desktop-friendly Debian options |
| • Issue 747 (2018-01-22): Ubuntu MATE 17.10, recovering open files, creating a new distribution, KDE focusing on Wayland features |
| • Issue 746 (2018-01-15): deepin 15.5, openSUSE's YaST improvements, new Ubuntu 17.10 media, details on Spectre and Meltdown bugs |
| • Issue 745 (2018-01-08): GhostBSD 11.1, Linspire and Freespire return, wide-spread CPU bugs patched, adding AppImage launchers to the application menu |
| • Issue 744 (2018-01-01): MX Linux 17, Ubuntu pulls media over BIOS bug, PureOS gets endorsed by the FSF, openSUSE plays with kernel boot splash screens |
| • Issue 743 (2017-12-18): Daphile 17.09, tools for rescuing files, Fedora Modular Server delayed, Sparky adds ARM support, Slax to better support wireless networking |
| • Issue 742 (2017-12-11): heads 0.3.1, improvements coming to Tails, Void tutorials, Ubuntu phasing out Python 2, manipulating images from the command line |
| • Full list of all issues |
| Random Distribution | 
Evinux
Evinux was a Linux live CD based on Knoppix, but with light-weight window managers - Fluxbox and XFce. It was developed by Linucie.net, a French organisation for promoting Free Software and GNU/Linux.
Status: Discontinued
|
| Linux Training |
|
|
• 
• 
• 
• 
• 
• 
• 
