 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 • alternative package manager distro (by fenglengshun on 2023-03-13 04:14:34 GMT from Indonesia)
Currently running Vanilla OS myself, I'm waiting for the 2.0 to test the migration process (if there's one, if not then I'll just proceed to use something else). Overall, it's pretty easy to adapt to how they want to do things, especially as apx makes it easy to run stuff from AUR and Nix, making me not need to install host that much.
Was thinking about trying out blendOS as well, but it seems like a scuff Vanilla OS, led by rudra who is young and busy enough that I'm not entirely sure if everything is well maintained (I didn't see any commit for many of blendOS projects on github which doesn't inspire confidence in a WIP distro), and they're planning to do major changes according to their blog post, so I might as well wait for that.
I'm also keeping an eye on Crystal Linux's Project Shard, which apparently aims to do a macOS style multi-volume immutability that apparently would allow users to still use pacman as normal. Seems to be the more sensible approach to immutability on Arch-based.
And of course, there's whatever is going on with PopOS with their immutable core with overlays for user packages, which probably has something to do with Linus and something something "Yes, Break My System."
Overall, it's pretty interesting. So far, only Vanilla feels worth running to me, due to having Nix well-integrated and having the most active development. I'm not going to daily drive immutable distro any time soon but I'm keeping an eye on the space in general. I really hope using Nix to supplement the usual immutable package managers becomes standard, because it makes it much more convenient and I have less need to do what I'm "not supposed to".
2 • Package Manager (by Dr.J on 2023-03-13 08:17:48 GMT from Germany)
To date, there has been no need for the desire for alternative package managers. Because Arch has with the AUR a huge fund of software away from the official repositories. And should a package from a third party actually be necessary, this is often available as a deb.package. With debtap there is a tool for this in the AUR.
3 • blendOS et al: Complexity, Component-Count, Attack-Surface? (by Benjamin on 2023-03-13 09:12:55 GMT from United Kingdom)
Whilst the conceptual goals around distro-agnostic package-support (unifying and simplifying) may be laudable (and probably fashionable), I do have to wonder and worry about the implications for security and robustness. Especially when it's small teams (or worse, a lone individual) "maintaining" a whole distro.
How much attention is being given to the well-established principles: simple small components doing one thing and doing it well, and simple small codebase in which it's easier to spot problems?
We're in a cat-and-mouse world of increasingly hostile and innovative digital actors (e.g., go read about Pegasus spyware by Israeli NSO).
As a refugee fleeing Canonical's Ubuntu I'm looking for a distro where there's a good community of developers (not one-man-band projects) with security-experts who are looking to reduce the complexity and component-count and reduce the attack-surface, actively plugging holes. I want better clarity/transparency and fewer potential points-of-failure.
Proof-of-Concept multi-flavour package-support might be nice in theory, but how high are security and long-term maintainable robustness on the list of priorities?
Actually, @Jesse, question/suggestion, it would be helpful to have knowledgeable reviews of the state of play here in 2023 of distros actively prioritising Security. I keep reading references to kernel-tweaks and immutable filesystems and various forms of compartmentalisation and jails, so it would be good to have others expertise and opinions on these developments (and on the distros implementing them), gathered and shared here.
4 • Alternative package maned distros (by Hank on 2023-03-13 09:41:09 GMT from Germany)
A solution creating a problem. Massive Bloat.
Like using Flatpack except even more overloaded and bloated. Thanks, will stick with DEB.
If a package is unavailable self compiling is usually a solution.
5 • Packaging (by Friar Tux on 2023-03-13 16:13:53 GMT from Canada)
Not really sure what all the fuss (FOSS) is about. For me, Flatpaks and Snaps are out. They are way too new, with way too many issues, to even bother with. My preference is AppImages - one file - that is easily storable and transferable to anywhere and, so far, has worked with no glitches. Mostly, though, I find the default software quite adequate. If I need something that isn't in the default repository, I use DEB, and if that doesn't have it, I go for AppImage. So far, I haven't had any issues.
I AM curious why the AppImage folks haven't gained more popularity as their product seems to be the crowning glory of this whole "universal software" push. It requires no "installer", just download the app (a single file), make it executable, and go to work. Easy peasy. So, to me Flatpak and Snaps appears to be a "my way or the highway" type of thing - not the Linux one job, done well. (I wish all apps/programs were in the AppImage format)
6 • @3 (by Justin on 2023-03-13 16:15:24 GMT from United States)
OS security and patching is one major reason I moved to Linux. I like a centralized archive (repository) of software being watched in my (relatively) best interest. All the portable packages, containers, etc., in Linux have the very problem you describe: who maintains them? It is the fragmentation of maintainers. I understand the historical reasons why, but still, it boils down to "we don't collaborate, we fork" with OSS (this approach is both positive and negative for the ecosystem, I'm not making a judgement here).
I've seen this problem before. Windows had it decades ago (and still does). You used to download random zip files from the internet. They would come prepackaged with libraries you needed because you never knew what was on someone's system. You end up with 20 DLLs for the same component, but they would be at different versions, all with different bugs and flaws. They are great for malware and system penetration because they are a nightmare for security. Linux offered single packages for shared libraries, so when one gets fixed, all apps get fixed. If some app breaks because of incompatibility, either that also gets fixed (hopefully by the author) or some other alternative existed that wasn't too hard to find (look in the repo rather than scour the internet, or if you were technical enough, make the fix yourself because you can read the script or source).
Don't get me wrong, I love the idea of portable packages. I have a couple AppImages I've made so that I can run that software anywhere. However, for security and maintenance, we're going in the wrong direction. Users put convenience over security because they feel convenience every day. It's only after security affects them (like someone robs their house because they've left it unlocked for years with "no problems") that they suddenly care, only to forget a few weeks/months later because it's become inconvenient again.
In my mind the solution is better collaboration between projects. I don't think having one unified project is the solution because there are a lot of benefits from a community working on different but similar things to find better overall solutions (in biology you want to have diversity so that a single defect doesn't wipe out your species). However, the how is always harder, so I appreciate the people and groups that work toward this goal.
7 • HTTP access (by David on 2023-03-13 16:29:00 GMT from United Kingdom)
One answer is not to use a browser that insists on HTTPS. I've just checked the avidemux site with both Firefox and Pale Moon — no problems. Who needs anything else?
8 • immutable (by Toran on 2023-03-13 17:06:23 GMT from Belgium)
I think the concept of Vanilla OS is the future, but only when we have the same possibiliies as f.e. ubuntu. And I am talking about hplip and hp-plugin. Okay, we have ScanVue, but that one is commercial.
9 • Tracking all the files installed with a package (by Tuxworx on 2023-03-13 17:26:05 GMT from United States)
If you are running a system that supports the apt package manager and might want to check everything that is installed along with a package, it seems a lot easier to me to install packages with Synaptic. It has a built-in History function that will list (by date and time) everything that was installed, removed, or updated each time you used it to perform any of those functions. An added bonus is that you can configure it to differentiate between installing only dependencies or installing dependencies plus recommended packages. You can check what a packages depends on and what it only recommends before running the installation; so if, for instance, you only want to install some of the recommended packages, you can initially run the install with only dependencies and then separately install just the recommended things that you want.
10 • Package files - portage (by MC on 2023-03-13 20:40:08 GMT from United States)
On Portage-based systems (eg. Gentoo) the equery utility, found in the gentoolkit package, can fetch this information
11 • Packaging (by joncr on 2023-03-14 11:55:30 GMT from United States)
I am inclined to think Flathub enthusiasm among big-name Linux distributions is motivated, in part, by the possibility Flatpaks can get them out of the packaging business. However, if/when everyone is running the same Flatpaks, what's left to distinguish between distributions beyond kernels, etc.?
My only grievance with Canonical's Snap is the performance of Firefox on Wayland. I do not care how software I do no interact with is packaged.
12 • @5 Packaging (by StephenC on 2023-03-14 19:19:22 GMT from United States)
I agree that the push for Flatpak does seem to be so that maintainers can reduce their time. I can understand that. But, for the couple of apps that I want to be portable, I just run them as AppImages in a sandbox on Linux. This allows me to carry the same Mac, Windows, and Linux portable app on a USB stick. No need to install anything, anywhere.
As a end-user, I'm not interested in portable "distribution", just portable "usage".
13 • How to find inotifywait (by Bruce F. on 2023-03-14 23:05:12 GMT from United States)
In case you are having trouble finding it, "inotifywait" is part of the "inotify-tools" package. At least on Manjaro.
14 • What's left... is still right. (by Friar Tux on 2023-03-15 00:40:02 GMT from Canada)
@11 (joncr) "... what's left to distinguish between distributions beyond kernels, etc.?" I see the distros similar to cars/trucks/buses etc.. They basically all do the same thing, BUT, there are hundreds (thousands even) of different models (some even within the same company). Most can be repaired with the same, or similar tools. Some folks will swear by a certain model while disparaging all others. Some don't really care one way or the other so long as they get to where they're going. Some have more than one - one for work and another for play. And some folks like to pull their's apart to see what makes it tick, while others just send their's to a shop for repairs.
Distros are quite like cars and we treat the two very similarly.
15 • Packages (by penguinx86 on 2023-03-15 07:01:25 GMT from United States)
I prefer traditional Linux packages like .DEB or .RPM. I really don't like Snap packages showing up when I type the 'df' command to check disk space. I don't want to be forced to use more and more abstraction layers on my home laptop. Keep it simple!
16 • blendOS and the like (by Simon on 2023-03-15 08:47:12 GMT from New Zealand)
I just don't understand the point of this mess. Why complicate a system with so many different package managers? Even if your distro doesn't have the package you want in its repositories, it's trivially easy to create your own package from upstream source: surely much easier, and a better investment of your time (and also more helpful to the community, if you share your packages) to learn how to build your own packages for your preferred distro, than to learn how to manage one of these cobbled together pastiche distros. I suppose I can appreciate that people do stuff like this just for the fun of doing something different... but I would hate to be running one of these hybrid things as my daily desktop.
17 • Old Software (by John on 2023-03-15 11:51:50 GMT from Canada)
As a Slackware user, the Slackware team worries about these issues for me :)
18 • Snap no more (by verndog on 2023-03-15 12:39:01 GMT from United States)
@15 I don't use Snap at all. I follow this removal process:
https://onlinux.systems/guides/20220524_how-to-disable-and-remove-snap-on-ubuntu-2204
Then I add Firefox as per these instructions:
https://support.mozilla.org/en-US/kb/install-firefox-linux#w_install-firefox-from-mozilla-builds-for-advanced-users
19 • @16: (by dragonmouth on 2023-03-15 13:11:13 GMT from United States)
You have to look no further than the Linux philosophy for the answer. Any Tom, Dick or Harry can create their own version of an application or a distro. It does not have to be revolutionary or evolutionary. It doesn't even have to be practical or useful. It just has to a LITTLE bit different. And the vast majority of the Linux community encourages it.
When it comes to corporate Linux developers, it is about control. Each company wants and expects their product(s) to be THE ONES to dominate the rest of the Linux universe. As Mark Shuttleworth said about Canonical's development of Unity, Mir, Snap, etc - "We want products WE can control."
Number of Comments: 19
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 | 
Kwheezy
Kwheezy was a Debian-based Linux distribution with an intuitive KDE desktop and a good selection of GNU/Linux and open-source software. It also includes popular device drivers, media codecs and browser plugins, all pre-configured and ready for use at first boot.
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.
|
|
• 
• 
• 
• 
• 
• 
• 
