 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 • Linux Mint 22 (by penguinx86 on 2024-07-29 02:01:59 GMT from United States)
I installed Linux Mint 22 Xfce Edition. The install process went smoothly and everything works great! No problems detecting my wifi adapter.
2 • Linux Mint Upgrades (by Sam Crawford on 2024-07-29 04:16:38 GMT from United States)
This morning I upgraded two LM 21.3 machines to LM 22 and the upgrades went well with the only exception is that some of the Flatpak app configurations were lost and I had to set them up again when I opened the apps.
I also installed LM 22 from a USB drive to a laptop yesterday and everything went well.
Overall I'm pleased with the results.
3 • Automatic updates (by Guido on 2024-07-29 06:36:29 GMT from Philippines)
Does your home computer have automatic updates enabled? Yes, because I use Snaps, which receive automatic updates. This means I cannot influence the browser updates. It should be similar with Flatpaks. But neither is active at the kernel level.
4 • systemd feature "Automatic boot assessment" (by Mark Rijckenberg on 2024-07-29 06:56:48 GMT from Finland)
GNU/Linux distributions can protect themselves against Crowdstrike crashes by enabling the systemd feature "Automatic boot assessment". This feature is being enabled on NixOS unstable and will be available to "NixOS Unstable" users in the coming days.
See https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/
5 • Linux Mint 22 (by kc1di on 2024-07-29 11:06:48 GMT from United States)
Did a fresh install of Mint 22 and all works well on my t-450 machine.
only problems were a couple of third party programs i use, which I install via ppa's did not work ppa's need updating so will have to wait until that happens. But Mint itself is running smooth and stable. Good release.
6 • Automatic Updates - No* & Mint (by Bernie on 2024-07-29 15:20:12 GMT from France)
No* ...and yes... I picked up the nasty habit of installing all recommended updates every time. Simply because I don't know every piece of software on my computer and would hate to be left unsecured by not updating. After-all, I'm an amateur user, not a full blown system admin.
So No, not automatic, I used to wait a week, check the forums and manually authorize all the updates. Then I got lazy, still waited a week but didn't do any of the research. Finally, earlier this year, a kernel update for Mint 21 broke my system... a week or so after it was released. Turns out the problem was a well documented AMD Ryzen bug, my system recognized my hardware and yet still proposed the incompatible update. Now I'm back to my wait a week and see habit. When I brought that point up in a user chat, I was just told to "git gud".
I'd also like to point out that earlier this year, I received a proposed update for Intel microcode... on that same AMD laptop.
Seconday point, when I first started with Mint (14? 17?) I don't remember ever having as many issues getting my hardware to work as with Mint 21. Sure I'm not running a business computer anymore but my hardware's easily 5 years old.
Mint's great, I learned a lot, but those unneeded updates are starting to make me look elsewhere for my next OS. Something with either better or minimal update support so I know what's expected of me but this in-between stuff really rubbing me the wrong way.
7 • Crowdstrike crashes (by lincoln on 2024-07-29 18:08:45 GMT from Brazil)
It's amazing how people and institutions are fooled by sellers of "firewalls", "antivirus systems", ..., "intrusion detection systems", relying on solutions that don't actually address the root cause of the problem: the bugs in critical software or the software engineering deficiencies that generate them. How can they assess its quality and security if the code is not available for auditing? How can they trust a notoriously bug-ridden operating system like Windows to serve as the basis for mission-critical services? Would they trust that a silver tape (CrowdStrike code) could turn a faulty airplane/ship/car into something safe for their family or society?
Even today, I have to listen to the common excuse that all software has bugs because it was created by human and is therefore potentially vulnerable. How can so-called security experts ignore the fact that formally/mathematically proven correct software is extremely secure? Many are even unaware of sel4 (https://sel4.systems/). And when confronted, they claim that the costs of formal software development lead them to choose software with bugs and weak legal contract protections. Is it really true that the cost of service interruptions and licenses for buggy software is lower than creating formally proven open source software in the first place? Or is this just another version of the maxim: create problems to sell solutions?
8 • CrowdStrike (by Canned Ham on 2024-07-29 18:10:11 GMT from United States)
We had an issue when we upgraded our RHEL 9 systems which run CrowdStrike from RHEL 9.3 to 9.4 and those systems failed to boot after restarting them. I ended up having run with an older kernel -- the at-the-time latest falcon-sensor was not compatible with the *newer* kernel in 9.4 -- or have an *older* version of falcon-sensor installed.
Fortunately this was caused by OS updates, which only affected a few servers at a time, and not an automatic update of the falcon-sensor code.
So, yes, CrowdStrike can bork linux boxes, too, because it has. Just on a much smaller scale.
9 • Reviews (by grindstone on 2024-07-29 19:03:58 GMT from United States)
Appreciate the mention of how many ports are open by default. Have often wished a similar comment was present for all reviews.
10 • Torrent Downloads Section Is Skimpy (by Bob Smith on 2024-07-29 19:59:21 GMT from Guam)
I wish the DistroWatch "Torrent Downloads" area included all the torrents from the distros they advertise... but sadly, the torrent downloads section is skimpy.
11 • Torrents (by Jesse on 2024-07-29 20:02:52 GMT from Canada)
@10: It would be nice if more distributions provided torrents, but most have switched away from torrent options in favour of CDNs these days.
12 • Software Engineering was: Crowdstrike crashes (by Bruce Fowler on 2024-07-29 22:35:45 GMT from United States)
@7 Follow the dollars, just like everything else today. Quality engineering costs money, and the beancounters would just rather take a chance. A good engineer is one who takes into consideration everything that could possibly go wrong.
13 • Software Engineering (by lincoln on 2024-07-29 23:30:08 GMT from Brazil)
@12 "Follow the dollars, just like everything else today." Unfortunately, I believe that this logic in the software world is summed up in the dilemma: what will generate more money, correct software or software with bugs that repeatedly requires new purchases or subscriptions?
14 • Auto Updates (by scuzzy on 2024-07-29 23:47:28 GMT from United States)
As far as auto updates go - you are an idiot if you have them enabled on live production servers.
I always test first, then if OK run backups on live, then install updates, then take backups again, and then make sure test & live are in sync.
15 • @12: (by dragonmouth on 2024-07-30 10:50:52 GMT from United States)
" A good engineer is one who takes into consideration everything that could possibly go wrong. "
Judging from TV programs like "Engineering Disasters" and "Engineering Catastrophes", there aren't too many "good engineers". :-)
The ratio of users to software developers is 10,000 to 1, if not higher. 10,000 can discover problems with a program faster than 1 can fix them. NO software developer can foresee ALL the causes that may make a program fail. There are just too many variables, most of them external to the program and very localized (can only happen in one or two installations).
16 • Good engineers are rarely this good. (by Mark B on 2024-07-30 14:33:51 GMT from United Kingdom)
In a 2015 article from FastCompany.com it said this:
"...how much work the software does is not what makes it remarkable. What makes it remarkable is how well the software works. This software never crashes. It never needs to be re-booted. This software is bug-free. It is perfect, as perfect as human beings have achieved. Consider these stats : the last three versions of the program — each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. Commercial programs of equivalent complexity would have 5,000 errors."
It was referring to the software running the Space Shuttle.
It went on to say:
"The group writes software this good because that's how good it has to be. Every time it fires up the shuttle, their software is controlling a $4 billion piece of equipment, the lives of a half-dozen astronauts, and the dreams of the nation. Even the smallest error in space can have enormous consequences: the orbiting space shuttle travels at 17,500 miles per hour; a bug that causes a timing problem of just two-thirds of a second puts the space shuttle
three miles off course.
Contrast this, for example, with something from a few years ago on Ubuntu's own website stating there were 135,000 outstanding bugs in the OS.
Makes you think, doesn't it?
17 • Wayland (by Michael on 2024-07-30 16:12:26 GMT from Belgium)
Please think about introducing keyboard-layouts for Wayland.
In Belgium we have AZERTY.
I like to test Wayland
18 • Crowdstrike crashes (by Much Derper on 2024-07-30 19:49:00 GMT from United States)
The reason why so many people and institutions install various AV and similar software often has more to do with regulations like PCI DSS than with them being fooled into it. And while AV software is controversial in some circles (there are plenty good arguments that they actually increase attack surface of the system), the truth is that security is not just (or even less so) about features, but also (and even more so) about processes. If we're talking personal systems, where end user is also the administrator - the user that doesn't download random crap from Internet and always uses minimal privileges required may not need AV software, but even with all its flaws an AV monitor can really save a user that has no self-discipline on an exactly the same OS, be it Windows or Linux. Considering an organization cannot know with 100% certainty how disciplined each and every one of its employees are, it makes perfect sense they'd rather take the risk of AV software causing outage th!
an bet on its employees never making the mistake of opening a legit-looking infected attachment in an email. Hence the regulations like PCI DSS, that really are there because of the lowest common denominator of a corporate/government computer user.
19 • Crowdstrike crashes (by lincoln on 2024-07-30 22:43:13 GMT from Brazil)
@18: "Considering an organization cannot know with 100% certainty how disciplined each and every one of its employees are, it makes perfect sense they'd rather take the risk of AV software causing outage th! an bet on its employees never making the mistake of opening a legit-looking infected attachment in an email."
A bug-free and secure software stack is not compromised by an infected attachment in an email or random crap from the Internet. By denying access to those random malicious bits to the filesystem and sockets, providing a uid dedicated to process ID (ensuring that nothing is running under the uid, prohibiting kill(), ptrace(), fork()), setting the desired limits on memory allocation and other resource allocation, and the respective isolation of the resource (including processor timing channels and cache channels).
References:
Verified Protection Model of the seL4 Microkernel
Experience Report: seL4 Formally Verifying a High-Performance Microkernel
Refinement in the formal verification of the seL4 microkernel
seL4 Enforces Integrity
seL4: Formal Verification of an Operating-System Kernel
seL4: from General Purpose to a Proof of Information Flow Enforcement
From L3 to seL4 What Have We Learnt in 20 Years of L4 Microkernels?
The Last Mile An Empirical Study of Timing Channels on seL4
The seL4 Microkernel An Introduction
20 • @6 : Automatic Updates - No* & Mint (by Kazlu on 2024-07-31 09:06:01 GMT from France)
I'm interested in your experience because I have similar concerns for my next OS. I am considering a change whenever I need it, meaning I will not change until it breaks or falls out of support. But I always keep an eye on what could suit me.
Regarding your broken Mint 21: has Timeshift be of any help to repair the system? Maybe switching to LMDE, and therefore a Debian base, could help being provided with more conservative updates while keeping the excellent Mint software layer?
21 • Crowdstrike crashes (by Much Derper on 2024-07-31 11:47:18 GMT from United States)
@19 that kernel is only a small part of the much larger picture. But even assuming everything is exactly as you say, migrating the whole IT infrastructure will take lots of time and lots of money, it will never happen overnight, especially onto a relatively young OS with barely any software running on it. It will be a lot more of these Crowdstrike-like events for the people paying the bills to agree to pay for that migration. It's never the question of security or reliability, it's always the question of costs. Perceived costs, not real-world ones.
22 • @20 (by Bernie on 2024-08-01 10:21:12 GMT from France)
I never use automated backups. Had several bad experiences years ago and found the software more complicated to configure than simply backing up 2 fold (1 flash drive & 1 cloud) + various externals.
I was able to boot by choosing the previous kernel at boot, easy enough but still an annoyance. And I’m glad it happened to me because I have both my parents Mint computers, they love them but would have been unable to apply that fix should it have affected them.
I want to go on a rant but it essentially boils down to Mint being a great experience on business level computers on one hand and then my 5 yr old gaming Asia is only at best 90% functional with only 85% of that being consistent. (Unreliable to non existent Bluetooth for one).
23 • crowdstrike and linux (by ion on 2024-08-01 18:42:00 GMT from Moldova)
things like crowdstrike don't happen on linux cause LINUX HAS BETTER DESIGN
since 2014
the solution is ebpf, a virtual machine in linux kernel, SENSITIVE APPS for which can be implemented (think about .net and java, but only for kernel)
instead of designing kernel modules
There are security companies who implemented their security solutions as epbf apps,
instead of kernel modules,
so pretty much nobody cares about crowdstrike on linux, cause there are better solutions.
and epbf is fantastic cause it is maintained by google, facebook and other big companies,
and is very safe, so even if you ebpf app is faulty, it will not bring down the kernel when it will crash.
24 • a nice article about ebpf and windows and linux (by ion on 2024-08-01 18:46:08 GMT from Moldova)
https://www.brendangregg.com/blog/2024-07-22/no-more-blue-fridays.html
25 • CrowdStrike (by De Schatberg on 2024-08-02 05:39:00 GMT from The Netherlands)
@23 (by ion from Moldova)
"things like crowdstrike don't happen on linux cause LINUX HAS BETTER DESIGN"
With all due respect, people like you and a few others here who don't understand the CrowdStrike problem or the problems with Linux design should stay away from writing comments because they can only end up being ridiculous like yours.
It wasn't bad Windows design that caused the problem, it was a badly written system driver.
Address 0x0 is commonly used as a null pointer to indicate that there is no valid object. Programmers should always check for null pointers before accessing objects or their properties. The programmer didn't check for the null pointer.
Bad drivers can crash any system.
https://heise.cloudimg.io/width/610/q70.png-lossy-70.webp-lossy-70.foil1/_www-heise-de_/imgs/18/4/6/3/7/2/3/0/Unbenannt-495a939d1f257576.png
26 • CrowdStrike (by lincoln on 2024-08-02 20:07:15 GMT from Brazil)
@25 (by De Schatberg )
"With all due respect, people like you and a few others here who don't understand the CrowdStrike problem or the problems with Linux design should stay away from writing comments because they can only end up being ridiculous like yours."
The excerpt above could be an opinion on your own comment.
eBPF/BPF is a virtual machine in the Linux kernel, and its bytecode can be generated by the LLVM compiler from pseudo-C code. This bytecode program goes through a security verifier, ensuring:
"- The program does not crash or otherwise harm the system;
- The program always runs to completion;
- Programs may not use any uninitialized variables or access memory out of bounds;
- Programs must fit within the size requirements of the system."
Therefore, it is evident that in this design, a catastrophic error from a bad drive accessing a null pointer could not crash the entire Linux system, since the eBPF verifier itself would prevent its execution.
References:
https://ebpf.io/what-is-ebpf/
https://www.kernel.org/doc/html/latest/bpf/index.html
27 • Automatic updates (by Andreas on 2024-08-02 20:08:00 GMT from Austria)
My Raspberry machine has unattended-upgrades (8) enabled, so that it automatically downloads and installs security updates, but it's set not to automatically reboot. My desktop and laptop are always manually updated first time after booting.
28 • CrowdStrike (by De Schatberg on 2024-08-02 21:58:00 GMT from The Netherlands)
@26 (by lincoln from Brazil)
"Therefore, it is evident that in this design, a catastrophic error from a bad drive accessing a null pointer could not crash the entire Linux system..."
Obviously, you're missing the point. It is irrelevant whether the OS itself is affected when the critical application starts to fail. It is the application crash that matters.
If that system was that great, everyone would be using it, but companies still rely on dos, windows 3.1, and OS/2.
29 • CrowdStrike (by lincoln on 2024-08-02 22:27:06 GMT from Brazil)
@28 (by De Schatberg from The Netherlands)
"Obviously, you're missing the point."[2]
If only the CrowdStrike code had failed, there wouldn't have been the biggest disruption in history to essential services around the world. The big problem was that the Windows operating system was not resilient and did not continue to support essential services.
"If that system was that great, everyone would be using it, but companies still rely on dos, windows 3.1, and OS/2."
That must be why the last three operating systems are the most used on servers.
30 • @29 (by Noname on 2024-08-03 00:00:16 GMT from United States)
CrowdStrike was not just a Windows issue. It messes up with Linux kernel too. That's just a bad C++ programming. Those 3 ancient OSs are stil in use by German railways, American airlines, American post, etc.
Number of Comments: 30
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.
|
| Archives |
| • Issue 1100 (2024-12-09): Oreon 9.3, differences in speed, IPFire's new appliance, Fedora Asahi Remix gets new video drivers, openSUSE Leap Micro updated, Redox OS running Redox OS |
| • Issue 1099 (2024-12-02): AnduinOS 1.0.1, measuring RAM usage, SUSE continues rebranding efforts, UBports prepares for next major version, Murena offering non-NFC phone |
| • Issue 1098 (2024-11-25): Linux Lite 7.2, backing up specific folders, Murena and Fairphone partner in fair trade deal, Arch installer gets new text interface, Ubuntu security tool patched |
| • Issue 1097 (2024-11-18): Chimera Linux vs Chimera OS, choosing between AlmaLinux and Debian, Fedora elevates KDE spin to an edition, Fedora previews new installer, KDE testing its own distro, Qubes-style isolation coming to FreeBSD |
| • Issue 1096 (2024-11-11): Bazzite 40, Playtron OS Alpha 1, Tucana Linux 3.1, detecting Screen sessions, Redox imports COSMIC software centre, FreeBSD booting on the PinePhone Pro, LXQt supports Wayland window managers |
| • Issue 1095 (2024-11-04): Fedora 41 Kinoite, transferring applications between computers, openSUSE Tumbleweed receives multiple upgrades, Ubuntu testing compiler optimizations, Mint partners with Framework |
| • Issue 1094 (2024-10-28): DebLight OS 1, backing up crontab, AlmaLinux introduces Litten branch, openSUSE unveils refreshed look, Ubuntu turns 20
| | • Issue 1093 (2024-10-21): Kubuntu 24.10, atomic vs immutable distributions, Debian upgrading Perl packages, UBports adding VoLTE support, Android to gain native GNU/Linux application support |
| • Issue 1092 (2024-10-14): FunOS 24.04.1, a home directory inside a file, work starts of openSUSE Leap 16.0, improvements in Haiku, KDE neon upgrades its base |
| • Issue 1091 (2024-10-07): Redox OS 0.9.0, Unified package management vs universal package formats, Redox begins RISC-V port, Mint polishes interface, Qubes certifies new laptop |
| • Issue 1090 (2024-09-30): Rhino Linux 2024.2, commercial distros with alternative desktops, Valve seeks to improve Wayland performance, HardenedBSD parterns with Protectli, Tails merges with Tor Project, Quantum Leap partners with the FreeBSD Foundation |
| • Issue 1089 (2024-09-23): Expirion 6.0, openKylin 2.0, managing configuration files, the future of Linux development, fixing bugs in Haiku, Slackware packages dracut |
| • Issue 1088 (2024-09-16): PorteuX 1.6, migrating from Windows 10 to which Linux distro, making NetBSD immutable, AlmaLinux offers hardware certification, Mint updates old APT tools |
| • Issue 1087 (2024-09-09): COSMIC desktop, running cron jobs at variable times, UBports highlights new apps, HardenedBSD offers work around for FreeBSD change, Debian considers how to cull old packages, systemd ported to musl |
| • Issue 1086 (2024-09-02): Vanilla OS 2, command line tips for simple tasks, FreeBSD receives investment from STF, openSUSE Tumbleweed update can break network connections, Debian refreshes media |
| • Issue 1085 (2024-08-26): Nobara 40, OpenMandriva 24.07 "ROME", distros which include source code, FreeBSD publishes quarterly report, Microsoft updates breaks Linux in dual-boot environments |
| • Issue 1084 (2024-08-19): Liya 2.0, dual boot with encryption, Haiku introduces performance improvements, Gentoo dropping IA-64, Redcore merges major upgrade |
| • Issue 1083 (2024-08-12): TrueNAS 24.04.2 "SCALE", Linux distros for smartphones, Redox OS introduces web server, PipeWire exposes battery drain on Linux, Canonical updates kernel version policy |
| • Issue 1082 (2024-08-05): Linux Mint 22, taking snapshots of UFS on FreeBSD, openSUSE updates Tumbleweed and Aeon, Debian creates Tiny QA Tasks, Manjaro testing immutable images |
| • Issue 1081 (2024-07-29): SysLinuxOS 12.4, OpenBSD gain hardware acceleration, Slackware changes kernel naming, Mint publishes upgrade instructions |
| • Issue 1080 (2024-07-22): Running GNU/Linux on Android with Andronix, protecting network services, Solus dropping AppArmor and Snap, openSUSE Aeon Desktop gaining full disk encryption, SUSE asks openSUSE to change its branding |
| • Issue 1079 (2024-07-15): Ubuntu Core 24, hiding files on Linux, Fedora dropping X11 packages on Workstation, Red Hat phasing out GRUB, new OpenSSH vulnerability, FreeBSD speeds up release cycle, UBports testing new first-run wizard |
| • Issue 1078 (2024-07-08): Changing init software, server machines running desktop environments, OpenSSH vulnerability patched, Peppermint launches new edition, HardenedBSD updates ports |
| • Issue 1077 (2024-07-01): The Unity and Lomiri interfaces, different distros for different tasks, Ubuntu plans to run Wayland on NVIDIA cards, openSUSE updates Leap Micro, Debian releases refreshed media, UBports gaining contact synchronisation, FreeDOS celebrates its 30th anniversary |
| • Issue 1076 (2024-06-24): openSUSE 15.6, what makes Linux unique, SUSE Liberty Linux to support CentOS Linux 7, SLE receives 19 years of support, openSUSE testing Leap Micro edition |
| • Issue 1075 (2024-06-17): Redox OS, X11 and Wayland on the BSDs, AlmaLinux releases Pi build, Canonical announces RISC-V laptop with Ubuntu, key changes in systemd |
| • Issue 1074 (2024-06-10): Endless OS 6.0.0, distros with init diversity, Mint to filter unverified Flatpaks, Debian adds systemd-boot options, Redox adopts COSMIC desktop, OpenSSH gains new security features |
| • Issue 1073 (2024-06-03): LXQt 2.0.0, an overview of Linux desktop environments, Canonical partners with Milk-V, openSUSE introduces new features in Aeon Desktop, Fedora mirrors see rise in traffic, Wayland adds OpenBSD support |
| • Issue 1072 (2024-05-27): Manjaro 24.0, comparing init software, OpenBSD ports Plasma 6, Arch community debates mirror requirements, ThinOS to upgrade its FreeBSD core |
| • Issue 1071 (2024-05-20): Archcraft 2024.04.06, common command line mistakes, ReactOS imports WINE improvements, Haiku makes adjusting themes easier, NetBSD takes a stand against code generated by chatbots |
| • Issue 1070 (2024-05-13): Damn Small Linux 2024, hiding kernel messages during boot, Red Hat offers AI edition, new web browser for UBports, Fedora Asahi Remix 40 released, Qubes extends support for version 4.1 |
| • Issue 1069 (2024-05-06): Ubuntu 24.04, installing packages in alternative locations, systemd creates sudo alternative, Mint encourages XApps collaboration, FreeBSD publishes quarterly update |
| • Issue 1068 (2024-04-29): Fedora 40, transforming one distro into another, Debian elects new Project Leader, Red Hat extends support cycle, Emmabuntus adds accessibility features, Canonical's new security features |
| • Issue 1067 (2024-04-22): LocalSend for transferring files, detecting supported CPU architecure levels, new visual design for APT, Fedora and openSUSE working on reproducible builds, LXQt released, AlmaLinux re-adds hardware support |
| • Issue 1066 (2024-04-15): Fun projects to do with the Raspberry Pi and PinePhone, installing new software on fixed-release distributions, improving GNOME Terminal performance, Mint testing new repository mirrors, Gentoo becomes a Software In the Public Interest project |
| • Issue 1065 (2024-04-08): Dr.Parted Live 24.03, answering questions about the xz exploit, Linux Mint to ship HWE kernel, AlmaLinux patches flaw ahead of upstream Red Hat, Calculate changes release model |
| • Issue 1064 (2024-04-01): NixOS 23.11, the status of Hurd, liblzma compromised upstream, FreeBSD Foundation focuses on improving wireless networking, Ubuntu Pro offers 12 years of support |
| • Issue 1063 (2024-03-25): Redcore Linux 2401, how slowly can a rolling release update, Debian starts new Project Leader election, Red Hat creating new NVIDIA driver, Snap store hit with more malware |
| • Issue 1062 (2024-03-18): KDE neon 20240304, changing file permissions, Canonical turns 20, Pop!_OS creates new software centre, openSUSE packages Plasma 6 |
| • Issue 1061 (2024-03-11): Using a PinePhone as a workstation, restarting background services on a schedule, NixBSD ports Nix to FreeBSD, Fedora packaging COSMIC, postmarketOS to adopt systemd, Linux Mint replacing HexChat |
| • Issue 1060 (2024-03-04): AV Linux MX-23.1, bootstrapping a network connection, key OpenBSD features, Qubes certifies new hardware, LXQt and Plasma migrate to Qt 6 |
| • Issue 1059 (2024-02-26): Warp Terminal, navigating manual pages, malware found in the Snap store, Red Hat considering CPU requirement update, UBports organizes ongoing work |
| • Issue 1058 (2024-02-19): Drauger OS 7.6, how much disk space to allocate, System76 prepares to launch COSMIC desktop, UBports changes its version scheme, TrueNAS to offer faster deduplication |
| • Issue 1057 (2024-02-12): Adelie Linux 1.0 Beta, rolling release vs fixed for a smoother experience, Debian working on 2038 bug, elementary OS to split applications from base system updates, Fedora announces Atomic Desktops |
| • Issue 1056 (2024-02-05): wattOS R13, the various write speeds of ISO writing tools, DSL returns, Mint faces Wayland challenges, HardenedBSD blocks foreign USB devices, Gentoo publishes new repository, Linux distros patch glibc flaw |
| • Issue 1055 (2024-01-29): CNIX OS 231204, distributions patching packages the most, Gentoo team presents ongoing work, UBports introduces connectivity and battery improvements, interview with Haiku developer |
| • Issue 1054 (2024-01-22): Solus 4.5, comparing dd and cp when writing ISO files, openSUSE plans new major Leap version, XeroLinux shutting down, HardenedBSD changes its build schedule |
| • Issue 1053 (2024-01-15): Linux AI voice assistants, some distributions running hotter than others, UBports talks about coming changes, Qubes certifies StarBook laptops, Asahi Linux improves energy savings |
| • Issue 1052 (2024-01-08): OpenMandriva Lx 5.0, keeping shell commands running when theterminal closes, Mint upgrades Edge kernel, Vanilla OS plans big changes, Canonical working to make Snap more cross-platform |
| • Issue 1051 (2024-01-01): Favourite distros of 2023, reloading shell settings, Asahi Linux releases Fedora remix, Gentoo offers binary packages, openSUSE provides full disk encryption |
| • Issue 1050 (2023-12-18): rlxos 2023.11, renaming files and opening terminal windows in specific directories, TrueNAS publishes ZFS fixes, Debian publishes delayed install media, Haiku polishes desktop experience |
| • Issue 1049 (2023-12-11): Lernstick 12, alternatives to WINE, openSUSE updates its branding, Mint unveils new features, Lubuntu team plans for 24.04 |
| • Issue 1048 (2023-12-04): openSUSE MicroOS, the transition from X11 to Wayland, Red Hat phasing out X11 packages, UBports making mobile development easier |
| • Issue 1047 (2023-11-27): GhostBSD 23.10.1, Why Linux uses swap when memory is free, Ubuntu Budgie may benefit from Wayland work in Xfce, early issues with FreeBSD 14.0 |
| • Issue 1046 (2023-11-20): Slackel 7.7 "Openbox", restricting CPU usage, Haiku improves font handling and software centre performance, Canonical launches MicroCloud |
| • 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 | 
Xubuntu
Xubuntu is a community-developed operating system based on Ubuntu. It comes with Xfce, which is a stable, light and configurable desktop environment.
Status: Active
|
| 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.
|
|
• 
• 
• 
• 
• 
• 
• 
