 DistroWatch Weekly |
| DistroWatch Weekly, Issue 1046, 20 November 2023 |
|
Welcome to this year's 47th issue of DistroWatch Weekly!
Every year computers become faster, more capable, and more powerful. Tasks which once took days of processing power can now be achieved in minutes. This is wonderful, most of the time, but there are times when we'd like our computers to slow down. There are any number of reasons for this, from wanting to consume less battery power to leaving some CPU resources available to other tasks. In this week's Questions and Answers column we talk about limiting the amount of CPU resources consumed by a process running on Linux. First though we talk about Slackel, a Slackware-based distribution which is partnered with the lightweight Openbox window manager. Read on to hear first impressions of this live distribution. Slackel's default interface, Openbox, is one of several lightweight window managers; there are several available for Linux. In this week's Opinion Poll we'd like to hear whether our readers run full featured desktop environments or minimal window managers. Let us know about your preference in the comments. Also in this issue we talk about Haiku developers adding new improvements and bug fixes to their desktop operating system while Canonical unveils MicroCloud for automated cloud solutions. Plus we are pleased to share the releases of the past week and list the torrents we are seeding. 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) |
Slackel 7.7 "Openbox"
Slackel is a live Linux distribution based on Slackware Linux and Salix. It is binary compatible with both, allowing it to use packages from these other projects. The Slackel distribution has been made available in a number of different editions with various desktop environments over the years. The project's latest release, Slackel 7.7, ships with the Openbox window manager and is available in 64-bit and 32-bit builds for x86 machines.
Special instructions
Slackel can be written to and run from a USB thumb drive as a normal, live distribution. We can also use a special set of instructions and a script (which is included in the distribution's ISO file) to install Slackel to a thumb drive. This allows us to run Slackel from a thumb drive almost as though it were installed on a hard drive with the option of enabling a persistent storage location. The instructions for doing this are provided on the project's website and included in the ISO.
The special instructions for setting up Slackel on a thumb drive basically involve mounting the ISO file and running a script called install_on_usb.sh which requires two bits of information: the location of the ISO file and the name of the thumb drive where we wish to install Slackel. The command looks like this:
sudo sh install_on_usb.sh --usb path_to_iso_image device
I followed the instructions provided and running the above command resulted in an error message which read: 'install_on_usb.sh: 82: Syntax error: "(" unexpected'. After checking the contents of the script I discovered the problem. The install_on_usb.sh file is a Bash script, it specifically requires Bash features in order to run properly. However, the command we're told to use to run the script says to use sh, not bash. The sh command invokes different shells on different distributions. On some distributions the sh command is its own shell, on some distributions it is a link to bash and on others it is a link to dash. In other words, using sh is unpredictable if you're working across multiple platforms. In my case sh was a link to dash when I needed to be using bash to run the script. Rewriting the command as follows worked:
sudo bash install_on_usb.sh --usb path_to_iso_image device
The script asks if we wish to proceed, performs some basic checks to confirm the drive we are planning to use is a thumb drive and not our main hard drive, and we're asked if we wish to make use of persistent storage. We can then choose to set up storage with the ext3 or FAT filesystems. The ext3 option feels a bit dated, but seemed the reasonable choice in my situation. We're then asked how big the persistent storage space should be with a list of numbers displayed, indicating potential sizes in megabytes. We're also given the chance to encrypt the persistent storage, though I skipped this step.
Slackel 7.7 -- The instructions for setting up persistent storage
(full image size: 1.3MB, resolution: 1920x1080 pixels)
Early impressions
Booting from the thumb drive I had just imaged brought up a text menu where I was asked to select my language from a list. Once I had selected English the distribution booted and, fairly soon afterward, presented me with an Openbox-powered desktop. A panel sat across the bottom of the screen, a few icons sat on the desktop, and there was a Conky status panel in the upper-right corner of the screen.
The Openbox environment uses a light theme and most elements are grey. The application menu is arranged in a classic tree style without any search feature. The icons in the system tray all seem to have a faded, grey look which makes them blur together a bit. One thing I found unusual was the Conky status widget had its own entry in the task switcher on the panel, in other words it is treated similarly to other open application windows.
Something I noticed fairly quickly was Slackel uses fonts that are quite small (9pt) and thin. On a laptop screen at full resolution this makes text harder to read compared to most other distributions I've used this year. I figured it would be a simple matter to adjust the fonts, though I was gradually proved wrong on this point.
Slackel ships with at least three graphical tools which will offer to adjust font settings. There is an appearance module which will offer to adjust fonts for us, though this just works for adjusting font styles rather than size. There is an Openbox settings and customization application which will adjust the fonts of menus and title bars, but not the rest of the desktop. There is also a desktop settings module which will change the size of the text which appears under desktop icons, but no other areas of the interface. As far as I can tell there are no tools which will adjust the fonts for applications and the application menu. There also didn't appear to be any zoom or scaling feature included. Some applications, including Firefox and the virtual terminal, will zoom and adjust font sizes independently of the Openbox environment.
Slackel 7.7 -- Three tools for adjusting fonts
(full image size: 1.3MB, resolution: 1920x1080 pixels)
At any rate, what had started as a low priority exploration into adjusting a minor feature of the desktop experience turned into about ten minutes of searching and experimenting with some minor success and a lot of frustration. Nevertheless, I decided to reboot the laptop and see if my changes did indeed remain persistent across reboots. They did not.
Persistent storage
The Slackel documentation talks about a persistent area of the filesystem, though it doesn't go into details on where it is. There are also some comments about making our home directory persistent, but the English in the documentation is a bit broken and I'm not clear on whether home directory persistence is a default or under which circumstances it is enabled. I was able to work out through the on-ISO documentation that we should be able to enable persistence at boot time, but it needs to be manually selected.
I restarted my laptop again and this time paid more attention to the boot menu. Along with the language selection section there has a text box for typing kernel parameters. There are also hints saying we can press F1 and F2 to get general information and boot parameter tips, respectively. There are a few tips listed, including one for adjusting power settings and one for enabling persistence.
Here I ran into another problem. The informative parts of the boot menu indicate we can use the arrow keys (Up and Down) to select which language we want to use and we can press Enter to boot Slackel, and we are told we can type boot parameters into the text box, but there isn't any indication of how to select the text box. I've been using computers for close to 40 years and Linux for about 25 years, so I thought this part would be the easiest aspect of my experience with the distribution. I'd just tap Tab, or Shift+Tab, or Page Down, or either the Left or Right arrow key, or use the mouse to select the text box. None of these worked and I couldn't find any tip in the documentation for how to select the text box, only that typing options into the box was expected. I knew my keyboard was working since I could select the information screens and pick my desired language, but no key combination I tried switched between screen elements. This ultimately meant I couldn't make use of persistent storage on my laptop.
I later discovered that when booting Slackel in a VirtualBox instance the boot menu screen was divided into two parts. The first screen asks us to select our language and a second screen shows a menu which asks us to pick kernel parameters. Some experimenting in VirtualBox revealed that the distribution shows the unified (every choice on one screen) boot menu when booting in UEFI mode, but shows the two-phase approach in Legacy BIOS mode. This made it easy to select boot options without switching between on-screen widgets.
I also found that in VirtualBox I was able to simply start typing on the unified screen and text would appear in the boot parameters box. This does not happen when booting the distribution on my laptop. The function keys, arrow keys, and Enter work as expected, but the text box doesn't have focus and doesn't accept typed letters on my laptop, only in VirtualBox.
In short, Slackel provided different experiences and capabilities depending on whether I was booting in UEFI mode or BIOS mode, and depending on whether I was booting in a virtual machine or on physical hardware.
Hardware
While I'm discussing different experiences in different test settings, I feel it important to mention that while the distribution would boot and run on my laptop (though without allowing me to type boot parameters), Slackel was unable to boot in VirtualBox. Whether I was in UEFI mode or BIOS mode, the distribution would start background services and then lock up while trying to launch a graphical environment. The error 'INIT: Id "x1" respawining too fast: disabled for 5 minutes' was displayed on the console. If I waited for five minutes the same error would be repeated again and then again while the system remained unresponsive.
When the distribution booted on my laptop I found the base system and the Openbox window manager would consume 540MB of RAM. This is unusually heavy for a minimal window manager, about on par with Xfce or KDE Plasma. It's quite a bit more memory than other instances of Openbox or small window managers I've run lately. The installation on my thumb drive took up about 2.6GB of space.
Most of my laptop's hardware was detected and used properly. Wireless networking functioned out of the box, my touchpad worked smoothly and interpreted taps as clicks. Slackel was unable to produce sound on my laptop and some exploring revealed the distribution was unable to detect my sound card, something other Slackware-based distributions have handled without issue.
Slackel 7.7 -- Unable to play audio
(full image size: 2.5MB, resolution: 1920x1080 pixels)
Included software
Slackel's live environment provides a nice collection of open source software. Browsing through the application menu we can find popular items such as Firefox, Thunderbird, LibreOffice, and the GNU Image Manipulation Program. The FileZilla file transfer application is included along with SMPlayer, Transmission, and Pidgin. The mtPaint drawing program is included along with a series of utilities for customizing the user interface.
Slackel 7.7 -- Exploring the application menu
(full image size: 2.9MB, resolution: 1920x1080 pixels)
Slackel provides us with the GNU command line utilities, manual pages, and the GNU Compiler Collection. The distribution runs the SysV init software and version 6.1 of the Linux kernel.
By default, the distribution signs us into an account with the username "one" and the password "one". Administrative tasks can be performed through the sudo utility and using the "one" password.
Package management
Slackel uses the slapt-get command line package manager (there doesn't appear to be a graphical package manager). I experimented with slapt-get and it worked quite well. I was able to refresh the package database, search for new packages, and fetch new applications. The slapt-get utility pulls in software from Slackware's repositories and worked smoothly with no problems.
I was happy with slapt-get, especially after recent experiments with other members of the Slackware family where the package manager tended to run into problems or require manual configuration. Slackel handles package management quite well with slapt-get working quickly.
The distribution also ships with the Flatpak framework and enables the Flathub software repository by default. This gives us access to a large selection of up to date desktop applications, something which is usually not a focus of Slackware-based projects. Flatpak bundles can be managed from the command line.
Conclusions
There are some things the Slackel project handles quite well and which made the distribution fun to explore. The Openbox environment has a nice, classic layout; the distribution ships with a lot of useful desktop applications; and I like that Flatpak is set up for us in case we want to use it. I also appreciated how up front the project was with its documentation and access to scripts which make it easier to transfer the distribution to a thumb drive and enable persistence.
On the other hand, I regularly ran into problems (most of them small, a few of them significant) which hint at the project not getting enough testing or not being used by a wide enough audience. Having three completely different boot experiences whether I was using VirtualBox or my laptop, and whether I was using UEFI or Legacy BIOS modes, was a key example. The script for transferring the distribution to a thumb drive failing because the author assumes sh links to bash is another as this isn't true on the majority of the world's Linux installations.
Having my sound card not detected by Slackel while it works on virtually every other Linux distribution was disappointing. A smaller issue was finding three separate utilities which could be used to adjust fonts on the system, but none of them affected the font used by the application menu or desktop applications. Playing audio and changing font sizes/styles feel like pretty standard features of desktop distributions these days.
In short, Slackel does a few things really well, but it also tripped over simple tasks a lot during my trial. I felt like the overall design was good, the style of the project felt as though it could be quite useful, especially for people who want to take their operating system with them in a portable fashion. However, there were several areas which lacked polish, didn't work for me, or which could benefit from broader testing (across more environments and equipment).
* * * * *
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
Slackel has a visitor supplied average rating of: 8.7/10 from 3 review(s).
Have you used Slackel? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
Haiku improves font handling and performance, Canonical launches MicroCloud
The Haiku team have been hard at work, introducing new features and bug fixes into their lightweight operating system. The project's monthly newsletter highlights some of the changes, locale bug fixes, and driver improvements. "jscipione fixed Deskbar submenus to all use the 'menu' font. Previously, some of them used the 'plain' font and some the 'menu' font, which made things obviously inconsistent when two different fonts were in use for these; now things should be properly consistent.
apl fixed some minor issues and improved the performance of HaikuDepot a bit, and also fixed a corner-case regarding invalid characters being entered into the username field. He also added more logging to allow for easier debugging of performance issues.
waddlesplash fixed colour name handling in Terminal, which was incorrect for non-English locales and broke adjusting colours entirely. Now things should work properly."
* * * * *
Canonical has announced a new technology for people interested in deploying their own cloud infrastructure. The new software, called MicroCloud, is intended to be set up with a single command, reducing the amount of human interaction involved in setting up new cloud instances. Support for MicroCloud is included in Ubuntu Pro subscriptions. "Canonical announced today the general availability of MicroCloud, a low-touch, open source cloud solution. MicroCloud is part of Canonical's growing cloud infrastructure portfolio. It is purpose-built for scalable clusters and edge deployments for all types of enterprises. It is designed with simplicity, security and automation in mind, minimising the time and effort to both deploy and maintain it. Conveniently, enterprise support for MicroCloud is offered as part of Canonical's Ubuntu Pro subscription, with several support tiers available, and priced per node." Additional information is provided in the company's announcement.
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
Restricting CPU usage
Pick-a-core-any-core asks: Is there a command I can use to determine how many CPU cores a process uses? When I compile or convert something, I want to be able to limit its CPU usage.
DistroWatch answers: There are a few different ways you can limit the amount of CPU resources a process can use at a time. Which approach makes the most sense will vary depending on the situation. Below, I'll cover three options for restricting a process's CPU access.
When what you are doing is specifically related to compiling, you can usually set the maximum number of jobs/cores to use at a time through your build tools. For instance, if you're compiling any software which uses the GNU make build tool then you can specify the number of jobs to run at a time using the "-j" flag. For example, the following would limit your build process to executing one job at a time, presumably requiring just one core:
make -j1
The compile job that is running may move between different cores as the Linux scheduler sees fit, but only one would be in use at a time. To run up to two jobs (using two cores) at a time, you could run the following:
make -j2
* * * * *
In situations where you want to lock one process to using a specific CPU core (and just that core) you can use a command called taskset. Let's say I want to run the make command again and only allow it to run on one of my eight CPU cores. I can force make to run on CPU #3 by running the following:
taskset -c 3 make
in this instance the make command might use up all of its single core, but it won't spread to others.
* * * * *
A third option is: we might not care on which or how many CPU cores are being used, just the total amount of CPU resources a process consumes. For these situations we can use a program called cpulimit which will throttle back running jobs to only consume a certain percentage of our available CPU resources. For instance, we can run Firefox and limit it to only using up to 50% of our CPU time by running the following command:
cpulimit -l 50 -- firefox
Using this approach, the launched program can run on any cores, it just can't use more than half (50%) of our processing power. This can be useful when running long jobs which we may want to run more slowly in the background.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
AlmaLinux OS 9.3
AlmaLinux OS is a Linux distribution built using the source code of Red Hat Enterprise Linux. The project has published version 9.3 which introduces security improvements and updates to the web-based administration tools. "AlmaLinux 9.3 aims to improve flexibility and reliability, as well as to enhance security across hybrid environments. This release continues simplifying automation and system management. Web console enhancements simplify management tasks. Additionally, users can configure health check actions for Podman containers and vsock devices in virtual machines. Application Streams updates provide developers with flexibility and customization options without affecting the platform's stability. The 9.3 offers enhanced security and compliance. Additionally, it provides enhanced flexibility, stability, and reliability needed to support hybrid cloud innovation. You can read more about this release by checking out the Release Notes." Additional details on the new version can be found in the project's release announcement.
Red Hat Enterprise Linux 9.3
Red Hat has announced the release of a new update to its 9.x Red Hat Enterprise Linux (RHEL) product line. The new version, RHEL 9.3, introduces a few changes, including supporting UEFI environments in cloud instances. "Previously, RHEL image builder created EC2 AMD or Intel 64-bit architecture AMIs images with support only for the legacy boot type. As a consequence, it was not possible to take advantage of certain AWS features requiring UEFI boot, such as secure boot. This enhancement extends the AWS EC2 AMD or Intel 64-bit architecture AMI image to support UEFI boot, in addition to the legacy BIOS boot. As a result, it is now possible to take advantage of AWS features which require booting the image with UEFI." The new release also makes it easier to select a specific kernel when installing on ARM processors. Additional information is provided in the company's release notes.
EuroLinux 9.3
The EuroLinux project publishes and supports an enterprise-focused distribution based on source code from Red Hat Enterprise Linux. The EuroLinux team have published version 9.3 of their distribution which introduces a number of updates to server software as well as new utilities. "Major changes in EuroLinux 9.3. Security - key security-related highlights: Keylime was rebased to version 7.3.0. OpenSSH was further migrated from the less secure SHA-1 message digest. The pcsc-lite-ccid USB Chip/Smart Card Interface Device(CCID)) and Integrated Circuit Card Device (ICCD) driver was rebased to version 1.5.2. SEtools, the collection of graphical tools, command-line tools, and libraries for SELinux policy analysis, was rebased to version 4.4.3. OpenSCAP was rebased to version 1.3.8. Programming languages, web and database servers - later versions of the following application are now available: Redis 7; Node.js 20. Furthermore, the Apache HTTP Server has been updated to version 2.4.57." The project's relesae announcement and release notes offer additional information.
pfSense 2.7.1
Bill Rathbone has announced the release of pfSense 2.7.1, un updated build of the project's FreeBSD-based specialist operating system for firewalls and routers. This version uses the FreeBSD's 14-CURRENT branch as its base. "Netgate is pleased to announce the release of pfSense Community Edition (CE) software version 2.7.1. Major changes and features: OpenSSL upgraded to 3.0.12 - this change was essential because OpenSSL 1.1.1 has reached end of life (EOL) and will no longer receive security patches for vulnerabilities; the Kea DHCP server is available as an opt-in feature, basic functionality is present in version 2.7.1, but it is not feature-complete; support for SCTP has been improved in PF for firewall rules, NAT and logging, and rules can now act on SCTP packets by port number; IPv6 Router Advertisement configuration has been relocated to Services, Router Advertisement as a part of the ongoing Kea DHCP server integration; PHP upgraded to 8.2.11; the base operating system upgraded to a more recent point of FreeBSD 14-CURRENT...." See the release announcement and the release notes for further information and upgrade instructions.
Oracle Linux 9.3
Simon Coter has announced the release of Oracle Linux 9 Update 3, an updated build of Oracle's distribution built from the just-released Red Hat Enterprise Linux (RHEL) 9.3: "Oracle Linux 9 Update 3 for the 64-bit Intel and AMD (x86_64) and 64-bit Arm (aarch64) platforms is now generally available. This release continues to be application binary compatible with the corresponding Red Hat Enterprise Linux 9 Update 3 release, as has been the case since the first release in 2006. Oracle Linux 9 Update 3 ships with the newest Unbreakable Enterprise Kernel Release 7 Update 2 (UEK R7U2) and Red Hat Compatible Kernel (RHCK) packages. Oracle Linux now supports automatic reboot of systems after patches are installed through DNF. With enhanced DNF, automatic reboot with different options (never, when-changed, when-needed) can speed-up patch management operations. The enhanced DNF utility introduced two new options: dnf leaves - to list the installed packages that aren't required by any other installed packages; dnf show-leaves - to list newly installed leaf packages and packages that have become leaves after a transaction." See the release announcement and the release notes for further details.
* * * * *
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: 2,928
- Total data uploaded: 43.8TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
Window manager or full desktop environment?
In this week's review of Slackel we touched on the Openbox window manager. Some distributions ship with a minimal window manager with just a handful of features. This makes them lighter and often faster than distributions which offer full featured desktop environments such as GNOME and KDE Plasma. This week we'd like to hear how many of our readers have gone the minimal route and run plain window managers rather than full desktop environments.
You can see the results of our previous poll on using open source applications exclusively in last week's edition. All previous poll results can be found in our poll archives.
|
Window manager vs full desktop environment
| I run a window manager: | 372 (21%) |
| I run a full desktop environment: | 1423 (79%) |
|
|
| Website News |
New distributions added to waiting list
- AZOS GNU/Linux. AZOS GNU/Linux is an Arch-based distribution which strives to provide all necessary desktop functionality without relying on a command line. The project aims to be suitable for both office work and gaming, as well as other common desktop activities.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 27 November 2023. 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 |
|
| Extended Lifecycle Support by TuxCare |
|
|
|
| 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 | 
Foresight Linux
Foresight Linux was a desktop operating system, based on rPath Linux, featuring an intuitive user interface and showcasing the latest desktop software. As a Linux distribution, Foresight sets itself apart by eliminating the need for the user to be familiar with Linux, combining a user-focused desktop environment on top of the Conary package management system. As the most technically innovative software management system available today, Conary ensures that users can efficiently search, install, and manage all the software on the Foresight system, including bringing in the latest features and fixes without waiting for a major release.
Status: Discontinued
|
| TUXEDO |
TUXEDO Computers - Linux Hardware in a tailor made suite
Choose from a wide range of laptops and PCs in various sizes and shapes at TUXEDOComputers.com. Every machine comes pre-installed and ready-to-run with Linux. Full 24 months of warranty and lifetime support included!
Learn more about our full service package and all benefits from buying at TUXEDO.
|
| Star Labs |
Star Labs - Laptops built for Linux.
View our range including the highly anticipated StarFighter. Available with coreboot open-source firmware and a choice of Ubuntu, elementary, Manjaro and more. Visit Star Labs for information, to buy and get support.
|
|
• 
• 
• 
• 
• 
• 
• 
