| DistroWatch Weekly
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 • Video Drivers (by TuxRaider on 2018-09-10 01:24:29 GMT from United States) |
my thinkpad has nvidia and i just use the FOSS nouveau, i have a optiplex desktop with intel video and use what antiX (mostly debian) supplies (probably an open source driver provided by xorg, and my newest PC has a AMD Radeon RX580 and i use the amd-graphics kernel firmware
2 • nvidia drivers (by Vytas on 2018-09-10 05:34:43 GMT from Lithuania)
Sadly OSS nvidia driver spins on my GTX430 (I think or 420) fan on one PC always to max or sth. close to that so I have to install proprietary there.
3 • VDs (by zykoda on 2018-09-10 06:32:14 GMT from United Kingdom)
Pragmatism and the law of least effort rule: I resort to proprietary when FOSS fails expectations. A single PC may have both in multiboot. Switching graphics cards. DEs, WMs ..etc or software eg CUDA Opengl version, may dictate.
4 • Video Drivers (by kc1di on 2018-09-10 08:47:34 GMT from United States)
I chose use both, on my machines with Nvidia cards the nouveau driver does not work well and I'm forced to use Nvidia's drivers if I want the machines to do any real demanding stuff. I will say that Nvidia has tried to supply Linux drivers for most of their cards and they work quite well at least the ones I have tried. Nouveau work ok with some cards but not all. only alternative would be to install a different card. So that's how it stand as of today.
5 • Video drivers (by Argent on 2018-09-10 09:15:55 GMT from United States)
Not a gamer by any description but do enjoy video from various sources. Run strictly AMD and Xorg does the job with my Asus Radeon RX560-04G-EVO video card. The card is quite sufficient for anyone's needs but strictly watch videos. Also use GIMP, Inkscape for image manipulation and editing, with a really good HD LED monitor the graphics are amazing. Trust Xorg throughout my PC although have ventured with proprietary AMD drivers with great success. Maybe it is easier with Xorg and experience really no distinct differences with proprietary.
Linux and Xorg apparently have better results with Radeon versus NVidia or perhaps a better relationship with development with Radeon.
To me less is more, less you have to fiddle around to get something working OOTB then it's the best and safe bet. Xorg works great!
6 • fglrx (by Tim on 2018-09-10 09:42:35 GMT from United States)
This is something I have to admit I don't understand very well
For years, I used Debian with the closed-source AMD Catalyst driver (fglrx.) but it stopped working when stretch was in testing (AMD dropped support upstream.)
The open source radeon drivers work ok with my card (an older AMD Cedar one) but on Debian I could never get the right aspect ratio on either a 16:9 monitor or a 16:10 one. No luck with xrandr. On Ubuntu/Mint they detect the proper resolution automatically. Usually that means there's some non-free firmware, but I for the life of me couldn't find it. Hence we've been using Ubuntu since 15.04
7 • Poll, Netrunner,Kali, and TAILS (by cykodrone on 2018-09-10 11:11:07 GMT from Canada)
I chose open-source in the polll, BUT, I will use the non-free firmware in the distro's repo if the FOSS driver doesn't cut the mustard. Does firmware count as a 'driver'?
I used Netrunner back in the day, I can't even remember what it was based on back then, that being said, it changes its base distro as often as I change my underwear. I have no problem learning new commands for different base flavours, noobz, not so much.
Kali and TAILS: Anything that runs systemd under the hood is always OFF my radar. The corporation that writes and maintains secretive and system enveloping systemd has many contracts with numerous government agencies, including law enforcement. Systemd has become the actual distro, the kernel, package manger and GUI are now just 'necessary evil' extra layers to the author. Have a nice day. :)
8 • sceptical? (by dxrobertson on 2018-09-10 11:28:23 GMT from United States)
'Some people are sceptical of distributions like Devuan because it is just Debian without systemd'.
Thats exactly what Devuan is, Debian without systemd. Simple. What in regards to 'distrubutions like' Devuan is sceptical (mistrusting, doubtful)?
Distrowatch provides a good answer to the posted question, not sure why this skepticism phrase was included.
9 • skeptical (by Tim on 2018-09-10 12:47:50 GMT from United States)
I think he was defending Devuan. A lot of times people will say that a particular distro isn't anything new because it's "just a respin" of Debian or Ubuntu. Jesse's point I took to mean that it's a lot of work to make a distro with very different defaults than the base, even if you're using the base repositories.
10 • Netrunner Rolling review: unanswered question (by curious on 2018-09-10 13:17:07 GMT from Germany)
Thanks for the review.
You recommend Netrunner Rolling for "users wanting the Arch Linux experience without the effort". This immediately brings up the question of how this distro compares to Manjaro - I always thought that Manjaro was meant to provide exactly that: an Arch(-like) experience without the effort. And Manjaro has a KDE flavour.
So, what sets Netrunner Rolling apart from its immediate parent, Manjaro KDE?
11 • Arch Linux experiance (by silent on 2018-09-10 13:55:57 GMT from Hungary)
"Users wanting the Arch Linux experience without the effort should give Netrunner Rolling a try." The effort itself is the Arch Linux experience, I guess: sort of do it yourself from some prebuilt elements. Could any binary distro provide LFS/BLFS experience?
12 • Open versus proprietary video drivers (by YumaJoe on 2018-09-10 15:02:15 GMT from United States)
I sort of remember at least one distro that selects the proper proprietary driver by default during installation. When I first started exploring Linux, it was not uncommon to ruin a fresh installation by trying to switch to proprietary drivers (in my case Nvidia). In most cases, for me, what ever is default is good enough.
13 • Devuan (by anonymous on 2018-09-10 15:12:50 GMT from United States)
I agree with #8.
14 • video drivers (by Johannes Kirk on 2018-09-10 15:30:00 GMT from Canada)
I run 'nvidia-detect' script which checks for an NVIDIA GPU in the system and recommends one of the non-free accelerated driver.
sudo apt-get install nvidia-xxx (For Nvidia driver package)
sudo apt-get install fglrx (AMD/ATI drivers)
mostly serves the purpose.
15 • Why wouldn't you use proprietary? (by DriverGuy on 2018-09-10 15:39:13 GMT from United States)
I don't understand why you wouldn't use proprietary graphics drivers when manufacturer makes it available. If it is a licensing issue, well didn't we buy our graphics cards? Wouldn't support drivers, manuals, etc...come with the purchase of the card? I don't mean this to be trolling, this is an honest question for my own curiosity. If the manufacturer of your graphics card makes available a driver for your operating system, why not use it? Unless it out right breaks your graphics, why use FOSS?
16 • fglrx (by Tim on 2018-09-10 16:00:21 GMT from United States)
fglrx isn't in Debian or Ubuntu anymore and hasn't been since 2016. AMD dropped support for it.
I think that's one part to your answer... if you're using the manufacturer's driver and they stop supporting it, you're out of luck. If there's a FOSS one that works and you know it works that's some piece of mind (although not entirely- the switch from nv to nouveau EOL'd one of my computers)
The other part is that if there's a bug in the driver your distro can't fix it, only, the maintainer
But honestly the main part is that if the computer's working right with the default driver (the FOSS one) then going through the extra effort to set up the manufacturer's one isn't something most will bother doing. As @12 said, it's sometimes not trivial to switch.
17 • Proprietary Video Drivers (by penguinx64 on 2018-09-10 16:11:28 GMT from Bahrain)
Intel processors and chipsets seem to work just fine with no driver hassles using Linux. Intel is much more Linux friendly than AMD/ATI/NVidia. The same thing with Intel Wifi adapters instead of Broadcom or Realtek. But these alternatives to Intel seem to work just fine with Windows. Shouldn't Linux be able to handle these as well?
18 • Proprietary Wifi Drivers (by Justin on 2018-09-10 17:04:09 GMT from United States)
I know this week's topic is video, but the proprietary drivers got me thinking about wifi. Intel provides kernel drivers for their laptop wifi chipsets, so if you have a laptop with one, you're in good shape. USB dongles, on the otherhand, are a crap shoot. Does anyone know why Intel wifi chipsets aren't used in USB dongles? All I can find our internal PCI cards that may or may not work in a desktop (and definitely aren't portable).
Similar question for chipsets that use the ath9k driver. Last time I researched this I recall seeing explicit disclaimers of not using the ath9k driver with them even though the chipset was supposedly the same. Wireless AC support on Linux seems like basically Intel.
19 • @15, 17 Proprietary Drivers (by cykodrone on 2018-09-10 17:30:01 GMT from Canada)
Since beginning of time when CPUs were chiselled from stone and Linux was written on punch cards...just kidding, seriously, been fiddling with many diff flavours of Linux since the middle 00s, went full blown Linux in 2010 (propane torched my XP install disk), tried MANY proprietary and non proprietary drivers of all flavours. Overall, the proprietary drivers were buggy bloat, rarely ever had a problem with FOSS drivers, after install settings, etc. I also found that proprietary drivers are resource hogs (too many CPU cycles and hot running GPUs), aside from their annoying advertising GUI omnipresence. Even though I am an AMD fan and user now, Nvidia's worked the best, but they cheesed me off when they refused cooperate with Linus (angering my god turned me off of them). My AMD CPU/GPU machine works fine, firmware does help though, enables sensors and extra features, etc. I do get the occasional full screen video tearing, but nothing I can't live with, it's a reasonable trade off for a lack of trouble shooting, and a cooler running machine with with plenty of overhead processing power. Each to their own.
20 • video cards (by DB on 2018-09-10 18:04:20 GMT from Canada)
I don't know about how amd/ati works with linux, but I've been using PCLinuxOS with the Nvidia drivers now for a few years and have had Very good results. Now on Mint, at least untill recently, I've Always had a problem using the nvidia drivers in there as as soon as I reboot the font is SO SMALL that I can't even read it, and shame on Mint as this went on from the fist time I used it (15) untill the most recent version before they finally fixed the problem (19). Now they seem to have the Best set up for my laptop, which uses both Intel and nvidia. Thank You Mint.
21 • Proprietary video cards and... (by Kazan on 2018-09-10 20:11:26 GMT from United Kingdom)
Proprietary video cards and...the firmware that runs them.
If a company makes video cards, graphic cards, etc they do so to earn money, and not to give them away for free. 2% users in the world won't make that money, so sometimes those manufacturers pay the good guy by releasing some firmware that might, yes might, work with Linux. We, who use Linux and other open source operating systems, would always get 2nd rated firmware, so called drivers. Or, all you have to do is to make open source video cards, graphic cards, etc.
22 • @ # 20 • video cards (by Johannes Kirk on 2018-09-10 21:35:07 GMT from Canada)
@ # 20
MX linux ships with VLC, rest can be installed by Package Installer.
Mint used to bundle VLC in the ship-box, in latest you have to install it.
with MX and Mint, I hardly install any additional drivers.
23 • Thank God for SystemrescueCD... (by Kingneutron on 2018-09-10 21:37:05 GMT from United States)
They finally revved another one, I was worried it was no longer being maintained ;-)
24 • @22 Re: Video Cards (by Rev_Don on 2018-09-10 23:34:41 GMT from United States)
And what does VLC have to do with Video Cards and Video Card Drivers? Plus, VLC ships with the majority of Linux Distros and can easily be installed on the rest so what makes MX Linux special or pertinent to Graphics Drivers?
25 • we have choices :) (by mmphosis on 2018-09-11 01:44:31 GMT from Canada)
I come from a "there is only one way to do it" kind of philosophy (ie. the Python programming language), although now there are two ways with python2 vs python3 but I digress. I am seeing how great Linux can be because: we have choices :)
Open source video driver or closed source video driver? Your choice. Maybe even boot up with different choices. Systemd or another init? Your choice. Swap out one init for another init? Your choice -- and even though swapping inits on the fly might cause a problems it is doable, again your choice. Swapping out the init system is probably next to impossible on MacOS and Windows (not too many choices there.)
26 • re #12 Test X and video drivers (by More Gee on 2018-09-11 04:40:14 GMT from United States)
The only one that I remember offering choices of drivers to to try and switch between VESA and X.org was Puppy Linux. I uses to use it try and debug the resolutions and scan rates. In the past I had issues in Linux from video cards that had HDMI or s-video or composite ports or were SiS or Intel direct X accelerated cards that came with buggy XP drivers that would not display 640x480 text without direct x or a generic windows driver.
27 • @ 21 Video and graphics cards (by OstroL on 2018-09-11 18:32:43 GMT from Poland)
True, there are no non-proprietary video and graphics cards, so if the manufacturer kindly decides that they should provide the 2% of us Linux users with (most times 2nd grade) drivers for Linux, all we can do is be thankful to them.
28 • @ 10 - difference between Manjaro and Netrunner (by brad on 2018-09-11 22:37:56 GMT from United States)
I'm a Manjaro KDE user, but I've never used NetRunner. Based on the review, the only differences that I can spot are the use of a NetRunner "theme", and the Discover package manager, vs. pamac on Manjaro (this difference is surprising to me, since Discover is "typically" used with Kubuntu).
The reviewer points out that there aren't many differences, and that one can tweak Manjaro to emulate the NetRunner "look and feel".
I guess it comes down to preferences, but I will note that Manjaro has been relatively stable since 2016, but when I tried NetRunner during that time frame, I found it to be lacking in certain aspects.
29 • Video Drivers (by Ken on 2018-09-12 04:47:31 GMT from United States)
On my LIbreboot Thinkpad x200 running Parabola, I use the nouveau driver which works flawlessly, as it should.
For my desktop, the goal was to be able to dump Windows but still play my favorite games. My previous Nvidia graphics card had no problem with the nouveau driver. Unfortunately, I now have a GTX 970, which hasn't yet been reverse-engineered (and may never be), so nouveau doesn't work well with it. So running Manjaro, I use the distribution-provided proprietary driver out of necessity.
30 • @29 GTX970 card... (by Kazan on 2018-09-12 12:42:28 GMT from United Kingdom)
"Unfortunately, I now have a GTX 970, which hasn't yet been reverse-engineered (and may never be), so nouveau doesn't work well with it."
I just can't understand people, who pay a lot of money to buy an excellent graphic card to NOT to use it, just because of some ideological problems. But have use it, using the "proprietary" driver, hiding the same ideological matter under a pillow, while using the driver to play games, one has to buy, also from companies, which are there to make profit.
(By the way, reverse engineering is equal to stealing, after all.)
31 • @30: (by dragonmouth on 2018-09-12 15:37:08 GMT from United States)
"reverse engineering is equal to stealing"
It depends on who does it. If it is an individual or a small, insignificant company, then it is called stealing. But when Microsoft, Google, Intel or any large company, with plenty of high powered lawyers, reverse engineers anything, it is called a business strategy or a business tactic.
32 • @31 stealing... (by OstroL on 2018-09-12 20:00:32 GMT from Poland)
>> "reverse engineering is equal to stealing"
It depends on who does it. If it is an individual or a small, insignificant company, then it is called stealing. But when Microsoft, Google, Intel or any large company, with plenty of high powered lawyers, reverse engineers anything, it is called a business strategy or a business tactic.<<
Are you saying that those lawyers of your country are helping those big companies, which also are in your country, to steal?
33 • @32: (by dragonmouth on 2018-09-12 20:40:19 GMT from United States)
The lawyers know who is signing their checks. In my country, in your country, in any country.
34 • Reverse Engineering (by M.Z. on 2018-09-13 16:03:05 GMT from United States)
The truth about reverse engineering is that it is very much a 'it depends' type of situation. ReactOS doing a version of Windows as a non-profit hobby project? That's fine by everyone.
China & North Korea doing state sponsored espionage to get technology transferred to their countries from everyone else? The whole world hates that, or practically all of it anyway.
Likewise the corporate world has an 'it depends' attitude.
The last case I heard was of a German company tearing down a Tesla Model 3 & and doing a thorough product & engineering analysis. There was a cost estimate for the total parts, ($28,000 US if I remember right), & an estimate on what would have to be sold to generate a profit at various average price points. They also complimented the electronics as the best they saw in automobiles & said various other things in their report to a German auto company. That got a reply of 'the cost sounds about right' from Musk, & everyone went on with their business.
Of course if someone tried to get those engineers to wholesale ripoff the Model 3 design & start profiting off copies, it would be a very different story with a very different reaction.
35 • Closed or open source drivers for proprietary graphic, sound or video cards (by Pierre on 2018-09-14 07:43:47 GMT from United Kingdom)
"This week we would like to know if you are currently using open or closed source video drivers on Linux."
The question above appears to be a straightforward one, but it hides a trap in it. There aren't any open source graphic, sound or video cards or any other device cards, so even the more or less adequate drivers for Linux to them come from the manufacturers themselves. Whatever drivers made by the Linux distro makers are general ones, which might or might not work with a given card, or a given laptop or a given configuration of a computer.
The manufacturers would most times provide drivers for Linux for their cards, just to show that they are not bad guys, but they don't really have to work too hard on giving fully up to date drivers. On the other hand, high praise for the Linux distro developers for providing us with those general drivers.
Some work, some don't though. I have a laptop, where every Linux general driver work, but not the driver for the touchpad, not even the proprietary Linux driver for it. I have to use a mouse to get things done.
36 • Open Source Video Drivers (by debianxfce on 2018-09-14 10:46:28 GMT from Finland)
For the open source drivers, use a rolling release os, Mesa git and the latest available kernel. Mainline Mesa and kernels do have buggy and partially implemented gpu drivers. These are in my distribution: https://www.youtube.com/watch?v=fKJ-IatUfis
Number of Comments: 36
Display mode: DWW Only • Comments Only • Both DWW and Comments
|• 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 220.127.116.11, 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|
|• Issue 741 (2017-12-04): Pop!_OS 17.10, openSUSE Tumbleweed snapshots, installing Q4OS on a Windows partition, using the at command|
|• Issue 740 (2017-11-27): Artix Linux, Unity spin of Ubuntu, Nitrux swaps Snaps for AppImage, getting better battery life on Linux|
|• Issue 739 (2017-11-20): Fedora 27, cross-distro software ports, Ubuntu on Samsung phones, Red Hat supports ARM, Parabola continues 32-bit support|
|• Issue 738 (2017-11-13): SparkyLinux 5.1, rumours about spyware, Slax considers init software, Arch drops 32-bit packages, overview of LineageOS|
|• Issue 737 (2017-11-06): BeeFree OS 18.1.2, quick tips to fix common problems, Slax returning, Solus plans MATE and software management improvements|
|• Issue 736 (2017-10-30): Ubuntu 17.10, "what if" security questions, Linux Mint to support Flatpak, NetBSD kernel memory protection|
|• Issue 735 (2017-10-23): ArchLabs Minimo, building software with Ravenports, WPA security patch, Parabola creates OpenRC spin|
|• Issue 734 (2017-10-16): Star 1.0.1, running the Linux-libre kernel, Ubuntu MATE experiments with snaps, Debian releases new install media, Purism reaches funding goal|
|• Issue 733 (2017-10-09): KaOS 2017.09, 32-bit prematurely obsoleted, Qubes security features, IPFire updates Apache|
|• Issue 732 (2017-10-02): ClonOS, reducing Snap package size, Ubuntu dropping 32-bit Desktop, partitioning disks for ZFS|
|• Issue 731 (2017-09-25): BackSlash Linux Olaf, W3C adding DRM to web standards, Wayland support arrives in Mir, Debian experimenting with AppArmor|
|• Full list of all issues|
|Random Distribution |
Namib GNU/Linux is a desktop operating system based on (and compatible with) the Arch Linux distribution. Namib is available in multiple desktop editions and can be set up using the Calamares system installer.