 DistroWatch Weekly |
| DistroWatch Weekly, Issue 1173, 18 May 2026 |
|
Welcome to this year's 20th issue of DistroWatch Weekly!
Have you ever wanted to set up a FreeBSD server, maybe with some virtual machines or jails, but didn't want to wander down the path of manual configuration and command line tools? If so then the Sylve administration tool offers a solution. Sylve is a web-based administration tool which can be used to remotely administer FreeBSD systems. The web-based experience makes it possible to create and manage jails and virtual machines with a few clicks. This week we begin with a look at an early version of Sylve and report on the experience it provides. In our Questions and Answers section we talk about another administrative tool, BleachBit, and how it can be used to tidy filesystems. Do you have a filesystem cleaner that you like to use? Let us know your preferred clean-up method in the Opinion Poll. In our News column we talk about Debian's commitment to reproducible builds while Haiku introduces multi-core support for ARM64 processors. We share an update on Fedora's plans, and reversal, to include AI tools and applications in a new spin. We also report on KDE receiving a generous donation to help support the project's infrastructure while Rocky Linux introduces a new security repository. This week we link to an in-depth commentary on the technology sector and open source culture as well as summarize the releases of the past week. 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) |
Sylve on FreeBSD
One of the projects which has been mentioned in recent FreeBSD quarterly status reports is Sylve. What is Sylve?
"Sylve is an open-source control panel for FreeBSD virtualization and storage. It brings Bhyve, FreeBSD Jails, and ZFS into one modern web UI.
The backend is written in Go, and the frontend uses Svelte/SvelteKit. The goal is simple: manage guests, containers, and datasets without living in shell scripts."
The Sylve website goes into further details, outlining the key features:
What Sylve Delivers: Bhyve management: Create, start, stop, snapshot, and console into VMs. Configure CPU, memory, PCI passthrough, VNC, and serial access from the same place.
Jails with VM-like workflows: Jails follow the same lifecycle model as VMs, with networking, datastores, limits, and console/shell access.
ZFS-first storage: Manage pools, datasets, disks, and datastores in one interface, with clear VM/Jail storage mapping.
Network and service controls: Configure physical interfaces, virtual switches, and DHCP scopes, with optional integrations like Samba and libvirt.
According to the project's documentation, Sylve's web portal requires about 400MB of RAM. We are also told that Sylve requires ZFS; it will not work properly on FreeBSD systems that run on classic filesystems, such as UFS.
Installing
The Sylve website and documentation say to install the control centre we can run "pkg install sylve" to get started, as long as we are running FreeBSD 15.0 or higher.
I logged into a FreeBSD 15.0 system running ZFS and ran the above command. I was told this package, sylve, did not exist in the repository. I did a search for any package with "sylve" in the name, thinking perhaps it had been renamed as something like "sylve-go" or "sylve-admin", but no matches were returned.
On a hunch, I switched the FreeBSD package manager over from the operating system's default "quarterly" release repository to the cutting-edge "latest" repository. In the "latest" branch the sylve package was found and I was able to install it. The requirement of switching the default repository on FreeBSD should probably be mentioned in the Sylve documentation and on the website to avoid confusion, but (eventually) the quarterly branch will catch up and the situation will resolve itself.
The Sylve documentation states that once the package has been installed, we will be able to use a web browser to connect to the remote control panel over port 8181. The documentation skips over two key pieces of information. First, we first need to activate the Sylve service (running "sysrc sylve_enable="YES" ; service sylve start" as the root user will accomplish this). Second, our web browser must connect over the HTTPS protocol to the server's port 8181; connecting over plain HTTP will return an error message.
Connecting to port 8181 in a web browser displays a login screen. We are asked to provide a username and password. By default the interface uses "sylve" as an authentication method (which will presumably use an internally defined account), but if we want to sign in with a regular user account we need to switch the login method to "PAM".
I signed in as a regular system user. Sylve brings up a page which asks us which services, such as virtualization, ZFS management, and Samba we want to manage. Once we make selections the web interface says it needs to restart the server. I was a bit surprised my regular user was able to perform this confirmation and perform a system reboot through the Sylvie web portal. My regular user was not part of the wheel or operator group and normally could not perform any admin actions.
Exploring the web interface
After the system reboots our browser automatically reconnects to the Sylve service and displays a status dashboard. To the left of the web interface is a tree-style view showing Sylve nodes and machines we control. We can click on a machine name in order to see a summary of on-line nodes with resource usage statistics. There is a place in the tree for seeing notes related to the machines in a group. We can view clusters of machines and create new clusters from this tree view. There is another section in this view for seeing backups.
At first, there isn't much for us to do with this tree of information because we just have the one node, with no jails, backups, or clusters. The tree of nodes will become more interesting at a later time.
In the upper-right corner of the page we see buttons for creating new virtual machines and jails. There are also buttons at the top of the page for accessing help and sponsoring the project. The Help button opens the Sylve on-line documentation.
At the bottom of the screen we can see a list of recent logins and login attempts to the Sylve dashboard.
Mostly, for the sake of this trial, I was interested in creating jails, a few for various purposes, and then seeing if I could easily manage them from the central dashboard. Clicking the button to create a new jail opens a pop-up in the Sylve interface with five tabs:
- Basic - Provide a name and description for the new jail.
- Storage - Select which ZFS pool to use for the new jail.
- Network - Inherit host networking or disable networking for the jail.
- Hardware - Assign CPU cores, maximum memory, and toggle whether to start a jail on system boot.
- Advanced - This screen asks if we want to create a FreeBSD or Linux jail. It also allows us to set which process(es) to run when the jail starts and what command to run when the jail shuts down.
The pop-up for virtual machine (VM) creation is almost exactly the same, but with a bit more flexibility with low-level resource allocation. It also allows us to pick the install media we wish to use.
One of the first tasks I performed was creating a jail for a public FTP service. I clicked the Create Jail button and went through the screens mentioned above. Once I got to the end and clicked the Create button Sylve reported I had not selected a "base". Going back a few steps I found that on the Storage tab we are asked to pick a ZFS pool (zpool) where the jail will be located. We are also asked to select a "base" from a drop-down menu. Unfortunately, no base was listed in the drop-down menu and it wasn't clear from the context what Sylve meant by a "base".
Sylve -- Creating a new jail
(full image size: 102kB, resolution: 1491x839 pixels)
The documentation proved useful at this point. It explains that "base" in this case refers to one of the classic package sets used by FreeBSD:
In the Storage tab, you can select the dataset where (pool) the jail's root filesystem will be created, you also have to select a base that you downloaded. You can download a base.txz from https://download.freebsd.org/releases/amd64/15.0-RELEASE/base.txz using the downloader (remember to select the correct architecture and version) and also to enable extraction in the downloader.
Sylve -- Missing a base for the jail
(full image size: 116kB, resolution: 1491x839 pixels)
This explained what the storage screen meant by a "base", but it raised a new question: What downloader was the documentation referencing? With some exploration of the web portal I found I could click on the name of my FreeBSD server in the information tree on the left side of the page. Selecting the server brought up options for working with the server, adjusting its networking settings, viewing its storage, and accessing a terminal. The terminal is automatically logged is as the root user. There is a section in this tree called Utilities and under this sub-section we find a tool called Downloader. This tool accepts a URL and will display progress as a file is fetched. I used this downloading tool to fetch the base.txz file from the FreeBSD servers.
Sylve -- Using the Downloader utility
(full image size: 127kB, resolution: 1491x839 pixels)
I then tried to create a jail again. This time, on the Storage screen, the "base" package I'd just downloaded appeared in the drop-down menu and I selected it. When I got to the end of the jail creation tabs a new error appeared which stated, "select base image could not be found on disk". This baffled me as not only had I downloaded the base.txz file, the jail creation wizard had found it and added it to the drop-down menu for me to select. It was reporting a file it had detected and offered to me could not be found.
I then remembered the documentation had specified the downloaded base.txz file needed to be unpacked before it could be used by the jail creation wizard. I went back to the downloader utility and made sure to check the box for automatic extraction of the archive. Once this was completed, I was able to create a jail, access it in the node tree, and access its terminal to install new packages and services.
Linux jails
Since the jail creation window supports creation of both FreeBSD and Linux jails I decided to see what the process of creating a Linux jail would involve. When trying to create a Linux jail the creation window still insists that we select a "base" package. In other words, we need to find a Linux distribution which provides a minimal filesystem package (not just an ISO file).
I used the Sylve downloader tool to download Alpine Linux which provides a minimum filesystem archive. Sylve was able to unpack this tar archive and detect it as a potential base. It then created a new jail, using the userland provided by the Alpine archive and running on the host's FreeBSD kernel.
Sylve -- Running Alpine in a Linux jail
(full image size: 219kB, resolution: 1491x839 pixels)
The Alpine jail mostly worked for me. I was able to use the apk package manager to download new software, including the OpenRC service manager. From there I was able to add new services, such as OpenSSH, to provide remote access to the jail.
There are some limitations. Not all software in the Linux jail will run, at least not with the default system setup. Any tools which rely on the existence of the /proc filesystem, such as process monitors, will fail. Some more complex software, such as a web browser compiled for Linux, will likely also run into incompatibilities when trying to run on the FreeBSD kernel.
Snapshots
Sylve requires ZFS storage volumes to function and it also seeks to provide access to ZFS features, including filesystem snapshots. Through the node tree on the left side of the screen we can access storage options, including the options to create snapshots of jails and rollback to earlier snapshots. I tested these and found they worked well, allowing me to restore jails to earlier points in time. The interface is pleasantly simple, making basic snapshot management fairly easy.
Sylve -- Managing ZFS snapshots
(full image size: 98kB, resolution: 1491x839 pixels)
Conclusions
Sylve is in its fairly early stages and has just recently been added to the FreeBSD "latest" repository. Despite its youth, the Sylve software has made a strong start. The package installed successfully, the user interface is fairly easy to navigate, and the documentation covers most of the necessary information we need.
I found the Sylve dashboard, filesystem snapshot tools, and jail management tools worked (at least once I got used to the terminology used by the interface). I liked that jail networking was mostly automated with sane defaults. I was surprised by a few items, such as selecting the FreeBSD base was not automated, as it is with other jail managers, and that Sylve doesn't provide a pre-selected list of supported Linux distributions for jails. However, I suspect these are features which will come later, once the basic tools have been further refined.
Sylve -- My regular user signed in automatically to a terminal as root
(full image size: 240kB, resolution: 1491x839 pixels)
My main issue with Sylve during my trial was the near complete lack of security. Any user on the host FreeBSD system, even a completely unprivileged user, can sign into Sylve at any point - including the initial setup. Signing into the web portal grants immediate root access to any user. This allows any user to create jails and virtual machines, manage ZFS snapshots, and shutdown the system. Any regular user is also able to open the terminal window which automatically signs the user in as root without a password. This is a big security hole and basically turns the current version of Sylve into a backdoor that can be used by any local user (or single-sign-on user on the network) to become root for all managed servers, virtual machines, and jails.
This is a serious issue and I didn't see it mentioned in the documentation. I would avoid installing the Sylve service on any server until this hole is addressed. Once user authentication is fixed then the interface will provide a pleasant, central method for managing multiple machines and multiple jails across the network. The friendly, web-based interface is a much more friendly approach than most command line tools I have used in the past for VM and jail management on FreeBSD.
|
| Miscellaneous News (by Jesse Smith) |
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
The Debian project is committing to providing reproducible builds for its packages. A reproducible build allows users to confirm the binary software they are running came from published source code. Paul Gevers writes: "Aided by the efforts of the Reproducible Builds project, we've decided it's time to say that Debian must ship reproducible packages. Since yesterday, we have enabled our migration software to block migration of new packages that can't be reproduced or existing packages (in testing) that regress in reproducibility." Gevers also mentions the loong64 CPU architecture was added to the build system and new package builds may take longer as a result.
This past week the Debian project published updated install media for both Debian 13 and Debian 12. The new media includes fixes for bugs which have been discovered since the launch of the Debian Stable versions. "The Debian project is pleased to announce the fifth update of its stable distribution Debian 13 (codename Trixie). This point release mainly adds corrections for security issues, along with a few adjustments for serious problems. Security advisories have already been published separately and are referenced where available. Please note that the point release does not constitute a new version of Debian 13 but only updates some of the packages included."
* * * * *
The Haiku project has published its monthly news update for the month of April. The report provides an overview of work going into the lightweight operating system. One of the milestones reached in April was the addition of support for using multiple cores on ARM64 processors: "smrobtzz implemented basic support for SMP (multiple CPU cores/threads) for ARM64, enough for it to work in QEMU, and also fixed running with some versions of the EDK2 EFI firmware (which QEMU ships with), some problems with system_time, and other issues. smrobtzz and waddlesplash updated a lot of HaikuPorts cross-compilation recipes, cleaned up the 'bootstrapping' procedure, and then upgraded the base ARM64 package set to work properly with the new port configuration. (This means ARM64 builds using the binary packages, as is default, now work out-of-the-box on many QEMU configurations.)" The newsletter lists the complete list of improvements made over the past month.
* * * * *
The Rocky Linux distribution is a clone of Red Hat Enterprise Linux which aims to be 1:1 compatible with the upstream product. This means both features and bugs which exist in Red Hat's product should be mirrored exactly in Rocky Linux. Over the past year, and especially in the past month, the security cost of maintaining 1:1 compatibility with Enterprise Linux has become apparent. Rocky Linux developers have found themselves waiting for security fixes to be published by Red Hat while other members of the RHEL family, such as AlmaLinux OS, have already published security patches.
Rocky Linux is addressing this security gap by creating an optional security repository which will publish patches not yet available to RHEL customers. "Alongside the Dirty Frag kernel patches, we've introduced the Rocky Linux Security Repository: an optional, opt-in repository that gives us a path to ship urgent security fixes ahead of upstream when circumstances genuinely demand it. This was not a casual decision. Rocky's founding principle is compatibility with upstream Enterprise Linux, and any departure from that deserves scrutiny. The security repository represents a narrow, deliberate exception, not a change in direction."
* * * * *
Last week we reported the Fedora project was planning to introduce new AI-related tools and applications. At the time, the divisive decision had a lot of pushback from Fedora users, and some developers, but the decision was voted through anyway. The issue has been re-opened for discussion after two Fedora members have reversed their votes on the plan. One Fedora developer wrote: "Changing my vote to -1. I fear that the feedback (that was unfortunately received after the initial vote) indicates that the Fedora community is not supportive of this initiative as is. As one of the elected representatives, I feel I need to listen to that feedback and try to better understand it before I can approve this with a clear conscience." A final decision should be reached on Friday, May 22nd.
* * * * *
There was some good news for fans of the KDE project and its Plasma desktop this week. The Sovereign Tech Fund donated over one million Euros to the KDE project to assist with the project's infrastructure. The KDE project published a statement about the donation: "As a non-profit, KDE has no shareholders to serve, no quarterly earnings to grow. KDE charges nothing for its software or its licensing. There are no subscriptions, no spying on users, no disclosure or resale of data that users choose to voluntarily share with KDE, and no secret training of AI models with said data. KDE will use Sovereign Tech Fund's investment to push its essential software products to the next level, providing every individual, business, and public administration with the opportunity to regain their privacy, security, and control over their digital sovereignty."
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
The benefit of BleachBit
I was interested in trying out Emmabuntus on my laptop and noticed in another website's review that the distro comes with BleachBit, which I have never heard of. After reading about it on-line, it seems that it performs actions similar to the commands:
sudo apt autoremove
sudo apt autoclean
But, I can not find any on-line info comparing the two methods of cleaning up unused files. There must be a reason for Emmabuntus to include the program, because it is a Debian-based system, and autoremove/autoclean are already available to use with apt.
I was wondering if you could investigate and provide some professional insight with actual testing of the two methods, and provide your findings in a DistroWatch Weekly article?
DistroWatch answers: While there is a little bit of overlap in the functionality of APT and BleachBit, the two tools are quite different and have different areas of focus. APT is a package manager which (along with its other functions) has the ability to remove packages which are no longer required by the system. This is pretty much the only "clean-up" APT does, apart from cleaning out its own package cache, deleting downloaded archive files from the system after they have been installed.
APT is primarily used to install, update, and remove software. It also happens to have a few housekeeping capabilities that can be used to remove unnecessary package files.
BleachBit is a utility for tidying up a variety of temporary files and caches from around the operating system, not just packages. The BleachBit documentation summarizes its capabilities as follows:
BleachBit helps you quickly and safely clean your computer by removing unnecessary files such as:
- Cache - Temporary files that accumulate over time
- Cookies - Web tracking data stored by browsers
- Logs - System and application log files
- Recent file lists - History of recently accessed documents
- Temporary files - Leftover files from installations and updates
The website also mentions BleachBit can shred files, making them harder to recover if someone gets their hands on your hard drive.
Basically, APT manages packages, including removing old package files. BleachBit handles housecleaning of files all across the system - including history, logs, cache, and temporary files. The two tools do not have a lot of overlap.
BleachBit is also cross-platform. While APT is used (almost) exclusively by members of the Debian family of Linux distributions, BleachBit runs across most Linux distributions, Windows, and (experimentally) on macOS.
Finally, I'd like to point out that APT, on its own, is a command line tool. There are desktop front-ends for APT, such as Synaptic, however, when used on its own, APT is a command line program. BleachBit has the option of running from the command line or as a desktop program with people typically running it as a desktop application.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Unraid OS 7.3.0
Lime Technology, Inc. has announced the release of Unraid OS 7.3.0, the latest version of the company's Linux-based commercial operating system designed for Network-Attached Storage (NAS) deployments. The new version brings critical security updates and a redesigned onboarding wizard for new installations: "New users getting started with 7.3.0 will be greeted by a completely redesigned onboarding wizard that gets your server configured and ready in about three minutes. It walks you through server name, time zone, language, SSH access, theme, boot method selection, and plugin installation in a clean step-by-step interface, with a summary screen to review everything before it's applied. The boot method choice (USB/Flash Drive or Internal Boot) is built directly into the flow, so new users encounter it from day one rather than discovering it later buried in settings. Existing users switching to Internal Boot can access the same wizard under Tools, Onboarding Wizard. This release includes several security fixes. Upgrade is recommended. The 7.3 kernel patches two local privilege escalation vulnerabilities: Copy Fail (CVE-2026-31431) and Dirty Frag (CVE-2025-43284), the latter previously addressed in 7.2.6. Users upgrading from 7.2.5 or earlier get both fixes in one update." See the full release announcement for more information and screenshots.
Archcraft 2026.05.12
Aditya Shakya has announced the release Archcraft 2026.05.12, an updated build of the project's lightweight, rolling-release distribution based on Arch Linux and featuring the Openbox and bspwm window managers. From the release announcement: "May 2026 ISO image of Archcraft is now available to download. Changelog: updated ISO profile to archiso 88-1; latest base with new packages; update some Archcraft and all AUR packages; small improvements and bugs fixed." Besides a freely-available ISO image, the project now also offers a Prime edition with a selection of lightweight window managers and Wayland compositors: "New Archcraft Prime ISO image is now available to download. Archcraft Prime offers every (not the one released after Prime) exclusive stuff of Archcraft in a single ISO image. It has Openbox Premium, bspwm Premium and i3wm Premium, as well as all several exclusive Wayland compositors (Sway, Wayfire, River, Hyprland and newm) pre-installed."
RakuOS 2026.05.16
RakuOS is an immutable Linux distribution based on Fedora, with a choice of KDE Plasma, GNOME and COSMIC desktops. The project's latest release is based on Fedora 44 and introduces some key changes. "The old behavior (RakuOS Linux 43): On every image update, your overlay was wiped. The system blocked at a black screen or Plymouth while all your packages were reinstalled from scratch. No network? No usable system. This was especially painful for laptop users on spotty Wi-Fi. The new behavior (RakuOS Linux 44): Your overlay is kept intact across image updates your apps stay installed and usable immediately after reboot. Package database rebuilding now happens silently in the background after you log in Desktop notifications keep you informed of rebuild progress. No network on boot? The system handles it gracefully, defers the rebuild to your next boot with a notification explaining what happened, and retries automatically for functions that require network." Addiitonal information is provided in the project's release announcement.
RakuOS 44 -- Running the COSMIC desktop
(full image size: 1.8MB, resolution: 2560x1600 pixels)
Rescuezilla 2.6.2
Shasheen Ediriweera has announced the release of Rescuezilla 2.6.2, the latest version of the project's Ubuntu-based specialist distribution with tools for system recovery. This version is based on Ubuntu 26.04. From the changelog: "Adds release based on Ubuntu 26.04 LTS 'Resolute' for best support of new hardware; the prior release Rescuezilla 2.6.1 (2025-07-16) left the default release using Ubuntu 24.10 'Oracular' which only provided hardware support to circa October 2024, despite it introducing a release based on Ubuntu 25.04 'Plucky'; adds release based on the end-of-life Ubuntu 25.10 'Questing' as a backfill; fixed blank error message window displayed after cloning (even on success), which causes the cancellation of the post-operation shutdown/restart request; fixed graphical shutdown menu not opening on the 'Plucky variant due to missing item in custom rules file for Polkit authentication manager; upgraded to latest Partclone 0.3.47; temporarily disables the 32-bit (Intel i386) build based on Ubuntu 18.04 'Bionic'; temporarily disables older 64-bit build based on Ubuntu 22.04 'Jammy', Ubuntu 24.04 'Noble' and Ubuntu 25.04 'Plucky'. Notably NOT included in this release - an arm64 build, or planned major overhaul to Image Explorer using indexed-gzip and improved UI. That's coming next release."
* * * * *
Development, unannounced and minor bug-fix releases
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
How do you clean your system?
In this week's Questions and Answers section we talked about BleachBit and how it can scrub temporary files, remove unused cache, and delete other unnecessary files from the system. Having a clean-up tool like BleachBit helps save disk space and removes files which could leak information about the user. What tools, if any, do you use to keep your filesystem tidy? Let us know your favourites in the comments.
You can see the results of our previous poll on the number of fonts on a system in our previous edition. All previous poll results can be found in our poll archives.
|
How do you clean your system?
| BleachBit: | 328 (22%) |
| Manually run commands: | 411 (28%) |
| Script or scripts: | 61 (4%) |
| System package manager: | 204 (14%) |
| Another automated tool: | 19 (1%) |
| Another CLI tool: | 13 (1%) |
| Another GUI tool: | 48 (3%) |
| I do not do system cleaning: | 392 (27%) |
|
|
| Website News |
The Slow Death of the Power User
In recent weeks I've been meaning to write an article about a topic which has been weighing on my mind. I have been wanting to talk about the slow, continuous eroding of computing freedoms, the increased reliance by our society on companies and services which have interests contrary to their users, and the every-increasing surveillance of those users. Mostly though I've been wanting to share my dismay for how many users, even those in the open source community, not only tolerate having their freedoms and options curtailed, but how they vocally advocate for their freedoms and power to be taken from them.
These thoughts were simmering in the back of my brain in recent weeks while I figured out how to best organize my thoughts, my observations, and my frustrations at the apparent decay (perhaps self-imprisonment) of the tech community. Then I discovered a writer going by fireborn had already written such an article. More significantly, the author had presented the same ideas I wanted to share with more context, greater depth, and better skill than I would have done.
The article, The Slow Death of the Power User, discusses how the technology community used to function, why it was effective, why that has changed, and how it is hurting both technology enthusiasts and the entire computing industry.
In all honesty, I'd like to quote the whole article, it is well worth a read. However, in the interest of brevity, I will share just one paragraph:
The users who grew up on these [iOS and Android] platforms don't know what they're missing. They've never used a system where they were genuinely in control. The idea that you should be able to run arbitrary code on hardware you paid for is foreign to them - not rejected, but simply absent as a concept. They'll defend the restrictions without prompting because they've internalized the vendor's framing so thoroughly that they experience the cage as comfortable. "I don't want to root my phone, that sounds scary." Cool. You've successfully trained yourself to be afraid of ownership. The platform vendors are proud of you.
The entire article is a series of value insights and gems of both observation concerning the fading of the technology community, why it is happening, and the damage it is doing to the software industry as well as the open source community. It is a valuable read. I hope you enjoy it as much as I did and that it inspires people to take an interest in, and control of, their computing experience.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 25 May 2026. 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: 0, value: US$0.00) |
|
|
|
 bc1qxes3k2wq3uqzr074tkwwjmwfe63z70gwzfu4lx  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
|
