 DistroWatch Weekly |
| Tip Jar |
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 1, value: US$5) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
| Extended Lifecycle Support by TuxCare |
|
|
| Reader Comments • Jump to last comment |
1 • Filesystem flags (by DC on 2023-07-10 01:09:29 GMT from United States)
Wait a minute. You have to list what all of the default mount options('filesystem flags') are before we can tell if our distros are using custom mount options (flags) or not...
2 • Filesystem flags (by Jesse on 2023-07-10 02:15:52 GMT from Canada)
@1: >> "Wait a minute. You have to list what all of the default mount options('filesystem flags') are before we can tell if our distros are using custom mount options (flags) or not..."
If you have any custom flags set, they'll be in the /etc/fstab file. If no custom flags are set, the feature column will say (literally) "defaults".
3 • Solus, Respect & Trust (by CorpSouth on 2023-07-10 02:53:59 GMT from United States)
I've been reading testimonials about Solus going back to before the project had stagnated for two years. One has to understand that respect and trust are two way streets, and the attitudes of the maintainers haven't been representative of those tenants, apparently. They're going to need to be aggressive about moving the project forward.
4 • Crystal Linux (by Olexander on 2023-07-10 02:57:46 GMT from Ukraine)
Unfortunately Crystal's iso on their Gitlab is old.
And yeah, it's buggy.
(actually I couldn't managed it to boot on my laptop)
But after I joining Discord channel I've got link to the fresh iso.
It booted and even installed without crashes.
I can say guys are working hard to clean bugs.
So please give them another try.
5 • Mount-Flags (by Dr.J on 2023-07-10 08:09:29 GMT from Germany)
I use a lot of mount flags, because it's like you say: you can use them to customize your system to your needs, which is especially useful if you have a lot of mounts (two disks, multiple partitions, mounting network or NFS drives, etc.).
6 • Mount flags (by nsp0323 on 2023-07-10 09:45:58 GMT from Sweden)
Voted: "Yes - I set custom flags" but, it's a bit of a lie.
Everything is default, except for "noatime" and "nodevmtime"
7 • Fedora's telemetry (by Bluecow on 2023-07-10 17:46:37 GMT from United States)
Red Hat's closed source, Fedora's spying their users (100% anonymously, of course).
I can imagine some ads coming to Fedora's start menu soon after that. Things like Disney+ and Outlook 365 promos, just like in W11.
8 • Fedora Telementry (by nickydi on 2023-07-11 01:41:46 GMT from Australia)
Red Hats love child "Fedora" wanting telemetry inside there distro. OMG what has happened to the Linux World... it has gone completely mad. Lets tell them at first we are only collecting a lttle bit of data like such and such, then the next few releases we will really ramp up the game and get there info just like all the other no good company's trying to harvest peoples data. Linux used to be great but now its just like all the rest, "Corrupt".
9 • Tweakers (by Trihexagonal on 2023-07-11 05:47:49 GMT from United States)
"Mount flags can be used to tune performance or provide additional functionality."
The biggest mistake people new to Linux or BSD by far was tweaking this and fiddling with that when they don't yet have the learned skills to fix what didn't need fixed in the first place.
Then some will become frustrated, find something about the OS to mumble about (Because what else could it be?) Kick rocks at Tux and go back to Windows.
Which is all good and fine with me as long as I'm not the one who has to fix it. Chaff from the wheat, Natures Way and all that..
10 • Fedora telemetry (by Christian on 2023-07-11 12:05:44 GMT from Canada)
Back in Fedora 7 there was "smolt" (https://en.wikipedia.org/wiki/Smolt_%28Linux%29). It was included by default and I can't remember it raising many concerns in the community. A few years later Ubuntu started something similar, but it was not very well received.
I've not being using used Fedora for a while, but, I would share telemetry from my system to contribute with the project.
11 • Smolt (by Otis on 2023-07-11 14:47:34 GMT from United States)
@10 yes Smolt seemed to usher in that mindset (of devs working with other entities to harvest hardware info on linux machines). It's usage info that made me nervous, but that's another conversation.
I see that only 5 distros shipped that little piece of ware, but the philosophy of it is now commonplace, of course.
12 • telemetry (by GrumpyGranpa on 2023-07-12 02:50:32 GMT from Australia)
One reason people came to linux was to get away from the privacy nightmare that is Windows and its data collection.
As soon as IBM became involved with Redhat, we allsort of guessed that down the road they would want to recoup their investment. Selling licences is fine, but data harvesting is another revenue stream.
Fortunately, we are swamped with choice. Don't like data collection, no problem. Don't like systemd, no problem. Don't like desktop xyz, no problem.
Fragmentation of distros is an issue from a dev pool point of view, but also a blessing for the rest of us who can pick and choose what we want to use.
13 • Opt-in works, just ask Debian (by Andy Prough on 2023-07-12 14:19:52 GMT from United States)
Fedora's argument against opt-in telemetry is based on a lie, claiming that opt-in never works.
Debian's popularity-contest package (popcon) has always been completely opt-in - you have to install the package for it to work. It has hundreds of thousands of users and has been giving a vast amount of Debian usage information for the past 25 years now.
14 • Fedora telemetry (by Dan on 2023-07-12 15:37:53 GMT from Israel)
I fully support developers' right to collect telemetry, as long as it's not invasive, described in an honest transparent way in the UI, and there's a way to fully disable it. It all depends on the type of information that is collected. Anyone who cries about their "privacy" just because there *is* telemetry collected, without having not even a *single* look into the type of data collected, is an idiot.
15 • Telemetry opt-in vs. opt-out (by Dan on 2023-07-12 15:52:43 GMT from Israel)
@13
"Fedora's argument against opt-in telemetry is based on a lie, claiming that opt-in never works."
I've had a brief look and that's not what was said.
"Debian's popularity-contest package (popcon) has always been completely opt-in… It has hundreds of thousands of users and has been giving a vast amount of Debian usage information…"
First, this is an anecdote. Second, Debian and Fedora might have users with completely different mindsets. And third, this doesn't refute the argument that people who uncaringly use default settings could contribute telemetry using an opt-out scheme but not using an opt-in scheme, while users who do care about settings would contribute the same telemetry regardless of whether it's opt-in or opt-out. Objectively, opt-out is better.
16 • @15 (by Andy Prough on 2023-07-12 17:41:10 GMT from United States)
>"I've had a brief look and that's not what was said."
Here's what is said in the Fedora proposal exactly: "This is to ensure the system is opt-out, not opt-in. This is essential because we know that opt-in metrics are not very useful."
I said that they said "never works", they actually said "not very useful". Not much difference between the two, but ok you are right that there is a difference, but the same outcome in their decision making.
>"First, this is an anecdote."
No, it's a decades long test with vast quantities of data. An anecdote is a single data point.
>"Second, Debian and Fedora might have users with completely different mindsets."
Why? What is potentially different about their mindsets? You haven't written a refutation, merely that you aren't willing to consider the point that Debian has collected vast amounts of useful data with an opt-in system. Unfortunately for your argument, the facts tell a dramatically different story.
>"And third, this doesn't refute the argument that people who uncaringly use default settings could contribute telemetry using an opt-out scheme but not using an opt-in scheme, while users who do care about settings would contribute the same telemetry regardless of whether it's opt-in or opt-out. Objectively, opt-out is better."
Wrong. Opt-out is better if Fedora wants to sneakily trick some people into not disabling telemetry who are trying to quickly install the system without reading all the verbiage. But once again, Debian's 25 successful years of popcon proves that undoubtedly opt-out is not inherently better.
17 • telemetry @15 (by Anthony on 2023-07-12 19:15:04 GMT from Czechia)
@15 Objectively, opt-out is better.
Funny you should appeal to objectivity, when your statement isn't true. Opt-out is worse from a privacy-focused viewpoint. It is better if you *only* consider the viewpoint of the one collecting (and supposedly "needing") the data. Nice fallacy. =)
@14
Another nice fallacy. No-one has the *right* to collect someone else's information. Information should be voluntarily given, not taken. That's one huge difference between the legal systems of the US and the EU. Arguing for unregulated and opt-out data collection is idiocy, especially if you make fallacies like you. (How the *supposedly* different mindsets of Debian- and Fedora users come into the topic of data collection is beyond reason...)
Keep up the circus show, folks. :)
18 • It seems that some people think they're smarter than logic (by Dan on 2023-07-12 20:17:27 GMT from Israel)
@16
"No, it's a decades long test with vast quantities of data. An anecdote is a single data point."
Irrelevant. You cannot deduce anything from this data, you can only induce, and induction isn't a logical way to get conclusions, it uses intuition, and thus it's prone to failure. (Deduction is prone as well to failure, if the method or the base assumptions are wrong, but with induction, there's *never* a guarantee that the conclusion is true, unlike deduction where it could be guaranteed to be true.)
"Why? What is potentially different about their mindsets? You haven't written a refutation, merely that you aren't willing to consider the point that Debian has collected vast amounts of useful data with an opt-in system. Unfortunately for your argument, the facts tell a dramatically different story."
What is potentially different about their mindsets is lots of things. This should be quite obvious to you, but apparently isn't. In any case, it is your responsibility to prove that their mindsets are universally always identical, and not my responsibility to prove that their mindsets aren't identical, because (surprise to you!) that's how logic works. I haven't refuted your data, because there's no need to; I've refuted the core of your reasoning (and also later provided a logical proof that opt-out is never worse than opt-in for collecting representative statistics). Unfortunately for your argument, you're just plain wrong and illogical. And unfortunately for you, facts tell different stories depending how you process them, and this is why the reasoning you use to conclude on the basis of facts is important as well.
"Wrong. Opt-out is better if Fedora wants to sneakily trick some people into not disabling telemetry who are trying to quickly install the system without reading all the verbiage."
Wrong. Out-out has nothing to do with the aspect of being "sneaky" (read: dishonest) nor with the actual data that's being collected. Apart from the opt-out aspect, there's also the aspect of how telemetry and the options to control telemetry are presented to users, and the aspect of whether the data that's ultimately collected contains anything that could be linked to an individual user or a group of users. There's not yet any proof that any arbitrary piece of information could be linked to the user(s) it was collected from, meaning that it's possible that telemetry could respect the privacy of the users it was collected from. Additionally, regarding the opt-out/opt-in aspect and the aspect of dishonesty in how telemetry is presented to users and given control of, the burden of proving that these two aspects are inherently linked together somehow is, again, on you.
"Debian's 25 successful years of popcon proves that undoubtedly…"
You're using words like "proves" and "undoubtedly" without understanding the most basic things about logic, thinking that you're convincing. Maybe others, but I see past your logical fallacies. Funny.
----------------
@17
"Funny you should appeal to objectivity, when your statement isn't true. Opt-out is worse from a privacy-focused viewpoint. It is better if you *only* consider the viewpoint of the one collecting (and supposedly "needing") the data. Nice fallacy. =)"
Funny that you're speaking of fallacies. The burden of proving that the aspect of opt-out/opt-in and the aspect of whether data collected breaches the privacy of the users it was collected from is on you. Since you've mindlessly assumed this unproven base assumption without backing it up in the first place, you've just ironically made fallacy! Congratulations. I, in contrast, have *proven* that opt-out is always at least as good as opt-in for gathering representative statistics, so yeah, it is objectively better than opt-in schemes, because there's nothing to lose and it unlocks the potential for better stats.
"Another nice fallacy. No-one has the *right* to collect someone else's information. Information should be voluntarily given, not taken."
Of course it is a right. Nobody forces you to run any privacy-invasive free-as-in-freedom operating system.
"Information should be voluntarily given, not taken."
You have already volunteered, the moment you chose to install that operating system. Perhaps you think that because the operating system is free as in freedom, you have the right to run the OS and hold the developers legally or morally responsible for whatever you dislike in it. Perhaps you forget that the OS is given to you under a license; it doesn't even matter which license, because the mere concept of licensing is based on the principle that somebody gives you access to their copyrighted creation provided that you agree to their conditions. It is the creator who has the right to design their creation however they like. And perhaps you forget that you cannot hold developers liable for any damages that occur to you rising from your use of the software.
"That's one huge difference between the legal systems…"
Funny that you talk about law.
"Arguing for unregulated…"
I didn't argue about any regulation. I had argued about morals, copyright law, and technical advantages and disadvantages of opt-in and opt-out telemetry schemes.
"…and opt-out data collection is idiocy…"
Idiocy? Prove that I am an idiot. You'll have a hard time doing it, because I ain't one.
"…especially if you make fallacies like you."
lol
"How the *supposedly* different mindsets of Debian- and Fedora users come into the topic of data collection is beyond reason..."
Perhaps the reason is beyond you, so here it is: Users either seek or don't seek telemetry collection settings, and (assuming that there's telemetry collection and a setting to control it, which is a fair assumption because it's exactly relevant to the topic at hand) are presented either with an already enabled setting ("out-out") or already disabled ("opt-in"). Given that all other aspects of the telemetry collection is the same in all evaluated cases (which again is a fair assumption because it's relevant to the argument at hand), users that do seek telemetry settings will get the same result with either opt-in and opt-out schemes, while users who don't seek will get different results and affect the amount of telemetry that the developers ultimately collect. The question is, which users fall into the category of the users who do seek such options, and which users don't? This question is directly relevant to the discussion because, as I've explained, the natural categorization of users into these two categories is what changes whether the telemetry collected could be more complete or less complete. Mindsets of users is what makes them fall into one of these two categories, which is the reason why "the *supposedly* different mindsets of Debian- and Fedora users come into the topic of data collection".
19 • @18 (by Andy Prough on 2023-07-12 22:06:29 GMT from United States)
>"You cannot deduce anything from this data, you can only induce, and induction isn't a logical way to get conclusions, it uses intuition, and thus it's prone to failure."
That's a nice word salad that amounts to nothing, just like the rest of your responses.
I've refuted Fedora's claim that "opt-in metrics are not very useful" with solid evidence from a successful and robust opt-in telemetry program that's been run for decades. The vast quantity of data is available for all to view in the beautiful charts at popcon[dot]debian[dot]org. I'll rest my case and let the jury decide.
20 • @19 Debian Fedora data (by Mr. Moto on 2023-07-13 09:01:39 GMT from Japan)
I'm undecided. I use both Fedora and Debian. When I boot Fedora I get a strong urge to share all my data. When I boot Debian, I suddenly dear for my privacy. Gonna have to choose one or the other as I'm already in the early stages of dissociative identity disorder.
21 • IBM and Red Hat sources (by Jan on 2023-07-13 09:17:24 GMT from Poland)
It seems that IBM is making the same mistake with Red Hat it did with OS/2.
Instead of encouraging Red Hat's even wider adoption and forgetting a bit about enforcement of strict licensing behaviour (forgetting about the short term fiscal goals as Microsoft initially did with Windows)) it clamps down on the user community alienating any good will towards themselves or their product.
If we exclude the possibility of poor judgement, intentional unprofessional behaviour and lack of basic product knowledge, we must assume this IBM's move is exactly the extinguish part of the process of eliminating Red Hat (and Linux in the long term) from existence. We know that linux will never go away, and IBM will exist for as long as the governments need to control their citizens, but it is very likely that IBM will loose its place in the linux world the same way it lost the PC and PC operating system markets. And opt-out telemetry in Fedora is just a confirmation of a complete disregard of everyone's right to privacy and to a complete control over their personal data.
22 • Fedora Telemetry vs. Privacy (by Cubehead on 2023-07-13 14:12:49 GMT from Netherlands)
I definitely am not against the "submit telemetry data switch" in Fedora—without collecting some reliable telemetry data, it is nowadays impossible to develop a reliable product. There is some new HW product almost every day, and one cannot rely on users to be willing to send bug reports, and even less that they are even capable of doing it—even less if it then needs some bug-report account somewhere. Check out the Steam forums to better understand what I mean. "I can't interact with objects (because I skipped the literally very first thing I saw—screen setup)." ;)
Such collecting of telemetry data might have worked in the case of Debian, but Debian and Fedora users are two completely different worlds and mindsets. Many servers across the world run on Debian, and probably the majority of those who sent telemetry data were some Debian admins who have an interest in improved reliability. Fedora is not used as a server platform, and "privacy-aware Joe average," who doesn't understand how the stuff works, won't bother helping the product's development.
It is also important to understand that collecting the telemetry data isn't an attack on your privacy—you lost your privacy that moment when you connected to the internet. Namely, at that moment when you start installing your OS and you have an internet connection, one could start logging server calls, and on each update or software install one would get more data; you'd be again connecting the same repositories, and at the end, if those calls are connected together, one could make an exact profile of each single PC if one only wanted to—they could track you until your entrance doors. What they can't see is that out of 1 million users, gnome-shell crashed 700'000 times on startup, and that's the exact point of telemetry.
This is how the standard setup routine works in Fedora:
https://ibb.co/qpmCCqY
After the OS installation is finished and upon reboot, the user gets the following 8 screens to read, answer, or enter the data. One switch more wouldn't make the day.
23 • Wow (by Dan on 2023-07-13 21:34:16 GMT from Israel)
@19
"word salad that amounts to nothing"
Could you please do what I've done (and still do, right here right now)? That is, back up your argument with details, instead of putting a shallow response like a "word salad"? Take claims I wrote and answer them directly instead of labeling them without backing up with reasoning and details. There's no use in labeling arguments without directly addressing what's brought up in them (or not brought up, in your case). You've got to try a bit harder to be convincing.
"I've refuted Fedora's claim that "opt-in metrics are not very useful" with solid evidence…"
Except our argument here wasn't about that. Whether opt-in schemes are good or useful is completely irrelevant. Reminder: We were comparing opt-in telemetry schemes to opt-out, we weren't discussing whether opt-in schemes are good by themselves. Objectively, opt-out is better than opt-in. Again, perhaps you have limited comprehension skills, so I'll say it again: Opt-out is proven to be *at least* as good as opt-in schemes of telemetry in practice, and objectively it's *always the better choice* because it unlocks the potential for better statistics.
----------------
@20
"…I use both Fedora and Debian. When I boot Fedora I get a strong urge to share all my data. When I boot Debian, I suddenly dear [sic] for my privacy…"
…
"I use both Fedora and Debian"
Seriously? Seriously?? The mindsets of Debian and Fedora users are different because the userbase is different. This should have been obvious. Are you really that stupid to misunderstand the argument as if I was speaking about an intersection of the Debian and Fedora userbases together, implying that switching operating systems causes them to mentally think differently? What the hell dude? Let's see what my first mentioning of this was:
@15 "…Second, Debian and Fedora might have users with completely different mindsets…"
Did you really read this and think I was talking about users who use both Debian and Fedora and have different mindsets for each? Either you're stupid af or you're a next-level troll.
@22 "…but Debian and Fedora users are two completely different worlds and mindsets…"
At least this commenter gets it.
Number of Comments: 23
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 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 |
| • Issue 1121 (2025-05-12): Bluefin 41, custom file manager actions, openSUSE joins End of 10 while dropping Deepin desktop, Fedora offers tips for building atomic distros, Ubuntu considers replacing sudo with sudo-rs |
| • Issue 1120 (2025-05-05): CachyOS 250330, what it means when a distro breaks, Kali updates repository key, Trinity receives an update, UBports tests directory encryption, Gentoo faces losing key infrastructure |
| • Issue 1119 (2025-04-28): Ubuntu MATE 25.04, what is missing from Linux, CachyOS ships OCCT, Debian enters soft freeze, Fedora discusses removing X11 session from GNOME, Murena plans business services, NetBSD on a Wii |
| • Issue 1118 (2025-04-21): Fedora 42, strange characters in Vim, Nitrux introduces new package tools, Fedora extends reproducibility efforts, PINE64 updates multiple devices running Debian |
| • Issue 1117 (2025-04-14): Shebang 25.0, EndeavourOS 2025.03.19, running applications from other distros on the desktop, Debian gets APT upgrade, Mint introduces OEM options for LMDE, postmarketOS packages GNOME 48 and COSMIC, Redox testing USB support |
| • Issue 1116 (2025-04-07): The Sense HAT, Android and mobile operating systems, FreeBSD improves on laptops, openSUSE publishes many new updates, Fedora appoints new Project Leader, UBports testing VoLTE |
| • Issue 1115 (2025-03-31): GrapheneOS 2025, the rise of portable package formats, MidnightBSD and openSUSE experiment with new package management features, Plank dock reborn, key infrastructure projects lose funding, postmarketOS to focus on reliability |
| • Issue 1114 (2025-03-24): Bazzite 41, checking which processes are writing to disk, Rocky unveils new Hardened branch, GNOME 48 released, generating images for the Raspberry Pi |
| • Issue 1113 (2025-03-17): MocaccinoOS 1.8.1, how to contribute to open source, Murena extends on-line installer, Garuda tests COSMIC edition, Ubuntu to replace coreutils with Rust alternatives, Chimera Linux drops RISC-V builds |
| • Issue 1112 (2025-03-10): Solus 4.7, distros which work with Secure Boot, UBports publishes bug fix, postmarketOS considers a new name, Debian running on Android |
| • Issue 1111 (2025-03-03): Orbitiny 0.01, the effect of Ubuntu Core Desktop, Gentoo offers disk images, elementary OS invites feature ideas, FreeBSD starts PinePhone Pro port, Mint warns of upcoming Firefox issue |
| • Issue 1110 (2025-02-24): iodeOS 6.0, learning to program, Arch retiring old repositories, openSUSE makes progress on reproducible builds, Fedora is getting more serious about open hardware, Tails changes its install instructions to offer better privacy, Murena's de-Googled tablet goes on sale |
| • Issue 1109 (2025-02-17): Rhino Linux 2025.1, MX Linux 23.5 with Xfce 4.20, replacing X.Org tools with Wayland tools, GhostBSD moving its base to FreeBSD -RELEASE, Redox stabilizes its ABI, UBports testing 24.04, Asahi changing its leadership, OBS in dispute with Fedora |
| • Issue 1108 (2025-02-10): Serpent OS 0.24.6, Aurora, sharing swap between distros, Peppermint tries Void base, GTK removinglegacy technologies, Red Hat plans more AI tools for Fedora, TrueNAS merges its editions |
| • 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 | 
BunsenLabs Linux
BunsenLabs Linux is a distribution offering a light-weight and easily customizable Openbox desktop. The BunsenLabs distribution is based on Debian's Stable branch and is a community continuation of the CrunchBang Linux distribution.
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.
|
|
• 
• 
• 
• 
• 
• 
• 
