DistroWatch Weekly |
DistroWatch Weekly, Issue 1106, 27 January 2025 |
Welcome to this year's 4th issue of DistroWatch Weekly!
What is reality? What is the nature of the Universe? Are we really living in the world we perceive or are we in a vast simulation, a virtual machine of sorts? While these questions are more philosophical than technical, a real technical query is whether our operating system is running in a virtual machine or directly on physical hardware. This week, in our Questions and Answers column, we explore how to detect whether we are running programs in a virtual environment. In our News section we mostly talk about flavours of BSD this week. We begin with a look at how to draw graphics in the NetBSD terminal and share an effort to port Nix to the FreeBSD kernel. We also report on GhostBSD hosting an on-line conference to discuss and promote desktop computing on the BSD family of operating systems. Before all of that, we take quick looks at progress being made by two distributions experiencing longer than usual development cycles. We give quick updates on work going into Adelie Linux and Pop!_OS, both of which have recently published new development snapshots. In our Opinion Poll we ask our readers to weigh in on Pop!_OS's efforts with the COSMIC desktop and what the next version of the distribution will look like. Plus we are pleased to share the releases of the past week and the torrents we are seeding.
Finally, we wrap up with some news closer to home. Several readers reported this week they can no longer post or see links to DistroWatch on Facebook as Facebook now considers Linux to be malware. People wishing to keep up with and share DistroWatch-related news can use our RSS feeds and the Mastodon social network instead of Facebook. Also, we take a moment to thank everyone who sent us donations this month, we greatly appreciate your help. We wish you all a wonderful week and happy reading!
This week's DistroWatch Weekly is presented by TUXEDO Computers.
Content:
|
Feature Story (By Jesse Smith) |
Adelie 1.0 Beta 6
Sometimes, when the flow of new releases slows down, I find myself revisiting projects which are trying new things to see how they are coming along. I'm not looking at the whole project in these cases, but revisiting key elements, feature gaps, or bugs that I have noticed before in order to see what has been changed or improved.
For instance, about a year ago I tried the Adelie Linux distribution. It's a multi-architecture distribution which aims to be small and efficient while supporting multiple desktop environments. I talked about the Adelie project last year and, around the start of 2025, received an e-mail from the project indicating they were making good progress toward version 1.0.
I downloaded the latest Beta release which is offered in four desktop flavours (Plasma, LXQt, MATE, and Xfce) along with a command line only (server) option. I decided to try the LXQt edition again as I'd had mixed experienced with it and wanted to see if any of the bigger bugs had been squashed. The ISO was a 690MB download, so the size hasn't changed much.
Initial impressions
The live environment and the initial install process are pretty much the same as they were a year ago. One thing which I believe is different now is the graphical system installer allows us to not only select a desktop flavour to setup, but it also offers a text-only mode and a Custom software selection option. The Custom screen allows us to select a desktop environment, games, optional office applications, and background utilities such as network services. I decided to use the Custom approach to pick the LXQt desktop with Firefox, a few utilities, and the OpenSSH service.
The Custom approach also allowed me to make some "either or" choices. I could use Dash or Bash as the default command line shell, I could select s6 or SysV for init, and I could choose eudev or mdevd for the event daemon. Unfortunately, none of these options are explained at all in the installer. The user is expected to know what these are or do some research on their own. I also noted that while we can pick between Dash or Bash for the default system shell, the user always ends up running zsh. I'm not sure why we can pick the shell for background services, but not our own user.
Adelie 1.0 Beta 6 -- Selecting packages to install
(full image size: 246kB, resolution: 1920x1080 pixels)
As before, the system installer asks us to make up a root password and we can create up to four regular user accounts.
The Adelie installer fetches its packages from on-line repositories, meaning we need an Internet connection to perform the installation. It can also mean the install process takes a while (about 15 minutes for LXQt, about 25 minutes to set up Plasma). During this time no progress information is shown on the screen, making it seem as though the installer has locked up. However, the install process did eventually complete successfully for me.
Then and now
When I experimented with Adelie a year ago, the LXQt edition had been able to connect to the network when I was running in live mode, but once installed, the LXQt edition did not appear to have any networking tools. This meant I could install Adelie, but then not get on-line afterwards. This time the experience was worse.
Once the LXQt edition installed, it booted to a graphical login screen. Here I found that the distribution would not recognize any keyboard or mouse input. I couldn't sign in, click on any options, or even switch to a local terminal screen.
I decided to go back to the beginning and, as I had a year ago, switched to trying the Plasma desktop. I still used the LXQt live media to launch the installer, selected the Plasma desktop with Mobile profile in the installer, and (when the installer finally finished its work), I was able to boot the distribution and sign in. Since my keyboard and mouse worked with the Plasma edition it seems there are still necessary pieces included in the Plasma profile which are not included in the LXQt package selection.
A year ago, I found Adelie's Plasma 5 desktop sometimes failed to display its wallpaper properly, the network tools were tucked away, and there were two audio controls in the system tray. In 2025 not much has changed. Plasma 5 is still being used rather than Plasma 6. This time around the wallpaper and panel always displayed properly, which is a step forward. This time there are still two audio widgets which looked identical in the system tray - though one controls volume and the other opens the KDE System Settings audio controls.
Adelie 1.0 Beta 6 -- Exploring Plasma's settings
(full image size: 193kB, resolution: 1920x1080 pixels)
In an unfortunate regression, I was unable to find any network connection tools included in the Plasma edition this time. I can't imagine why networking utilities would be included on live media, but not in the installed distribution. Network Manager is available in the repositories and I could side-load it from another computer, but this seems like a terrible oversight. Networking controls are either well hidden or just not included in the Mobile computing package selection and I cannot imagine why the developers are making it this hard to get on-line.
The distribution hasn't changed much in size over the past year. Adelie required about 5.7GB of disk space last year and that has remained steady. When signed into the Plasma desktop the distribution currently uses about 400MB of RAM, which is on par with last year. One change I noticed was last year active RAM usage would continue to creep up fairly rapidly, even when the system was idle, slowly consuming all available memory. In 2025 I found RAM topped out at about 440MB if I just signed in and left Plasma idle.
When I used Adelie a year ago I pointed out some quirks of the distribution. These were not bugs or problems, but unusual behaviours. For example, the distribution does not include access elevation tools such as sudo or doas. To perform administrative functions we need to login as root or use the su command. Another interesting quirk is there is no clear command, and Adelie might be the only distribution I know of that doesn't include the command to clear the terminal. These features (or lack of features) are all the same today as they were a year ago.
Adelie 1.0 Beta 6 -- Performing privileged actions
(full image size: 146kB, resolution: 1920x1080 pixels)
Another thing which hasn't changed is Adelie places the APK package manager in the root's executable path, but not the user's path. This means regular users cannot "see" the apk command. To run the package manager they need to become root, change their default path, or supply the full pathname for the apk command (/sbin/apk). This isn't a bad arrangement, but it does mean more steps or more typing when we want to perform searches for packages.
Conclusions
It seems not much has changed for Adelie over the past year. To the team's credit, it looks as though they've fixed the expanding memory consumption bug and that is great. On the other hand, there are more severe problems with the LXQt edition and I found it even harder to get on-line with the Plasma flavour than before. The odd quirks, like two identical audio widgets in the system tray persist and the system installer still doesn't show progress. On the whole, this release felt like it took one step forward, but two steps back.
Adelie 1.0 Beta 6 -- Dual audio widgets
(full image size: 115kB, resolution: 1920x1080 pixels)
* * * * *
Pop!_OS 24.04 Alpha 5
It's only been five months since my last experience with Pop!_OS and its new COSMIC desktop. When I tried out its initial development snapshot back in September, I found the COSMIC desktop had some interesting ideas behind it, but it was lacking features, window management was awkward, and the environment was unstable. I was curious to see what new options, applications, and improvements had been made.
Pop!_OS continues to be offered in two editions, Intel/AMD and NVIDIA. The download is about 2.5GB in size, which hasn't changed in the past five months. The install process all appears to have remained unchanged since I last tried the distribution.
Then and now
Once I had installed the distribution I found it booted to a graphical login screen where I could sign into the COSMIC desktop. COSMIC, it's worth mentioning, offers a Wayland session only; there is no X11 session.
Signing into COSMIC requires 1.5GB of RAM. This surprised me as the same desktop on the same laptop used 1.0GB five months ago. In the past five months the desktop's active memory usage has ballooned 50%, making it one of the heaviest desktop environments in the Linux community. Disk usage, meanwhile, remains about the same at 6.7GB for a fresh install. CPU usage tended to remain fairly low, around 1.5% to 2.0% when sitting mostly idle and just running the top process monitor.
Pop!_OS 24.04 Alpha 5 -- Exploring the application menu
(full image size: 1.3MB, resolution: 1920x1080 pixels)
Five months ago I mentioned one of my biggest issues with COSMIC was how it switched between windows: "COSMIC seems to assign each window a number as it is opened. Then pressing Alt+Tab cycles through the list of open applications in the order we launched them. If we open the terminal, the file manager, and a text editor (in this order) then pressing Alt+Tab once will always jump to the terminal, even if it is already the active window. Pressing Alt and then tapping Tab three times will always raise the text editor into focus."
Alt+Tab behaviour has changed in the latest Alpha snapshot, placing it more in line with how other desktops behave. Alt+Tab now cycles through windows in the order they've been recently accessed, not the order in which they were launched. This makes it easier to toggle rapidly between two tasks.
Five months ago I pointed out when running COSMIC I couldn't use menu keyboard shortcuts. For example, typing Alt+F doesn't open the active window's File menu, Alt+V doesn't open the View menu, etc. This behaviour remains the same and it makes navigating application menus awkward if you're accustomed to keeping your hands on the keyboard.
In my previous trial COSMIC crashed a couple of times in my three-day trial. This time the desktop didn't fully crash, but sometimes the application menu button on the dock would stop working. This made it hard to open new programs. Logging out and then signing back in seemed to be the only way to fix the application menu.
Software management
Pop!_OS's software centre is a functional, modern software centre. It handles working with both Deb packages (called "system" packages) and Flatpak bundles. My only complaint with the software centre five months ago was it constantly asked me for my password before every action (installing, removing, or updating packages). This behaviour has remained much the same, with each addition or removal of a Deb package requiring a password. Installing new Flatpak bundles does not require our password though.
Pop!_OS 24.04 Alpha 5 -- Managing software packages
(full image size: 1.7MB, resolution: 1920x1080 pixels)
New items
The big, new item in COSMIC is the COSMIC media player. This player is launched if we try to open any media file from the file manager. The new COSMIC application was able to play audio files for me, but it completely failed to work with video files. Any time I'd try to launch a video a message would appear in the player's window which read: "No video open." When this happened it would also disable the player's File menu, preventing me from trying to open another file.
Pop!_OS 24.04 Alpha 5 -- Trying to play a video file
(full image size: 1.4MB, resolution: 1920x1080 pixels)
There are new categories in the COSMIC settings panel. There were previously six categories or tabs available for us to browse in the two-pane panel: Desktop, Displays, Power and Battery, Input Devices, Time and Language, and System and Accounts. These six have been joined by two more categories: Bluetooth and Network & Wireless.
The Bluetooth section is probably self-explanatory, it helps us link our system with Bluetooth devices in the area. Networking is also about what we would expect, helping us view and connect with local networks. Under the networking section there is a button for managing VPN connections. When I clicked on the button for adding a VPN connection an error was displayed which read: "Failed to add VPN config - open dialog failed." So it seems Pop!_OS is ready to network, but not to network privately.
Pop!_OS 24.04 Alpha 5 -- Trying to enable a VPN connection
(full image size: 1.5MB, resolution: 1920x1080 pixels)
Five months ago I wrote "A problem I ran into was, when the settings panel was open, it constantly used around 20% to 25% of my laptop's CPU. This eventually caused the fan to run as the laptop would heat up. No other COSMIC applications had this problem, only the settings panel would constantly gobble up available CPU cycles."
This problem persists and it causes the fan to kick in on my laptop after a few minutes. This doesn't happen with other COSMIC applications and it seems to be a problem with the application window being constantly redrawn (judging by how hard it is impacting the window manager's CPU usage), even when nothing is happening on the screen. It's discouraging this hasn't been addressed in the past five months.
Conclusions
I feel that Pop!_OS, mostly through its COSMIC desktop, has made a few improvements over the past five months. The improved window switching order is definitely a perk and makes it nicer to work with multiple applications. I'm also happy to see the settings panel is expanding, bringing in new options, and the desktop appears to be more stable now than it was five months ago.
On the other hand, there were a lot of problems (both new and old) in this Alpha snapshot. Memory usage has gone up 50% but there are no new user-visible features in the default desktop. COSMIC is now one of the heaviest desktops around, but it has one of the smaller feature sets. The media player failing and locking up when trying to play video files wasn't a good sign and it put a dark mark on this new application's debut. Likewise, I was happy to see the networking section of the settings panel appear, only to be disappointed to discover the VPN section doesn't work yet.
Mostly I was disappointed at the issues which remain. The software centre still nags for our password instead of caching permissions/credentials, the settings panel still hungrily gobbles up CPU cycles, menu shortcuts still don't work, and there are still a few stability issues. At this rate, it seems unlikely COSMIC will be ready for a stable release prior to 2026.
This situation makes me wonder how System76 plans to handle the situation. The company has a few options before them, none of which are likely appealing to management. The company could reverse course and publish a new Pop!_OS release featuring their old GNOME environment and admit building a desktop is taking longer than expected. They could publish a new release of the distribution before COSMIC is ready, risking unhappy customers, or they could wait and ship COSMIC when it's ready - maybe as a 26.04 release. The last option currently seems the most likely, but that would mean there were four years between the company's LTS releases, which quite a gap for a company that sells expensive laptops to developers and gamers. I don't envy the people who need to make the decisions in this scenario.
* * * * *
Hardware used in this review
My physical test equipment for this review was an HP DY2048CA laptop with the following
specifications:
- Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
- Display: Intel integrated video
- Storage: Western Digital 512GB solid state drive
- Memory: 8GB of RAM
- Wireless network device: Intel Wi-Fi 6 AX201 + BT Wireless network card
* * * * *
Visitor supplied rating
Pop!_OS has a visitor supplied average rating of: 8.1/10 from 249 review(s).
Have you used Pop!_OS? You can leave your own review of the project on our ratings page.
|
Miscellaneous News (by Jesse Smith) |
Drawing graphics in a terminal with NetBSD, Nix package manager ported to FreeBSD kernel, GhostBSD hosting desktop conference
People who are interested in low-level graphics, programming, or just how to do neat tricks with a terminal may be interested in this tutorial. Julio Merino demonstrates how to draw graphics directly to the screen without needing to use Wayland or an X11 display server. "The EndBASIC console can now run directly on a framebuffer exposed by the kernel. No X11 nor Wayland in the picture (pun intended). But how? The answer lies in NetBSD's flexible wscons framework, and this article dives into what it takes to render graphics on a standard Unix system. I've found this exercise exciting because, in the old days, graphics were trivial (mode 13h, anyone?) and, for many years now, computers use framebuffer-backed textual consoles. The kernel is obviously rendering 'graphics' by drawing individual letters; so why can't you, a user of the system, do so too?" The tutorial goes on to demonstrate how to create graphics without relying on popular graphics technologies such as X11.
* * * * *
The NixOS project develops a Linux distribution centred around the Nix package manager. Nix has gained a lot of attention for its ability to manage not just packages, but also services and users in a declarative manner. The NixBSD project seeks to port Nix and its related components to a FreeBSD kernel. "NixBSD is an attempt to make a reproducible and declarable BSD, based on NixOS. Although theoretically much of this work could be copied to build other BSDs, all work thus far has been focused on building a FreeBSD distribution." So far no live ISO file has been produced, but building the base and running the operating system in a virtual machine is an option.
* * * * *
The GhostBSD project is organizing an on-line conference which will promote and discuss desktop computing on BSD bases. "GhostBSDCon 2025 is an inaugural on-line technical conference. High quality technical papers and engaging community presentations will be curated to support ongoing technical development and *BSD community experiences." The forum post links to a PDF with more details.
* * * * *
These and other news stories can be found on our Headlines page.
|
Questions and Answers (by Jesse Smith) |
Are we inside a virtual machine?
Are we inside a virtual machine? This isn't a philosophical question or a query about the nature of our existence. Rather, I'm talking about whether the computer environment we are using is running on physical hardware directly or if our programs are running in a virtual machine.
This sometimes matters when we are measuring resource usage, testing security, or determining which filesystem might best suit our situation. It could also be useful for determining whether the host provider we are working with really gave us physical machines for running servers or if they set us up with some virtual private servers (VPS) and hoped no one would notice the difference.
There are a few ways to determine if we are operating inside a virtual machine. I'm going to mention five of the easiest ways to quickly check if our operating system is running on bare metal hardware or in a virtual machine. These approaches generally do not require installing additional packages beyond what most Linux distributions provide in a default installation.
One approach is to look at boot messages from the kernel. We can do this by running the following command as the administrator (either by logging in as root or using sudo):
dmesg | grep -i hypervisor
In situations where we are operating inside a virtual machine we should see output which looks like this:
[ 0.000000] Hypervisor detected: KVM
However, if we are not working inside a virtual machine, then there should be no output from the dmesg command shown above.
Another approach is to use the lshw (list hardware) command and look at the first ten lines of output. We can filter output down to these first ten lines using the head command:
lshw | head
In particular, look at the Product and Vendor fields in lshw's output. On a physical machine we should see a vendor field which lists an OEM, such as "HP" or "Lenovo". When running in a virtual machine we will see a Product field which mentions the type of virtual machine, such as "VirtualBox" or "KVM".
Another utility we can use to check the environment is dmidecode. This tool checks BIOS information. Here we check for the machine's manufacturer:
dmidecode -s system-manufacturer
When run on physical hardware, the above command should output the name of an OEM, such as Lenovo, HP, or Dell. When run inside a virtual machine the above command will likely report something like "KVM", "GmbH", or "VMware".
People who run the systemd init software have another utility called systemd-detect-virt. This program can be run without arguments:
systemd-detect-virt
It should simply output "none" when running on physical hardware or the name of the virtual machine provider. For instance, when running in VirtualBox (which is owned by Oracle), the above command displays "oracle".
Also, for people who run systemd as their init software, there is a fifth tool. The hostnamectl command will tell us information about the underlying machine, real or virtual.
hostnamectl
The above command will print around a dozen fields of information about the name of the computer, its systemd Machine ID, the name of the operating system, and its kernel version. In particular, we want to look at the Virtualization and Hardware Model fields of the hostnamectl output. When run in a virtual machine these fields will say things like "KVM" or "VirtualBox" or "oracle".
There are additional ways to check for signs of running inside a virtual machine, but they usually require downloading additional tools. These five approaches are relatively simple and stick to using commands found on most distributions.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
Released Last Week |
BSD Router Project 1.994
BSD Router Project (BSDRP) is an embedded free and open-source router distribution based on FreeBSD. The project's latest release is version 1.994 and uses the FreeBSD 15 development branch. "Starting with this version, BSDRP requires at least a 4GB disk. If you installed BSDRP on a 2GB disk, upgrading will not be possible. However, if it was installed on a 4GB or larger disk, you can resize the system partition using the following command: 'system resize-system-slice 3921924'. New features: This is an intermediate release preparing the branch 2 that will use the poudriere-image framework in place of NanoBSD. Based on FreeBSD 15-head 8f6b66a9d3f and ports tree. New packages: dns/dnsmasq (will replace isc-dhcp44 and dhcprelya); Python 3.11 (this one added more than 100M of libs). Removed packages: freevrrpd (carp is now supporting VRRP mode); ucarp (no more conflict once carp enabled in VRRP mode); net/aquantia-atlantic-kmod (does not build on latest head). Deprecated packages (will be removed in next release): isc-dhcp44 (use dnsmasq, kea requires 300MB disk space with its dependencies); dhcprelya (use dnsmasq)." The release notes offer more information.
Solus 4.7
The Solus project develops an independent, rolling release distribution with a focus on desktop computing. The project has published Solus 4.7 (also labelled 2025-01-26) which features improved video card support and does away with the old software centre. "We encourage you to try one of the new software centres as a replacement for solus-sc (Solus Software Centre). A new software centre gets you out-of-the-box support for Flatpaks, and better app descriptions through Appstream metadata support. Our contributors and staff have been hard at work adding and fixing the metainfo.xml files used for Appstream support. Our goal is for every packaged GUI application to have a working metainfo.xml file, so that the software centres can show users all kinds of information about an app before they decide to install it. Curious Budgie, GNOME and Xfce users can install GNOME Software, while Plasma users should install Discover." Additional changes, along with screenshots, can be found in the project's release announcement.
Solus 4.7 -- Running the Budgie desktop
(full image size: 2.0MB, resolution: 1920x1200 pixels)
* * * * *
Development, unannounced and minor bug-fix releases
|
Torrent Corner |
Weekly Torrents
The table below provides a list of torrents DistroWatch is currently seeding. If you do not have a bittorrent client capable of handling the linked files, we suggest installing either the Transmission or KTorrent bittorrent clients.
Archives of our previously seeded torrents may be found in our Torrent Archive. We also maintain a Torrents RSS feed for people who wish to have open source torrents delivered to them. To share your own open source torrents of Linux and BSD projects, please visit our Upload Torrents page.
Torrent Corner statistics:
- Total torrents seeded: 3,149
- Total data uploaded: 46.3TB
|
Upcoming Releases and Announcements |
Summary of expected upcoming releases
|
Opinion Poll (by Jesse Smith) |
What should System76 do with Pop!_OS?
In our Feature Story this week we talked about Pop!_OS and the progress of its custom COSMIC desktop environment. Pop!_OS 24.04 was originally expected to launch in the middle of 2024 and would use Ubuntu 24.04 LTS as its base. However, the 24.04 release has yet to be published and the developers didn't bother to put out their usual x.10 release toward the end of the year. This has left some questions as to what the next release of Pop!_OS can or should look like.
Will System76 continue to work on COSMIC running on the 24.04 LTS base? Will they publish an interim 25.x release featuring an incomplete COSMIC? Will they backtrack and ship a version with their previous GNOME desktop? Perhaps they'll wait for the next LTS cycle (Ubuntu 26.04) before publishing a stable COSMIC? There are at least these four options and we'd like to hear what you think System76 should do with their distribution.
You can see the results of our previous poll on CentOS 10 Stream in our previous edition. All previous poll results can be found in our poll archives.
|
What should System76 do with Pop!_OS?
Publish 24.04 with GNOME: | 329 (17%) |
Wait for COSMIC to mature and publish an out of date 24.04: | 140 (7%) |
Rebase on an interim 25.x release and ship with a beta of COSMIC: | 139 (7%) |
Ship a 25.04 interim release with GNOME: | 149 (8%) |
Wait for 26.04 and ship a stable COSMIC: | 420 (21%) |
Something else (in comments): | 792 (40%) |
|
|
Website News |
Facebook ban
Starting on January 19, 2025 Facebook's internal policy makers decided that Linux is malware and labelled groups associated with Linux as being "cybersecurity threats". Any posts mentioning DistroWatch and multiple groups associated with Linux and Linux discussions have either been shut down or had many of their posts removed.
We've been hearing all week from readers who say they can no longer post about Linux on Facebook or share links to DistroWatch. Some people have reported their accounts have been locked or limited for posting about Linux.
The sad irony here is that Facebook runs much of its infrastructure on Linux and often posts job ads looking for Linux developers.
Unfortunately, there isn't anything we can do about this, apart from advising people to get their Linux-related information from sources other than Facebook. I've tried to appeal the ban and was told the next day that Linux-related material is staying on the cybersecurity filter. My Facebook account was also locked for my efforts.
Blocked by Facebook
(full image size: 102kB, resolution: 688x722 pixels)
We went through a similar experience when Twitter changed its name to X - suddenly accounts which had been re-posting news from our RSS feeds were no longer able to share links. This sort of censorship is an unpleasant side-effect of centralized communication platforms such as X, Facebook, Google+, and so on.
In an effort to continue to make it possible for people to talk about Linux (and DistroWatch), as well as share their views and links, we are providing two options. We have RSS news feeds which get updates whenever we post new announcements, stories, and our weekly newsletters. We also now have a Mastodon account where I will start to post updates - at least for new distributions and notice of our weekly newsletter. Over time we may also add news stories and updates about releases. Links for the feeds and the Mastodon account can be found on our contact page.
* * * * *
Donations and Sponsors
Each month we receive support and kindness from our readers in the form of donations. These donations help us keep the web server running, pay contributors, and keep infrastructure like our torrent seed box running. We'd like to thank our generous readers and acknowledge how much their contributions mean to us.
This month we're grateful for the $262 in contributions from the following kind souls:
Donor |
Amount |
Patrick M | $100 |
Doug S | $50 |
J S | $50 |
Ppb | $13 |
Jonathon B | $10 |
Sam C | $10 |
Brian59 | $5 |
Chung T | $5 |
surf3r57 | $5 |
TaiKedz | $5 |
J.D. L | $2 |
PB C | $2 |
aRubes | $1 |
Stephen M | $1 |
Kai D | $1 |
Shasheen E | $1 |
William E | $1 |
* * * * *
New distributions added to waiting list
- Bluefin. Bluefin is a desktop distribution which features the GNOME desktop, a cloud-focused approach, and atomic updates.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 3 February 2025. Past articles and reviews can be found through our Weekly Archive and Article Search pages. To contact the authors please send e-mail to:
- Jesse Smith (feedback, questions and suggestions: distribution reviews/submissions, questions and answers, tips and tricks)
- Ladislav Bodnar (feedback, questions, donations, comments)
|
|
Tip Jar |
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip. (Tips this week: 8, value: US$37.06) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
|