 DistroWatch Weekly |
| Tip Jar |
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) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
| Extended Lifecycle Support by TuxCare |
|
|
| Reader Comments • Jump to last comment |
1 • Mobile Linux (by DaveW on 2019-05-20 00:53:08 GMT from United States)
I do not have a mobile device or plans to get one. That leaves only one option to vote for.
2 • mobile (by Tim on 2019-05-20 01:34:59 GMT from United States)
A few years back I bought a very cheap 7 inch tablet with the brand name iRulu. It was running Android and was able to run Debian Wheezy LXDE in a chroot with no trouble.
It was only a toy, but I was struck by how well it ran. LXDE was obviously not designed for cheap bad touch screens, but the experience was actually ok.
The other way I’ve interacted usefully with Linux on a phone was to install an xserver and an ssh app and connect remotely to a computer on my home network. It was a good way to control a media center playing music.
I’ll be interested in both the librem 5 and the PinePhone. I hope they support all Linux apps and not just ones optimized for phones
3 • OS's (by vern on 2019-05-20 01:42:01 GMT from United States)
I never had much success with Sabayon. I had a 10 year old pc at the time. Even so it just didn't fit for me.
I just tried Pepermint. Someone on Ubuntu forums was not liking Lubuntu LXQT. Suggested he might try PeppermintOS 64x LXDE. Intrigued, I spent a hour looking for reviews and FAQ's. Just installed it. Not sure what to expect. The installation went without a hitch.
I also remember the creator of Peppermint left recently or maybe that was another distro.
4 • Clear Linux (6 names) (by gregzeng on 2019-05-20 02:05:46 GMT from United Kingdom)
There are two different & separate versions of "Clear OS". The Intel operating system: "Clear Linux* OS", with the asterisk punctuation. This seems very different from:
(2) Clear Linux
(3) ClearOS (USA)
(4) Clear Linux OS (New Zealand)
(5) Clear Linux 27900 (New Zealand, used by Distrowatch)
(6) Clear Linux 29350 (Intel USA, used by Phoronix)
"Clear Linux* OS" is a wrong use of "*" (asterisk punctuation). Elsewhere in their Intel web site, they replace the asterisk "*" with the superscript "1". So the correct name should be (4) above: "Clear Linux OS". However this proper name "Clear Linux OS", is very often also written as "ClearOS". "Clear Linux" is quite a very different operating system.
"Clear Linux OS", based from the nation New Zealand, is based on Fedora, according to Distrowatch. "Clear Linux" comes from Intel, USA, but seems to be "independent". Distrowatch claims of "independent" is very alarming & inconsistent. Both use RPM (Red Hat) package managers, so are NOT independent, relying on RPM packages. According to Distrowatch, the "latest" is Clear Linux 27900. According to Phoronix, the latest is Clear Linux 29350.
Using Distrowatch, I compared the files inside the two operating systems, Clear Linux 27900 and Intel's ClearOS 7.6.0. Clear Linux 27900 has more user applications, such as Firefox 65.0.1. The "independence" claim is because the RPM-based operating systems cannot be safe with RPM-packages. So "kdenlive.rpm" (a third party video editor) is guaranteed to not run on most RPM-based operating systems. That is why we MIGHT use kdenlive in its appimage format.
5 • Peppermint (by hotdiggettydog on 2019-05-20 03:02:48 GMT from Asia/Pacific Region)
#3 post. I'm pretty sure the developer team for Peppermint is intact. They just released version 10 which I'll be installing soon. I'm a huge Peppermint fan btw.
You must be thinking of Solus. I heard the main man abandoned the project under scandalous clouds.
6 • #5 abandonment (by vern on 2019-05-20 03:20:04 GMT from United States)
I stumbled across what OS I was thinking about. It's '#!' or CrunchBang. Oddly the originator suggested using pure debian when he left. A couple of teams revived #! - #!++ and another.
7 • Beginner-friendly Gentoo (by Arthur Prefect on 2019-05-20 03:35:04 GMT from Australia)
Thanks for the review of Sabayon - this distro always seems to be so close but not quite there, I hope that it reaches its goals eventually. Meanwhile, for a beginner-friendly way to learn Gentoo in a stable environment, I recommend Calculate Linux. I have used it for over two years as my daily driver and it is very stable across many upgrades. Everything works, it is very fast and there is Gentoo underneath to play with!
8 • Zombieland (by bison on 2019-05-20 03:58:37 GMT from United States)
> We also patched the latest Intel chip vulnerability called Zombieland in all five versions of our Robolinux 10 series.
They probably mean ZombieLoad. Zombieland is a movie. :)
9 • Intel FUD (by St. Vincent on 2019-05-20 04:42:25 GMT from United States)
Why won't Distrowatch tell the truth? The MDS vulnerabilities do not affect "multiple processors", they only impact Intel chips. AMD processors are immune.
10 • Mobile Linux (by Antonie van der Tweel on 2019-05-20 05:40:53 GMT from Netherlands)
The only mobile device I own is an old tablet with a no longer supported android version on it. It is only used to read e-books. I am not planning on buying another mobile device, so only one choice remains.
11 • Don't worry about MDS vulnerabilities (by whoKnows on 2019-05-20 09:45:22 GMT from United Kingdom)
9 • Intel FUD (by St. Vincent)
"Why won't Distrowatch tell the truth? The MDS vulnerabilities do not affect "multiple processors", they only impact Intel chips. AMD processors are immune."
Because they don't know.
Because you don't know.
If you're talking solely about the latest one, 'ZombieLoad' ...
Because I also don't know ... and don't care any more.
If we are talking about Meltown & Spectre, all processors which were ever made and use 'hyperthreading' are vulnerable.
AMD or Intel or Qualcomm in your smartphone or the Sparc processors ...
However, it doesn't really matter that much for you and the rest of us, on our home PCs.
Those are vulnerabilities which are not very easy to exploit, there are many other easier ways to 'hack' you and the only theoretical attack vector on your private PC is through the javaScript of your web browser.
All (Google Chrome & FireFox) web browser are getting regularly patched and so, not even that is exploitable.
The problem have only the 'big players' ... Professionals (== Linux servers).
In case where multiple VM’s are running on the same host (== as good as always) and if ‘the bad guy’ starts his ‘hostile’ guest VM on the same server, it can read all (random) data of all other VM’s which run on the exact same processor core/thread in a given moment.
https://www.heise.de/newsticker/meldung/Neue-Sicherheitsluecken-in-Intel-Prozessoren-ZombieLoad-4421217.html
https://www.heise.de/ct/artikel/Updates-gegen-die-Intel-Prozessorluecken-ZombieLoad-Co-4422413.html
Spectre & Meltdown:
https://www.heise.de/security/meldung/FAQ-zu-Meltdown-und-Spectre-Was-ist-passiert-bin-ich-betroffen-wie-kann-ich-mich-schuetzen-3938146.html
https://www.heise.de/thema/Meltdown-und-Spectre
https://www.heise.de/security/meldung/Analyse-zur-Prozessorluecke-Meltdown-und-Spectre-sind-ein-Security-Supergau-3935124.html
https://www.heise.de/security/meldung/AMD-rudert-zurueck-Prozessoren-doch-von-Spectre-2-betroffen-Microcode-Updates-fuer-Ryzen-und-Epyc-in-3939975.html
https://www.heise.de/security/meldung/AMD-Prozessoren-bekommen-Windows-10-Update-gegen-Spectre-V2-Luecke-4016546.html
https://www.heise.de/select/ct/2019/3/1549002014398779
https://www.heise.de/security/meldung/Meltdown-und-Spectre-Die-Sicherheitshinweise-und-Updates-von-Hardware-und-Software-Herstellern-3936141.html
12 • GNU/Linux distribution on a mobile device (by Stan on 2019-05-20 09:48:44 GMT from Netherlands)
I'm very skeptical about this, don't get me wrong I would love to reclaim back my privacy. But mobile device is all about user experience, in which GNU/Linux usually scores very low.
We cannot get it right in a desktop / workstation, let alone a laptop. We have issues with multiple monitors, hi-dpi, battery live, sleep/hibernate, proprietary chips, and the list goes on and on and on...
13 • Mobile Device (by PatH on 2019-05-20 09:58:20 GMT from United States)
I would like to have a GNU Linux powered Kindle Fire HD8 but seems like a daunting task indeed!
14 • I want my next smartphone to have Linux (by TuxRaider on 2019-05-20 11:17:30 GMT from United States)
i would rather have a smartphone that i can install my choice of arm Linux on, i am no longer satisfied with Google's android and the corporate sponsorship it entails which means Google is doing pretty much the same thing facebook is doing, gathering your personal info and more than likely sharing it with cronies and selling it to other corporate & government entities
15 • linux on phones (by Tim on 2019-05-20 12:31:51 GMT from United States)
@12
I'm not sure that's really fair- my desktops and laptops work pretty well with Linux and have for years. They certainly work better than they did with Windows.
You're right though that the phone market is hard though, mostly because it's been deliberately set up to force people to buy new phones constantly. It's not that GNU/Linux wouldn't work well on such devices- they're designed to put barriers to this because it would let people keep phones longer.
That makes me mad, and I'd gladly buy a device that gets me off the upgrade cycle for phones the way I'm not on it for computers anymore.
Whether the market bears that out, I don't know. But it would be better.
16 • Sabayon (by Sam on 2019-05-20 12:50:00 GMT from United States)
Kind of nice and kind of sad to see the review of Sabayon's latest release. Back in my intensive distro-hopping days a few years ago, Sabayon releases were in my list of distros to try out -- usually for a few days before the number of bugs or just awkward work-arounds to getting hardware working became too long and I was back to Mint or openSUSE. Frankly, I've thought the distro was dead for the last two years - the last release was quite a while ago (giving Mageia a run for its long-in-the-tooth releases) and, as the review mentions, the Sabayon forums are a ghost town.
17 • Kernel Patches (by Winchester on 2019-05-20 13:13:19 GMT from United States)
It seems convenient to me that Solus gives updated kernels every weekend,or at least every other weekend. Right now at 5.0.16 and 5.0.15 current and 4.9.176 LTS. Painlessly and without breakage. Symlinks to the most up-to-date .... Current or LTS based on which one used at the time of applying the most recent update. The best systemD distribution in my opinion.
Void Linux kernel updates are also quite painless. Currently at 4.19.142 last I checked a few days ago. But,Void requires manual removal of old,unwanted kernels. Simple command to do it but,manual.
I am guessing that 4.19.142 + is also patched being more recent than 5.0.8 .
PClinuxOS also offers the most recent kernel but,applied by selecting in Synaptic.
All 3 seem much more convenient than the Ubuntu approach ..... which,by the way,is one of the few bases where I have experienced breakage by updating the kernel.
Alpine Linux offers a security hardened kernel but,I have not seen updates for it in some time. They also offer a "vanilla" kernel which is more frequently updated.
18 • Linux (or such) phones (by Orvan on 2019-05-20 13:14:04 GMT from United States)
I have a 'Superbook' (yes, one of the few[?] that actually got the hardware) and the thing is disappointing - but I cannot entirely blame the Superbook hardware. The software, however, needs some work, but is made necessary by the very nature of Android. The idea of having a 'phone' work as more fully User Interfaced computer has appeal. Today's phones might be 'only' as powerful as the 'day before yesterday's' computer, but those machine served. What is needed is an Operating System that isn't all-but touch-screen only and can deal with real multitasking and run not-just-phone/tablet applications. This is where, eventually, I expect the "Linux phone" of some sort to shine. The Superbook will seem quaint then (a mere 1080 screen...) but I expect someone will be along with the hardware. The 'trick' is for the 'any dang phone' and NOT "We're $COMPANY, buy OUR phone and you can use OUR laptop-oid with it." The appeal is/will be that each can be upgraded separately and independently. Lock-in doesn't serve the user, and the user pays the bills.
19 • RPM packages and Intel chips (by Jesse on 2019-05-20 14:13:39 GMT from Canada)
@4: "Distrowatch claims of "independent" is very alarming & inconsistent. Both use RPM (Red Hat) package managers, so are NOT independent, relying on RPM packages. "
Whether a distribution uses a particular package manager or package format does not determine whether the distro is independent. Lots of distros use the RPM package format without using Fedora/Red Hat packages. File archives are not tied to specific distributions.
@9: "Why won't Distrowatch tell the truth? The MDS vulnerabilities do not affect "multiple processors", they only impact Intel chips. AMD processors are immune."
No one here said whether AMD chips were affected or not. Intel makes multiple processors. And, yes, MDS does affect many processors.
20 • mandatory (by mandatory on 2019-05-20 14:45:47 GMT from United States)
@12:
"user experience"?
Get out.
21 • Linux on phones (by isndw on 2019-05-20 15:14:42 GMT from Austria)
There are more options for phones, all based on linux for what i know:
LuneOS:
https://twitter.com/webosports
Plasma Mobile:
https://www.plasma-mobile.org/
Nemo Mobile:
https://twitter.com/nemomobile
Maemo Leste:
https://maemo-leste.github.io/
22 • Mobile Linux distros (by Roland on 2019-05-20 15:18:07 GMT from United States)
I have tested LuneOS, Plasma Mobile, and UBPorts / Ubuntu Touch and currently use UBPorts on secondary devices. The first two weren't yet usable when I last tested them, but UBPorts ships a distro you can actually use daily if your requirements are simple and if you acquire one of the small number of supported devices. The user experience is good, with mature gesture navigation that other mobile OSes are only now trying to graft onto their GUI. There is no need to drop to the terminal at all in routine use as a mobile phone. The terminal is there though if you want to use it to modify the OS or just work and play with the normal GNU tools. Native apps are strictly confined and relatively small in number (though the app store is growing again), but you can install most software from the Ubuntu ARM repositories in add-on containers (not that many of them are usable on a small touch scree), and there is now experimental support for Android apps using Anbox.
For the past year and a half I have kept a couple of phones stood up with UBPorts for testing and casual use. The main thing keeping me from switching to UBPorts for my daily driver are missing E2E encryption in Telegram and Matrix, and both are being worked on. There are also MMS bugs which could be a problem, but I'm sure those will be fixed in time. Filesystem encryption isn't supported by default, but encrypting home is possible with some cryptsetup work in the terminal.
Android app integration using Anbox is still very primative, but most of the Android apps I use have UBPorts equivalents, and the ones that don't I can leave on an Android tablet at home if/when I switch for good. Anbox runs but doesn't have a lot of hardware passthrough yet, and the kernel supporting it kills my battery. The browser and mail client are both very basic, but I don't need much on a phone. Unav actually works better for me than OSMAnd does on Android. Though not nearly as precise and well-polished as the proprietary Google apps of Maps and Waze, it's more than good enough to find my way around an unfamiliar city.
Aside from the app ecosystem being small and requiring some compromises and finding alternatives (like using Fdroid instead of Google Play does), almost every significant problem (disconnecting bluetooth, camera glitches, video playback failure on some devices, and other bugs) is due to proprietary hardware, which is a problem not just for UBPorts but for all alternative OSes. For the time being, such OSes are making due with Android hardware, using various buggy kludges in order to use closed source Android drivers. That is why it is good that two non-Android options with full open source drivers should be available within the next year. Librem 5 will probably have less OS support out of the box (maybe just PureOS), but many OSes are making good progress with the PinePhone development kits.
The PinePhone should only cost $150 or so, so I expect when it ships many more developers will get interested and involved with UBPorts, LuneOS, Maemo-Leste, Plasma Mobile, Nemo, PostmarketOS, and all the other non-Android mobile Linux distros.
23 • @17 Winchester: (by dragonmouth on 2019-05-20 16:04:03 GMT from United States)
"Solus.....Right now at 5.0.16 and 5.0.15 current and 4.9.176 LTS."
PCLinuxOS offers 4.9.177 LTS and 5.1.3 current.
24 • Sabayon Linux (by Flavio on 2019-05-20 16:27:51 GMT from Brazil)
My first experience with Rigo, from March to May 2017 was not so good and I ended up without most of KDE / KWin.
So, when I installed Sabayon again, back in 2018, I have decided to use just "equo" commands and the first thing I have done was to remove Magneto / Rigo.
Sabayon keeps fine after these 6 months, even if I have done some weird experiences, such as install old Kernel 4.4.0 and then remove it ─ and manually replace Kernel 4.18 with Kernel 4.19 later.
Upgrade Kernel is not so simple as just to install a newer one. You need to make some "eselect" and to test libraries, too.
In fact, updates to Sabayon take more time than in other distros ─ but a few less time with "equo" than with Rigo, IMHO.
I also found that "equo" outputs make more sense than Rigo outputs, and there were not so many questions along this 6 months. ─ Usually, there is an option to say "Yes to all".
Indeed, even if it is a rolling-distro, its updates keep package versions a few behind those in Arch Linux or PCLinuxOS ─ maybe for more insurance and tests, or maybe just because Sabayon has a smaller team.
25 • Open Source Phone (by isndw on 2019-05-20 16:41:40 GMT from Austria)
Here is also an open source phone:
https://necunos.com/community/
First batch has ended, but there will be a second one.
26 • Mobile Linux (by Dr. E.S. Ktorp on 2019-05-20 16:55:32 GMT from United States)
Though they will never admit it today, it's obvious that Gnome and Canonical had some Googley-eyed visions of sailing their 'flagships' in to mobile waters, but something behind the scenes apparently couldn't float their boats. Maybe if they hadn't been so arrogant and combined their efforts, they could've enticed manufacturers in to software/hardware deals, but instead, Linux desktop users are once again left cleaning up the debris, for years, while the devotees sing songs of praise and pretend that Gnome Shell (and Unity) was always intended for desktop use.
Even Red Hat ships a 'Classic' Gnome 2 styled version of Gnome 3. That alone should tell you what they really think of Gnome Shell and for whom it was truly designed.
How could they have miscalculated such a humongous blunder. It almost seems intentional. Would Red Hat & Canonical torpedo the Linux ecosphere to protect the big business status quo, that dominates the computer & electronics industries? I sure wouldn't put it past them.
27 • Linux on mobile (by Friar Tux on 2019-05-20 18:04:03 GMT from Canada)
Nope, none of the above. I know how much a mobile device should actually cost. Do a simple material and labour comparison with other devices/appliances. The prices asked are WAY too high. Call me cheap, but there is no way I would dish out that kind of money for a mobile.
Having said that, I do have an old Blackberry Playbook that is still going strong that I have wanted to switch to a Linux OS. Haven't found a way to do that, yet. And I've read that it can't be done as the OS is locked to the hardware.
28 • cost (by Tim on 2019-05-20 18:49:11 GMT from United States)
@27
a low end Android smartphone can be had for about $30 and is actually a pretty decent user experience. Only the camera is junk at that pricepoint.
There are many reasons to be opposed to either iOS or Android from a privacy perspective, but I think saying they're overpriced is a bit farfetched at this point. I bought a ZTE burner phone two years ago and have kept it because I liked it so much.
29 • Sabayon review (and remarks here in comments) (by Jordan on 2019-05-20 20:03:12 GMT from United States)
I certainly agree with what's being said about Sabayon here: that it has always "had promise" but honestly just does not deliver, even on the basic level of a successful installation in some versions over the years.
Like others here, I keep trying it and messing with it then having to dump it, "knowing" that it's got to get better at some point and may even feel complete at some point.
That's been for YEARS. It must be a daunting project, trying to make Gentoo a "just works out of the box" distro fork (or sibling or "based on" or whatever). As mentioned here also, there are other Gentoo based distros, but Sabayon has something very intriguing in its spiel and its hope and overall look, etc.
Good luck, Sabayon devs; many of us await its completion as a reliable desktop.
30 • Linux on a mobile device (by Lord Mozart on 2019-05-20 20:03:43 GMT from United Kingdom)
I'd love to give running a Linux distro (not including Adroid), on a mobile device. However, I have absolutely no clue how to do it. With all the various devices out there in circulation, is it possible to do a tutorial? If so, how soon can you do it? :)
31 • Installing UBports (by Jesse on 2019-05-20 20:13:50 GMT from Canada)
@30: We wrote a tutorial on installing UBports on supported devices two years ago: https://distrowatch.com/weekly.php?issue=20170130#tips
These days a tutorial typically isn't needed. If you have a device compatible with UBports, you download their installer, plug in your phone and launch the installer. It takes care of the rest.
32 • encryption and calamares (by lupus on 2019-05-20 20:26:16 GMT from Germany)
There seem to be a known issue with the calamares installer not telling grub the correct UUID for booting from an encrypted disk. Encountered the same Problem on Arcolinux, what a pity!
33 • Mobile prices (by Friar Tux on 2019-05-20 20:38:56 GMT from Canada)
@28 (Tim) The $30 dollar price you mentioned is good. Anything over $100 is overpriced. And paying $1200 for something that will be out of date even in 5 years - well, this is a 'family' site so I'll hold my tongue. Again, do a material and labour study on mobiles as compared to the material and labour in other small electronic items/appliances.
34 • /e/ solutions mobile (by aguador on 2019-05-20 22:00:49 GMT from Bulgaria)
I recently became aware of another mobile entry from Gail Duval, founder of Mandrake: /e/ (https://e.foundation/). This was forked from LineageOS, is privacy oriented and has its own selected apps. Of all the things I have seen, it is the one that gives me the best feeling going forward. Sailfish had great potential, but has not been able to fight the Google head winds. The Librem 5 project is a great one, but the entry will simply be too expensive for most people, like the company's laptops.
One of the biggest problems remains the fragmentation in hardware. Unlike PCs there is no standard, so if you are not using a top selling device it is unlikely that there is an easy to install Linux-based OS other than Android to be had.
With the escalating trade war and moves against Huawei, there may be opportunities for non-Google players to enter. However, the company already has its own OS for wearables, so the trade war may give it a boost rather than providing an opportunity for the options presented here.
35 • CPU vulnerabilities of the past years (by Mike on 2019-05-20 22:07:28 GMT from Germany)
@whoKnows (#11): You're wrong and St. Vincent (#9) is correct. As of today, 05/21/2019, the known situation regarding the most popular CPU vulnerabilities of the past years according to the sources below is:
Meltdown (GPZ V3) / Rogue Data Cache Load (RDCL),
CVE-2017-5754,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Spectre V1 / 1.0 / Bounds Check Bypass (BCB)
CVE-2017-5753,------------------------------------------------------------------> Intel: vulnerable, AMD: vulnerable
Spectre V2 / Branch Target Injection (BTI),
CVE-2017-5715,------------------------------------------------------------------> Intel: vulnerable, AMD: vulnerable
Spectre V1.1 / Bounds Check Bypass Store (BCBS),
CVE-2018-3693,------------------------------------------------------------------> Intel: vulnerable, AMD: vulnerable
Spectre(-NG) V3a / Rogue System Register Read (RSRR),
CVE-2018-3640,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Spectre-NG: Foreshadow / L1 Terminal Fault-SGX,
CVE-2018-3615,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Spectre-NG: Foreshadow-NG / L1 Terminal Fault-OS Kernel/SMM,
CVE-2018-3620,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Spectre(-NG) V4 / Speculative Store Bypass (SSB),
CVE-2018-3639,------------------------------------------------------------------> Intel: vulnerable, AMD: vulnerable
Foreshadow-NG / L1 Terminal Fault-VMM,
CVE-2018-3646,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Spectre-NG 3 / Lazy FPU state leak,
CVE-2018-3665,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
MDS-Fallout,
CVE-2018-12126,-----------------------------------------------------------------> Intel: vulnerable, AMD: not affected
RIDL-CVE-2018-12127,
CVE-2018-12127,-----------------------------------------------------------------> Intel: vulnerable, AMD: not affected
RIDL-CVE-2019-11091,
CVE-2019-11091,-----------------------------------------------------------------> Intel: vulnerable, AMD: not affected
SPOILER,
CVE-2019-0162,------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
TLBleed,
CVE ID unknown or n. a.,--------------------------------------------------------> Intel: vulnerable, AMD: not affected
ZombieLoad,
CVE-2018-12130,-----------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Spectre V1.2 / Read-only protection bypass (RPB),
CVE n. a.,----------------------------------------------------------------------> Intel: vulnerable, AMD: not affected
Alone this list states a vulnerability ratio corresponding to Intel:AMD = 17:4. And of course not everybody takes these vulnerabilities and data leaks as easy as you and "doesn't care" - for professional and/or for personal reasons.
Even if you have nothing important or private on your machines, the corporations, shops, (health) insurances, authorities, cloud storage and VM users and everybody else with whom you interact as a human being and member of a common present days computerized society very likely will have.
Of course, there are plenty of other vulnerabilities and vulnerable systems / system parts (just think of the "Intel Management Engine" e. g.). But why not focus on the known facts and at least try to always get the best security, integrity and protection possible - even if it comes with quiet some but rewarding effort.
Besides that and not least, mitigations - where possible - can reduce performance very nastily. It's much better to have hardware and processors that don't need those often crippling solutions in the first place.
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)
https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)
https://en.wikipedia.org/wiki/Microarchitectural_Data_Sampling
https://en.wikipedia.org/wiki/TLBleed
https://en.wikipedia.org/wiki/SPOILER_(security_vulnerability)
https://www.amd.com/en/corporate/product-security
https://www.thomas-krenn.com/en/wiki/Safety_Instructions_for_Spectre-NG_(Spectre_Next_Generation)
https://en.wikipedia.org/wiki/Intel_Management_Engine
36 • .rpm vs .deb @4 (by Titus_Groan on 2019-05-21 03:08:44 GMT from New Zealand)
RPMs are only different from .debs, in that they are a different compressed file format.
The author/packager determines any dependencies required, so, true, a Redhat sourced RPM may or may not work in another RPM distro, if the required dependencies are un-available.
Likewise, some .debs that are distro specific may or may not work in a .deb based distro different from the authors/packagers target distro.
IIRC, xed and mdm packages from LinuxMint will break other .deb based distros if installed.
37 • Linux Mobile OSs (by Alburgheiro on 2019-05-21 03:47:25 GMT from Russia)
The developers of Linux mobile OSs might want to contact Huawei. A huge, unexpected, opportunity seems to have appeared.
38 • Just think (by whoKnows on 2019-05-21 08:25:43 GMT from United Kingdom)
You're simply missing the point.
'Vulnerability ratio' itself is irrelevant. Having 100 security issues which get fixed is better than having one single which didn't get fixed. Numbers are just numbers and all (good) processors are having the same issues.
https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/
It also doesn't help anything when AMD is immune to Meltdown -- that's SW fixable issue and exactly what Google and Mozilla did.
https://www.techarp.com/articles/meltdown-spectre-cpu-flaws/
And of course AMD has fewer issues -- they had less different models, their models were more primitively built and had vastly inferior performance because of making bad use of hyper threading.
https://www.extremetech.com/wp-content/uploads/2018/02/11-21-16-AMD-pic-2.png
https://www.extremetech.com/computing/285280-amd-reports-improved-market-share-across-all-segments-in-q4
I'd even bet that there are more yet undiscovered vulnerability issues in AMD processors but, why bother looking for vulnerability issues in some old and technically inferior processors with irrelevant market share?
These vulnerabilities and data leaks are actually completely irrelevant for home users -- there's nothing you or anybody else can do to protect your "oh, so secret and private" data.
I recently traveled to U.S.A. -- the very first thing they did was to make my retina (== eyes) scan and take my fingerprints. My biometric passport contains most of that data too.
My name, my face and my biography are printed in a couple of books. My name and my address are published in a local telephone book. My birthday and my "life", my birth day, family status and such you can get on Facebook.
A copy of my passport, my driving license, my insurance numbers and even a paper copy of my fingerprints are all in Google Drive, Microsoft OneDrive and Yandex Disk -- unencrypted, of course.
"Even if you have nothing important or private on your machines, the corporations, shops, (health) insurances, authorities, cloud storage and VM users and everybody else with whom you interact as a human being and member of a common present days computerized society very likely will have."
So what? Of course they have it and imagine -- I'm still alive and nobody yet hacked my bank account.
When I interact with the authorities, (health) insurances, doctors and lawyers -- it all goes unencrypted (== 'postcard') over Google Mail, Microsoft Mail or Yandex Mail -- they don't accept any encrypted communication/mail.
Or shall I now be concerned that Google lists me every single thing that I ever bought in last 15 years, in easy readable list, that's made out of scanning my mail? At least, I don't need to search the pile of paper when I need proof on when something was bought.
The local supermarket has, by the way, same such list with every single purchase I ever made, be it a bread or butter -- so what? Shall I stop eating?
The only way to protect your 'digital life' is to stop using the computer and internet. The only problem -- not even that is any protection while ...
Each time I go to get another SIM card for a phone, there's another copy of my ID card, scanned and printed out and it lands on an unprotected pile of paper ...
All those typewriter letters are getting scanned by somebody in some office, and they again land in some archive or cloud and get compromised, at one or the other point.
Every single (paper) letter (== old-fashioned mail over the local post office) is getting scanned to collect 'meta-data' -- who send a letter to whom.
Believe me, some very hard to exploit processor vulnerability is the smallest problem in your life.
39 • Peppermint OS 10 (by Niyas C on 2019-05-21 08:54:40 GMT from Singapore)
Comparing to previous versions, I feel Peppermint OS 10 is much more polished and it provides a smooth user experience. However, I would love to have a light color theme by default.
40 • Sabayon - non-bleeding-edge rolling distro; (by Hoos on 2019-05-21 11:49:53 GMT from Singapore)
@24 said: " when I installed Sabayon again, back in 2018, I have decided to use just "equo" commands and the first thing I have done was to remove Magneto / Rigo....
Upgrade Kernel is not so simple as just to install a newer one. You need to make some "eselect" and to test libraries, too...
I also found that "equo" outputs make more sense than Rigo outputs, and there were not so many questions along this 6 months. ─ Usually, there is an option to say "Yes to all".
Indeed, even if it is a rolling-distro, its updates keep package versions a few behind those in Arch Linux or PCLinuxOS ─ maybe for more insurance and tests, or maybe just because Sabayon has a smaller team."
My install of Sabayon has been rolling for about 4 years now, without issue. I didn't have a problem with installation when I first installed Sabayon, but things may have changed now.
I'm not concerned that it's not bleeding edge since you will get the newer Gnome or Plasma or whatever in due course, just at a more leisurely pace.
I chose to go with the KDE Plasma version since I associated Sabayon with KDE when I first tried it out around 2009.
As for kernel installation, Rigo the graphical package manager now makes it easy to install new series of kernels with a dedicated "kernel" category. Previously this category didn't exist. I tested Rigo's kernel installation and it was straightforward. Of course, if user @24 has removed Rigo, they won't be able to make use of that.
While I upgrade my system via the terminal with equo, Rigo has its uses and plus points, namely installation/removal of individual packages, including the kernel.
41 • Sabayon Linux (by Flavio on 2019-05-21 15:44:18 GMT from Brazil)
@40: You are right. Rigo could have helped me in cases of install / remove Kernels.
42 • Linux on mobile devices (by Joerg on 2019-05-21 16:41:11 GMT from Germany)
Im waiting for a long time a suitable mobile open source project will arrive.
The market is still to hot and contested to deliver such a solution.
May be the ban on US supplies to Huawei will do us a favour.
The Huawei case shows what can happen if you misbehave in the eye of your american master and gives a warning to everyone else outside the US.
The company in question should counter that strike by developing an open source mobile system that our game kids understand. It is capable of doing so.
Instead of that they will bring up a Android clone with chinese characteristics, means that the data will end up with the chinese masters.
Another chance is gone
So the times are not good, the circumstances are hard but as Victor Hugo once twittert:
Nothing is more powerfull than a idea whose time had come
Joerg
43 • rpm and deb (by tim on 2019-05-21 23:40:43 GMT from United States)
@36 continuing what you explained, we should be mindful that a deb file is targeted at systems running a given release of a given distro. A deb file packaged for use on "Debian Stretch" systems may not interact flawlessly with the shared libraries present on a "Debian Jessie" system or a "Ubuntu 19.04" system or a "Ubuntu 18.xx" system...
44 • Linux on mobile devices (by OstroL on 2019-05-22 15:17:53 GMT from Poland)
Used Ubuntu from UBports for sometime on a N5. The N5 was not a terribly used device; the battery stayed longer with the original Android it came with. Ubports installed well, but the battery drying out quite fast, even idling. Then, installed Android Pie 9 fork from XDA, with which the battery stayed much longer. The community made Android was without much Google centred and, in a real way, that OS is a open source one. Interestingly, the N5 is more responsive and faster.
I can, of course, flash the newest UBports any time, but I don't think, the battery life had become better. Linux in general is quite terrible on battery life, but Android appears to find a solution for that somehow. The Unix based iOS also can get a lot out of the battery. I also have a N6 (still on guarantee) with Nitrogen OS (Android 9), which works quite nice, with a pretty good battery life. It is interesting that I got both of them at a fraction of its release price!
Now, Android is open source, and there are many devs at XDA creating lovely OS out of it. Android is based on Linux (Gentoo), so we really shouldn't attack it. If you really want, you can stay away from Google with those OSs. I personally don't have anything against Google. I don't consider it is spying on me, but it helps me in many ways.
The problem with us Linux guys is that we tend to do something against another, who had done something with Linux. Some people wants to create a phone to go against another, for example Google. You waste quite a lot of energy just to be against. And, that way, nothing worthwhile is created. I believe Librem 5 to become a flop -- original thought of creating it was hate, or to do something to hurt someone else.
45 • Linux on mobile devices (by Ricardo on 2019-05-23 03:27:38 GMT from Argentina)
I voted "I have run a GNU/Linux distro in the past" because I own a Nokia N900 (which is absolutely amazing, too bad it only supports 2G in my country), a gorgeous Nokia N9 and an HP TouchPad tablet dual booting WebOS and LuneOS.
Sadly, only the N900 is still functional, but I had great times with the three devices.
But I also "plan to run a GNU/Linux distro", as I'm eagerly awaiting a Librem 5 to try as many mobile distros as possible :)
Oh, I also tried a Sailfish community edition on a Nexus 5, pretty interesting mobile OS.
Cheers.
46 • @45 Sailfish OS on N5 (by OstroL on 2019-05-23 08:58:12 GMT from Poland)
"Oh, I also tried a Sailfish community edition on a Nexus 5, pretty interesting mobile OS."
This is interesting. I cannot find this community edition to flash on N5. Would be nice, if you could direct us to it, a link if possible. Or a how to. Thanks!
47 • Mobile Phones (by Jim on 2019-05-23 10:36:11 GMT from United States)
Until major carriers offer some other Linux operating system than Android I will be forced to use that, I do not have the technical expertise to install any other system on my phone.
48 • advantage of open-source mobile OS (by Tim on 2019-05-24 09:08:16 GMT from United States)
@44
I mostly agree with you about how we fight each other more often than we should and it holds us back. But I think having a truly open source OS for mobile available is essential for two reasons.
1.) I'm starting to get very concerned about the privacy implications of phones recording ambient audio at all times waiting for me to ask them to do something. I think an open source OS would be much easier to control and audit what is happening with this data, and to uninstall any such software if we want to. Right now we're kind of at the mercy of Google, Apple, our carrier, and whoever made our phone. I don't inherently distrust them, I just want a bit more power.
2.) Every smartphone I've owned since 2012 is still usable in some way or another (I guess except the iPhone 5s I sent through the washing machine in a pocket.) But especially in the non-flagship Android world, most of them only got one update over their entire lifetimes. I think this is deliberate and meant to get us to replace phones more often than necessary. A viable mobile GNU/Linux system would presumably have ports to keep older compatible phones running longer.
49 • open-source mobile OS (by Euler on 2019-05-24 17:27:55 GMT from Austria)
The main obstacle for any Android competitor, open source or closed source is the Google store. Google provides the app developers with a opportunity to earn money. To do so the Store must be closed source and linked to the other Google services.
Open source apps can provide all basic functions, but do not offer the enormous choice I have with Google. I believe the Google monopoly (mobile apps and advertising) must be broken, but neither the EU nor the US are willing to do so.
50 • Android (by Andy on 2019-05-25 03:09:38 GMT from United Kingdom)
@48 -Disabling the always-on microphone is really not so difficult. Settings>Apps>Google>Permissions, and toggle "microphone to "off." I keep mine off because I don't use those voice functions, and it's annoying when it pops up offering help unasked, which is often enough.
Anyone wanting to keep their Android phones updated for longer times would do well to search Google, of course. Usually, the closer you get to Google's stock Android, (including Google's own branded hardware) the better off you will be. Also, here's quite a variety of custom ROMs out there. Research on hardware needed for this too. Avoid hardware locked to an ISP or phone service provider. I'm running Cyanogen/Lineage 15 (Oreo) on a Samsung tablet from 2014. Access to Google Play apps, which are really needed for most things can be downloaded separately. On the other hand, someone brought me the same tablet branded by Verizon, and there's nothing can be done with it at this time.
I'd also like to try an full open-source OS. It's possible now, mostly on limited and older phones, (and new promises) but I've found no compelling reason to spend the money and time or bear with the inconvenience.
51 • Ubuntu Touch on Nexus 4 (by Simon on 2019-05-25 08:14:07 GMT from United Kingdom)
I installed Ubuntu Touch to a Nexus 4 without any trouble or issues - escaping the prying eyes of Google and Apple.
It works fine and I have no issues with it. Mind you, I don't spend that much time on mobiles and use it mainly for texts, phone calls and taking pictures.
As a bonus, it runs in my native language (Welsh) without any problems. How cool is that?
Number of Comments: 51
Display mode: DWW Only • Comments Only • Both DWW and Comments
| | |
| TUXEDO |
TUXEDO Computers - Linux Hardware in a tailor made suite
Choose from a wide range of laptops and PCs in various sizes and shapes at TUXEDOComputers.com. Every machine comes pre-installed and ready-to-run with Linux. Full 24 months of warranty and lifetime support included!
Learn more about our full service package and all benefits from buying at TUXEDO.
|
| *NEW* NovaCustom |
NovaCustom PrivacyGuard Laptops - Escape from Big Tech
The NovaCustom PrivacyGuard Laptop is ideal for anyone who prioritizes privacy. Comes with Dasharo coreboot open source firmware and Zorin OS Pro, free from influence of Big Tech.
|
| Archives |
| • Issue 1173 (2026-05-18): Sylve on FreeBSD, the benefit of BleachBit, Debian commits to reproducible builds, Debian publishes updated install media, Haiku introduces SMP support on ARM64 processors, Rocky Linux creates opt-in security repository, Fedora reconsiders AI tools, KDE receives generous donation |
| • Issue 1172 (2026-05-11): Fedora 44, dealing with extra fonts, Fedora plans to provide AI tools, problems with Ubuntu's new coreutils, TrueNAS extends its development cycle, postmarktetOS improves the boot splash screen, Redox ports tmux |
| • Issue 1171 (2026-05-04): Xubuntu 26.04, extending memory with VRAM, Ubuntu plans AI features, Devuan developer forks GTK2, Mint introduces hardware enablement builds, Linux running on a PlayStation 5, local kernel exploit found in Linux |
| • Issue 1170 (2026-04-27): ENux 5.2.1, picking a second distro, AlmaLinux expands CPU support, FreeBSD publishes Status Report, Ubuntu MATE skips 26.04 release |
| • Issue 1169 (2026-04-20): Lakka 6.1, free software and source-based distributions, FreeBSD Foundation publishes compatible laptop list, Debian holds Project Leader election, Haiku progresses ARM64 port, Mint to extend development cycle, Linux 7.0 released |
| • Issue 1168 (2026-04-13): pearOS 2026.03, EndeavourOS 2026.03.06, which distros are adopting age verification, Arch adjusts its firewall packages, Linux dropping i486 support, Red Hat extends its release cycle, Debian's APT introduces rollbacks, Redox improves its scheduler |
| • Issue 1167 (2026-04-06): Origami Linux 2026.03, answering questions for Linux newcomers, Ubuntu MATE seeking new contributors, Ubuntu software centre is expanding Deb support, FreeBSD fixes forum exploit, openSUSE 15 Leap nears its end of life |
| • Issue 1166 (2026-03-30): NetBSD jails, publishing software for Linux, Ubuntu joins Rust Foundation, Canonical plans to trim GRUB features, Peppermint works on new utilities, PINE64 shows off open hardware capabilities |
| • Issue 1165 (2026-03-23): Argent Linux 1.5.3, disk space required by Linux, Manjaro team goes on strike, AlmaLinux improves NVIDIA driver support and builds RISC-V packages, systemd introduces age tracking |
| • Issue 1164 (2026-03-16): d77void, age verification laws and Linux, SUSE may be for sale, TrueNAS takes its build system private, Debian publishes updated Trixie media, MidnightBSD and System76 respond to age verification laws |
| • Issue 1163 (2026-03-09): KaOS 2026.02, TinyCore 17.0, NuTyX 26.02.2, Would one big collection of packages help?, Guix offers 64-bit Hurd options, Linux communities discuss age delcaration laws, Mint unveils new screensaver for Cinnamon, Redox ports new COSMIC features |
| • Issue 1162 (2026-03-02): AerynOS 2026.01, anti-virus and firewall tools, Manjaro fixes website certificate, Ubuntu splits firmware package, jails for NetBSD, extended support for some Linux kernel releases, Murena creating a map app |
| • Issue 1161 (2026-02-23): The Guix package manager, quick Q&As, Gentoo migrating its mirrors, Fedora considers more informative kernel panic screens, GhostBSD testing alternative X11 implementation, Asahi makes progress with Apple M3, NetBSD userland ported, FreeBSD improves web-based system management |
| • Issue 1160 (2026-02-16): Noid and AgarimOS, command line tips, KDE Linux introduces delta updates, Redox OS hits development milestone, Linux Mint develops a desktop-neutral account manager, sudo developer seeks sponsorship |
| • Issue 1159 (2026-02-09): Sharing files on a network, isolating processes on Linux, LFS to focus on systemd, openSUSE polishes atomic updates, NetBSD not likely to adopt Rust code, COSMIC roadmap |
| • Issue 1158 (2026-02-02): Manjaro 26.0, fastest filesystem, postmarketOS progress report, Xfce begins developing its own Wayland window manager, Bazzite founder interviewed |
| • Issue 1157 (2026-01-26): Setting up a home server, what happened to convergence, malicious software entering the Snap store, postmarketOS automates hardware tests, KDE's login manager works with systemd only |
| • Issue 1156 (2026-01-19): Chimera Linux's new installer, using the DistroWatch Torrent Corner, new package tools for Arch, Haiku improves EFI support, Redcore streamlines branches, Synex introduces install-time ZFS options |
| • Issue 1155 (2026-01-12): MenuetOS, CDE on Sparky, iDeal OS 2025.12.07, recommended flavour of BSD, Debian seeks new Data Protection Team, Ubuntu 25.04 nears its end of life, Google limits Android source code releases, Fedora plans to replace SDDM, Budgie migrates to Wayland |
| • Issue 1154 (2026-01-05): postmarketOS 25.06/25.12, switching to Linux and educational resources, FreeBSD improving laptop support, Unix v4 available for download, new X11 server in development, CachyOS team plans server edtion |
| • Issue 1153 (2025-12-22): Best projects of 2025, is software ever truly finished?, Firefox to adopt AI components, Asahi works on improving the install experience, Mageia presents plans for version 10 |
| • Issue 1152 (2025-12-15): OpenBSD 7.8, filtering websites, Jolla working on a Linux phone, Germany saves money with Linux, Ubuntu to package AMD tools, Fedora demonstrates AI troubleshooting, Haiku packages Go language |
| • Issue 1151 (2025-12-08): FreeBSD 15.0, fun command line tricks, Canonical presents plans for Ubutnu 26.04, SparkyLinux updates CDE packages, Redox OS gets modesetting driver |
| • Issue 1150 (2025-12-01): Gnoppix 25_10, exploring if distributions matter, openSUSE updates tumbleweed's boot loader, Fedora plans better handling of broken packages, Plasma to become Wayland-only, FreeBSD publishes status report |
| • Issue 1149 (2025-11-24): MX Linux 25, why are video drivers special, systemd experiments with musl, Debian Libre Live publishes new media, Xubuntu reviews website hack |
| • Issue 1148 (2025-11-17): Zorin OS 18, deleting a file with an unusual name, NetBSD experiments with sandboxing, postmarketOS unifies its documentation, OpenBSD refines upgrades, Canonical offers 15 years of support for Ubuntu |
| • Issue 1147 (2025-11-10): Fedora 43, the size and stability of the Linux kernel, Debian introducing Rust to APT, Redox ports web engine, Kubuntu website off-line, Mint creates new troubleshooting tools, FreeBSD improves reproducible builds, Flatpak development resumes |
| • Issue 1146 (2025-11-03): StartOS 0.4.0, testing piped commands, Ubuntu Unity seeks help, Canonical offers Ubuntu credentials, Red Hat partners with NVIDIA, SUSE to bundle AI agent with SLE 16 |
| • Issue 1145 (2025-10-27): Linux Mint 7 "LMDE", advice for new Linux users, AlmaLinux to offer Btrfs, KDE launches Plasma 6.5, Fedora accepts contributions written by AI, Ubuntu 25.10 fails to install automatic updates |
| • Issue 1144 (2025-10-20): Kubuntu 25.10, creating and restoring encrypted backups, Fedora team debates AI, FSF plans free software for phones, ReactOS addresses newer drivers, Xubuntu reacts to website attack |
| • Issue 1143 (2025-10-13): openSUSE 16.0 Leap, safest source for new applications, Redox introduces performance improvements, TrueNAS Connect available for testing, Flatpaks do not work on Ubuntu 25.10, Kamarada plans to switch its base, Solus enters new epoch, Frugalware discontinued |
| • Issue 1142 (2025-10-06): Linux Kamarada 15.6, managing ZIP files with SQLite, F-Droid warns of impact of Android lockdown, Alpine moves ahead with merged /usr, Cinnamon gets a redesigned application menu |
| • Issue 1141 (2025-09-29): KDE Linux and GNOME OS, finding mobile flavours of Linux, Murena to offer phones with kill switches, Redox OS running on a smartphone, Artix drops GNOME |
| • Issue 1140 (2025-09-22): NetBSD 10.1, avoiding AI services, AlmaLinux enables CRB repository, Haiku improves disk access performance, Mageia addresses service outage, GNOME 49 released, Linux introduces multikernel support |
| • Issue 1139 (2025-09-15): EasyOS 7.0, Linux and central authority, FreeBSD running Plasma 6 on Wayland, GNOME restores X11 support temporarily, openSUSE dropping BCacheFS in new kernels |
| • Issue 1138 (2025-09-08): Shebang 25.8, LibreELEC 12.2.0, Debian GNU/Hurd 2025, the importance of software updates, AerynOS introduces package sets, postmarketOS encourages patching upstream, openSUSE extends Leap support, Debian refreshes Trixie media |
| • Issue 1137 (2025-09-01): Tribblix 0m37, malware scanners flagging Linux ISO files, KDE introduces first-run setup wizard, CalyxOS plans update prior to infrastructure overhaul, FreeBSD publishes status report |
| • Issue 1136 (2025-08-25): CalyxOS 6.8.20, distros for running containers, Arch Linux website under attack,illumos Cafe launched, CachyOS creates web dashboard for repositories |
| • Issue 1135 (2025-08-18): Debian 13, Proton, WINE, Wayland, and Wayback, Debian GNU/Hurd 2025, KDE gets advanced Liquid Glass, Haiku improves authentication tools |
| • Issue 1134 (2025-08-11): Rhino Linux 2025.3, thoughts on malware in the AUR, Fedora brings hammered websites back on-line, NetBSD reveals features for version 11, Ubuntu swaps some command line tools for 25.10, AlmaLinux improves NVIDIA support |
| • Issue 1133 (2025-08-04): Expirion Linux 6.0, running Plasma on Linux Mint, finding distros which support X11, Debian addresses 22 year old bug, FreeBSD discusses potential issues with pkgbase, CDE ported to OpenBSD, Btrfs corruption bug hitting Fedora users, more malware found in Arch User Repository |
| • Issue 1132 (2025-07-28): deepin 25, wars in the open source community, proposal to have Fedora enable Flathub repository, FreeBSD plans desktop install option, Wayback gets its first release |
| • Issue 1131 (2025-07-21): HeliumOS 10.0, settling on one distro, Mint plans new releases, Arch discovers malware in AUR, Plasma Bigscreen returns, Clear Linux discontinued |
| • Issue 1130 (2025-07-14): openSUSE MicroOS and RefreshOS, sharing aliases between computers, Bazzite makes Bazaar its default Flatpak store, Alpine plans Wayback release, Wayland and X11 benchmarked, Red Hat offers additional developer licenses, openSUSE seeks feedback from ARM users, Ubuntu 24.10 reaches the end of its life |
| • Issue 1129 (2025-07-07): GLF OS Omnislash, the worst Linux distro, Alpine introduces Wayback, Fedora drops plans to stop i686 support, AlmaLinux builds EPEL repository for older CPUs, Ubuntu dropping existing RISC-V device support, Rhino partners with UBports, PCLinuxOS recovering from website outage |
| • Issue 1128 (2025-06-30): AxOS 25.06, AlmaLinux OS 10.0, transferring Flaptak bundles to off-line computers, Ubuntu to boost Intel graphics performance, Fedora considers dropping i686 packages, SDesk switches from SELinux to AppArmor |
| • Issue 1127 (2025-06-23): LastOSLinux 2025-05-25, most unique Linux distro, Haiku stabilises, KDE publishes Plasma 6.4, Arch splits Plasma packages, Slackware infrastructure migrating |
| • Issue 1126 (2025-06-16): SDesk 2025.05.06, renewed interest in Ubuntu Touch, a BASIC device running NetBSD, Ubuntu dropping X11 GNOME session, GNOME increases dependency on systemd, Google holding back Pixel source code, Nitrux changing its desktop, EFF turns 35 |
| • Issue 1125 (2025-06-09): RHEL 10, distributions likely to survive a decade, Murena partners with more hardware makers, GNOME tests its own distro on real hardware, Redox ports GTK and X11, Mint provides fingerprint authentication |
| • Issue 1124 (2025-06-02): Picking up a Pico, tips for protecting privacy, Rhino tests Plasma desktop, Arch installer supports snapshots, new features from UBports, Ubuntu tests monthly snapshots |
| • Issue 1123 (2025-05-26): CRUX 3.8, preventing a laptop from sleeping, FreeBSD improves laptop support, Fedora confirms GNOME X11 session being dropped, HardenedBSD introduces Rust in userland build, KDE developing a virtual machine manager |
| • Issue 1122 (2025-05-19): GoboLinux 017.01, RHEL 10.0 and Debian 12 updates, openSUSE retires YaST, running X11 apps on Wayland |
| • Full list of all issues |
| Star Labs |
Star Labs - Laptops built for Linux.
View our range including the highly anticipated StarFighter. Available with coreboot open-source firmware and a choice of Ubuntu, elementary, Manjaro and more. Visit Star Labs for information, to buy and get support.
|
| Random Distribution | 
Cool Linux CD
Cool Linux was part of the LINUX EMERGENCY CD project and was based on Red Hat Linux. It was a bootable, live Linux CD with NVidia drivers, Blender, VMware (trial), OpenOffice and plenty of other software.
Status: Discontinued
|
| TUXEDO |
TUXEDO Computers - Linux Hardware in a tailor made suite
Choose from a wide range of laptops and PCs in various sizes and shapes at TUXEDOComputers.com. Every machine comes pre-installed and ready-to-run with Linux. Full 24 months of warranty and lifetime support included!
Learn more about our full service package and all benefits from buying at TUXEDO.
|
| Star Labs |
Star Labs - Laptops built for Linux.
View our range including the highly anticipated StarFighter. Available with coreboot open-source firmware and a choice of Ubuntu, elementary, Manjaro and more. Visit Star Labs for information, to buy and get support.
|
|
• 
• 
• 
• 
• 
• 
• 
