 DistroWatch Weekly |
| DistroWatch Weekly, Issue 962, 4 April 2022 |
|
Welcome to this year's 14th issue of DistroWatch Weekly!
How many Linux users are there? Which distributions do they run? Are these Linux systems powering desktops, servers, phones, or the Internet of Things (IoT)? These are some questions which are difficult to answer because of the decentralized nature of the Linux community. In this week's Questions and Answers column we discuss some of the reasons it is difficult to get solid information to answer these queries and why that is a good thing. We also discuss directory permissions for the user's home and configuration files. How tightly locked down is your home directory? Let us know in this week's Opinion Poll. This week we also share an opinion piece on why AlmaLinux OS might be the preferred choice for people migrating away from CentOS Linux and share news of new sandboxing tools coming to FreeBSD. We also report on the Debian Project Leader election of 2022. First through we talk about two Linux distributions in our Feature Story. The first is MassOS, an independent distribution with a focus on sleek technical design and performance. The latter is Neptune, a tried and true Debian-based desktop distribution. Read on to learn more about these two projects and let us know which one you think is more appealing in the comments section. 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!
Content:
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (21MB) and MP3 (15MB) formats.
|
| Feature Story (by Jesse Smith and Ivan Sanders) |
MassOS 2022.03
A little while ago I got to briefly experiment with a project new to the DistroWatch waiting list. While I only had a brief chance to experiment with it, the project made a big impression during my single day of trying it and so I'd like to talk about this unusual distribution: MassOS.
At first glance, the MassOS project doesn't seem to do anything particularly special. The distribution's website describes it as follows:
MassOS is a free (as in freedom) GNU/Linux operating system for laptops and desktops which is designed to be minimal and lightweight, without compromising on features.
MassOS uses a themed Xfce desktop environment. This allows it to be lightweight on system resources while still being visually appealing and easy to use.
MassOS is completely independent and not based on any existing GNU/Linux distribution. This means we are free from being tied down to distributions outside of our control.
There are three editions of MassOS. The regular/standard edition is a typical live image with a system installer. There is a second ISO which offers the same experience, except the firmware has been removed from the download. The third edition isn't an ISO, it's a filesystem archive which can be used to manually install the distribution. This could be useful if someone wanted to perform a completely manual setup or install MassOS into a chroot environment.
I downloaded the standard ISO which is 1.8GB in size. Booting from this media brings up the Xfce desktop fairly quickly. We are then shown a welcome window which gives a quick overview of where to find application launchers and how to use the GNOME Software utility to fetch additional programs.
MassOS 21.12 -- The application menu and settings panel
(full image size: 148kB, resolution: 1280x1024 pixels)
The Xfce desktop places a thin panel across the top of the display where we can find the application menu, task switcher, and the system tray. There is a compact dock at the bottom which provides quick access to tools such as the file manager, web browser, and software centre. On the desktop we find icons for opening the file manager and launching the system installer.
Installing
MassOS uses a text installer which gets launched in a terminal window. The installer looks quite similar to the one used by Slackware and Zenwalk, guiding the user through a series of menus. We're given the chance to take over the entire local disk or a single partition. We're asked to select a filesystem for ourselves and then walked through choosing our locale, keyboard layout, and location. We're asked to make up a password for the root account and credentials for a regular user account. The MassOS installer then asks if we want to enable Bluetooth support and whether it should check for other operating systems before installing the GRUB boot loader. The installer then wraps up and reboots the computer.
Early impressions
The distribution boots to a graphical login screen where we can sign into the Xfce desktop. The first time we login the desktop displays the welcome window.
The desktop is highly responsive, I'd even say unusually snappy for most modern distributions, even those running the relatively light Xfce environment. The system defaults to a dark theme which offered high contrast text and a consistent look.
The application menu has a small, yet useful, collection of software. The Firefox web browser is installed along with a document viewer, some desktop configuration tools, file manager, terminal, and GNOME Software. The Parole media player is included and plays both audio and video files out of the box.
Early on I noticed the volume control is muted by default. We can enable audio by clicking the volume icon in the system tray.
MassOS ships with a full set of GNU command line utilities, manual pages, and development tools such as GNU Make and the GNU Compiler Collection). The CUPS printing software is included and can be configured through the CUPS web portal. The distribution runs the systemd software and the version I was running shipped with version 5.16.12 of the Linux kernel.
Resource usage
The above utilities and desktop do not take up much in terms of resources. When signed into the Xfce desktop the system consumed about 380MB of RAM and a fresh install used up about 7GB of disk space. This is relatively light by modern standards.
I tried out MassOS in a VirtualBox machine and on my workstation. In both environments the distribution ran quickly, was stable, and detected all my hardware.
Software management
Apart from the base utilities and desktop environment, MassOS is fairly minimal which means most people will want to install additional software. The project's documentation suggests MassOS does not have its own repositories or package manager. Instead the project provides access to Flatpak bundles (through the GNOME Software utility) and recommends using AppImages from AppImageHub. This heavy reliance on portable packages is unusual, but it will work for many people who wish to primary install desktop software (rather than command line tools).
MassOS 21.12 -- The GNOME Software centre
(full image size: 186kB, resolution: 1280x1024 pixels)
I tried out GNOME Software and confirmed the distribution does automatically connect us with the Flathub repository. Using the software centre we can fetch popular third-party applications such as LibreOffice, GIMP, Falkon, Thunderbird, and other desktop applications. This worked fairly well and, despite the large size of the installed bundles, I had no complaints. Well, with one exception: the Rhythmbox media player kept crashing and locking up when I tried to add new music. Switching to another media player worked around this issue.
The update system MassOS uses is unusual and one of the few aspects of the operating system which struck me as being inconvenient. To check for updates we first need to download a script. We then set execute permissions on the account and run the script. The process looks like this:
curl -Os https://raw.githubusercontent.com/MassOS-Linux/massos-upgrade/main/massos-upgrade
chmod 755 massos-upgrade
sudo ./massos-upgrade
The shell script checks for new versions of MassOS and, if it finds one, will offer to install it. During my trial there were no updates available. This concerns me a little as it appears the operating system is upgraded as a whole and only when new versions are published. Which means, in the meantime, any individual components which might have security flaws are not being updated. I could be mistaken about this, but I did not find any indication on the project's website which would suggest a way for us to get minor, weekly updates for security fixes, short of downloading the source code for such updates and compiling it ourselves.
MassOS 21.12 -- Checking for software upgrades
(full image size: 132kB, resolution: 1280x1024 pixels)
Conclusions
For being such a young project, MassOS impressed me in a number of ways. The developer really understands the benefit of documentation. The steps for downloading, installing, and updating the system are all documented in detail, often with screenshots. The documentation is well organized and pleasantly to the point. In other words, we're told how to do things and spared the developer's philosophical views and marketing pitch.
MassOS is super fast, I'm not sure I've ever encountered a distribution running Xfce which performed this well. The distribution has managed to disable or avoid installing almost everything it doesn't need while including the basics most people will want. For me, at least, I was able to accomplish most tasks with the software included and a couple of Flatpaks. I suspect, were I to use MassOS longer, I'd eventually run into trouble when it came time to install more obscure development tools and command line items, but I could probably work around that by using a third-party package manager such as Nix.
Finally, I really like the dark, fairly minimal interface. I like Xfce as it walks a nice line between capable and customizable. I like its balance of performance and features. I like that MassOS includes a dark theme which seems consistent across the included utilities. The desktop felt almost immediately comfortable for me - a few conveniences were presented and then it got out of my way.
There are just two drawbacks I see to MassOS after a day of use. One is that it has a text installer. Which, for me, isn't really a problem, but it gives the distribution a legacy vibe that could scare off some people. Shifting to another installer, such as Calamares, would probably attract more users.
The second drawback is the lack of a built-in package manager. We may not need one for acquiring desktop software, but it would be nice to have a way to install small security updates. Getting the user to download and execute a script isn't an ideal way to provide new versions of software. At the minimum, I think the shell script for performing updates should be included by default.
However, this lack of package manager aside, MassOS is surprisingly mature for a young project. It's fast, it seemed to be stable, it worked well with my hardware, and it's practically documented. I really hope the developer keeps working on this as, with a few small changes, I'd feel very much at home with this distribution.
* * * * *
Hardware used in this review
My physical test equipment for this review was a Lenovo desktop with the following specifications:
- Processor: Hex-core Intel i5-10400 CPU @ 2.90GHz
- Storage: Western Digital 1TB hard drive
- Memory: 8GB of RAM
- Networking: Realtek RTL8111/8168/8411 wired network card, Realtek RTL8822CE 802.11ac PCIe wireless adapter
- Display: Intel CometLake-S GT2
* * * * *
Neptune 7.0
Neptune 7 "Faye" was released in December 2021. I've been using Neptune as my daily driver for approximately six weeks - this points to the stability of the operating system. Neptune OS is a GNU/Linux distribution which is, "based fully upon Debian Stable ('Bullseye'). It ships with a modern KDE Plasma desktop with its main view on [being] a good looking multimedia system which allows for getting work done." Essentially, if you're looking for a rock solid distribution based on Debian but including the non-free drivers, more up-to-date KDE Plasma desktop, and out of the box functionality, Neptune is for you.
Installation
Installation was clean and mostly painless. The partition screen would not allow me to continue when I selected, "replace a partition," but did allow me to continue when selecting manual partitioning. This should have been a flag to me that the initial install experience was not working as intended.
Neptune 7.0 -- Partitioning the hard drive
(full image size: 1,013kB, resolution: 1920x1080 pixels)
During the first attempt at installation, Neptune never asked me for a LUKS password for the partition and the system crashed during install. This could be a one-off experience but, again, I should have stopped at this point and tried installing again.
During the second attempt at installation, automatic install was now an option, as opposed to before, and I was able to complete an install and erase the disk, as desired.
After installation I attempted to sort out my mount issues. The KDE partition manager would not allow me to auto mount my second drive (with LUKS encryption). I have had luck with the GNOME partition manager in the past (GNOME Disks, gnome-disk-utility) in getting my disks to auto-mount but I was unable to accomplish this with Neptune. In other operating systems it tells me I am going to create an unencrypted password file for the encryption of the disk (which is stored on a LUKS encrypted disk), but this dialog never appeared for me.
Neptune 7.0 -- Testing the NVIDIA driver
(full image size: 1.7MB, resolution: 1920x1080 pixels)
This turned into a nuisance for me because every time I restarted or powered on my computer I needed to mount, decrypt, and sudo the mounting of the drive which is inside my computer. I mostly use this drive for Steam games so this wasn't a deal breaker and it only took approximately 30 seconds after mounting. Still, unacceptable for a modern operating system. My root drive was LUKS encrypted and requested its password safely upon startup, as expected. Note: I will say I realize there are modern CLI ways to mount drives with their encryption password automatically, but I was going for a user friendly, GUI approach.
Post installation and daily operation
I loved using Neptune 7. Neptune is a great way to use an updated version of KDE Plasma on a stable Debian operating system. Everything worked out of the box after install. I did not need to download some alternative Debian "Non-Free" ISO to accomplish my goals. I was able to install the NVIDIA driver as advertised for a Debian OS. I was able to play games on Steam using my NVIDIA drivers (optiums) and I was able to browse the web with ease, like with any other modern Linux OS. Steaming videos using common streaming services worked flawlessly through browsers and HDMI support was seamless out of the box. The operating system came pre-loaded with a few extra KDE tools, but nothing out of the ordinary. Would I recommend Neptune? Yes. Despite the minimal issues I had, Neptune is great if you're looking for a stable Debian based distro with an up-to-date Plasma desktop environment that is easy to install and use as a daily driver.
Neptune 7.0 -- Locating drivers in the package manager
(full image size: 1.0MB, resolution: 1920x1080 pixels)
Out of the box with NVIDIA drivers, Neptune used 746MB of RAM upon startup.
* * * * *
Hardware used in this review
Laptop - Lenovo Legion Y530
- Processor: Intel Core i7-8750H CPU @ 2.20GHz x 6
- Storage: 256GB NVMe SSD Samsung and 1TB HDD
- Memory: 16GB
- Networking: Realtek RTL8111/8168/8411
- Display: 1920x1080 @ 60Hz
- Graphics: Intel Corporation UHD Graphics 630, NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile]
Visitor supplied rating
Neptune has a visitor supplied average rating of: 8.8/10 from 36 review(s).
Have you used Neptune? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
AlmaLinux OS as preferred CentOS Linux replacement, FreeBSD getting suite of new sandboxing tools, Debian opens voting for Project Leader
In 2020 it was announced Red Hat would be phasing out CentOS Linux in favour of CentOS Stream. This move caught a number of people by surprise and several community projects rushed in to fill the void. Practically overnight several distributions based on Red Hat Enterprise Linux's source code sprang to life. While each of these new clones strives to be binary compatible with Red Hat Enterprise Linux (RHEL), each one has its own special features, architecture support, documentation, and support options. Has one RHEL clone stood out from the others? FOSS Force has put forward an opinion piece on why AlmaLinux OS might be the long-term best option of the various replacements for CentOS Linux. "Not only does AlmaLinux seem to be in front in terms of financing, it's also ahead of the game in the technology department, where its developers have demonstrated the efficacy of their development technology twice already.
This started with the distro being the first out-of-the-gate with its first release, AlmaLinux 8.3, last March, nearly three months ahead of Rocky Linux's first release, even though they both began development at about the same time. In November, less than 48 hours after RHEL 8.5 was released, AlmaLinux developers released their own 8.5 version based on it, several days ahead of Rocky. The project has also developed and released open source software that potentially benefits anyone using RHEL or any of its clones."
* * * * *
One area where OpenBSD and Linux distribution have made a lot of progress in recent years is in sandboxing applications, closing off the running program from the rest of the operating system. This is often used internally by a program to reduce its own system access or by a sandboxing utility to isolate a running program which might misbehave. One developer is working to bring these types of program isolation to FreeBSD. "Since a while I've been working on and off on a pledge()/unveil() implementation for FreeBSD. I also wanted it to be able to sandbox arbitrary programs that might not expect it with no (or very minor) modifications. So I just kept adding to it until it could do that well enough. " The mailing list post goes on to show examples of the new isolating software at work with instances of command line programs and some desktop software being sandboxed.
* * * * *
The Debian project has a lot of distinguishing features. It's one of the world's older distributions, it has a huge family of child distributions, and it's a massive democratic project. Each year the Debian developers (who number around a thousand people) cast their votes for the position of Debian Project Leader. This year there are three candidates: Felix Lechner, Jonathan Carter, and Hideki Yamane. Information on these developers and their platforms can be found on the Debian website. A discussion of the candidates and their positions can be found in the project's vote mailing list.
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
Tracking Linux installs and adjusting directory permissions
Keeping-count asks: It seems that the best gauge on the popularity of distros is your site's count of times people click on links to them. It came to me that it might be possible to develop a much better way.
Incorporate into the Linux kernel code that would, upon installation, send a ping (or whatever) containing information on the version of distro (version, desktop, etc) to a database program on remote servers that would compile and tally the received pings.
Such could be more elaborate if desired - hardware information of the computer, software programs installed on the computer, maybe other information such as location - if possible.
This could be designed to be a one time data gathering, in which the code could become inactive after sending the data. Or, it could be possible to leave the code active and have it send the information (maybe yearly) to establish that the install is being used.
DistroWatch answers: While a lot of people are interested in finding out how many Linux users there are and which distributions they run, DistroWatch doesn't make any attempt to track this information. The page hit ranking (PHR) table shown on the front page simply indicates how many people per day look up information on a given distribution on DistroWatch. The numbers indicate an interest in some projects, but isn't a reflection of usage. Or, as the Page Hit Ranking section of DistroWatch says of the PHR table numbers:
They correlate neither to usage nor to quality and should not be used to measure the market share of distributions. They simply show the number of times a distribution page on DistroWatch was accessed each day, nothing more.
As for placing tracking code into the Linux kernel, what you're describing is called spyware. It's highly undesirable and, in some parts of the world, illegal. It's unlikely any such tracking code would make it into the kernel and, if it were to somehow get accepted, virtually no one would use any distribution which included the feature.
There are some distributions which provide people with the option of sending a ping or hardware information to the distribution's developers, but it's (as far as I know) always a voluntary step and not baked into the lower level operating system. Debian goes a step further and invites people to submit software package statistics, but again it's entirely an optional feature. One which most people turn off.
Trying to automate this process without making it trivial to opt-out would insure virtually no one would use the distribution(s) which included the feature, negating its attempt to count users and track their software and hardware statistics.
* * * * *
Locking-down-directories asks: Should I cut off permissions to the directories under .config? Some have "rwxr-xr-x" permissions, but others have "rwx------". Shouldn't they all have their permissions stripped to protect them from other users?
DistroWatch answers: The ~/.config directory is special in that it holds a lot of information which is used by local programs. This information is specific to your user and may include relatively mundane information like your screen resolution or desktop theme. It can also hold sensitive information such as which files you've downloaded recently, your bookmarks, and passwords.
I have two answers for this question. First, in theory, all files and directories should have their permissions reduced to the lowest possible point where they are still useful. Ideally, no file or directory will offer permissions unless they are needed.
Usually the default file permissions for a new file or directory are determined using your user's umask. The umask determines which permissions a new file does not have. Most distributions set the umask to 0022 which means new files do not remove any permissions for their owner, and remove write access (value 2) for everyone else. You can check what your umask is set to by running the following command:
$ umask
0022
You can change your umask by running the command and specifying which permissions new files should not have. For instance, running the following command removes all permissions from new files for everyone except the file's owner:
$ umask 077
The umask command can be run from your shell's start-up script (typically ~/.bashrc on most distributions) so you don't need to type it each time you login.
I mentioned I have two answers and what I wrote above handles what I think the right answer is in theory. In practise, directories are only accessible to people if a person also has access to the parent directory. In other words, people can only access and see the information in the directories under ~/.config if they first have access to the ~/.config directory itself. Likewise, people can only see into your ~/.config directory if they have access to your home directory. If you simply cut off access to your home directory, then it shuts out people from seeing the information under it.
You can lock down your home directory by running the chmod command as follows:
$ chmod 0700 ~/
This will keep other users, apart from the administrator, from being able to see any of your private data files or configuration information.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Porteus Kiosk 5.4.0
Porteus Kiosk is a lightweight Gentoo-based Linux operating system which has been scaled down and confined to allow the use of one application only: a web browser. The project has published a new release, Porteus Kiosk 5.4.0, which improves hardware decoding and enables the OpenH264 plugin for Firefox. The release announcement offers additional information: "I'm pleased to announce that Porteus Kiosk 5.4.0 is now available for download. Major software upgrades in this release include: Linux kernel 5.15.28, Google Chrome 98.0.4758.102 and Mozilla Firefox 91.7.1 ESR. Packages from the userland are upgraded to portage snapshot tagged on 20220320: link. Short changelog for 5.4.0 release: Added support for importing DER certificates through the 'import_certificates=' parameter. Hardware video decode feature is now enabled for screensaver video and screensaver webpage functions. Added support for dynamically generated remote configs. Kiosk identification and settings can be now passed through the URLs which contain an append parameters. Enabled OpenH264 plugin by default for the Firefox browser as it's needed for the WebRTC streams. Added 'cec-client' utility for controlling the displays over HDMI interfaces. Number of initial connections from the client to Porteus Kiosk Server has been reduced from 5 to 3. This optimization lowers the server overhead when multiple kiosks are booting at the same time." Further details are available in the distribution's changelog.
Finnix
The Finnix distribution is a small, self-contained, bootable Linux CD distribution for system administrators, based on Debian. The project celebrates its 22nd anniversary this month with the release of Finnix 124. "Finnix 124 includes a number of fixes, new packages and new features: wifi-connect helper utility will now display nearby access points if invoked without any command line options. ip= kernel command line network configuration now supports netmasks in addition to prefix lengths. Added a pure Python strings implementation. Explanation from the commit: I had avoided including strings because, while it's incredibly useful, it's the only desirable utility in the binutils package, which otherwise includes a bunch of compilation-related utilities, and the package itself is quite large. So in the words of the 'my mechanics' YouTube channel, I make a new one! It's not a 100% complete reimplementation of GNU binutils' strings, but is fine for casual binary checking. This is also set up so that if you do apt install binutils in the live environment, its strings will take precedence over the Python version. RISC-V (riscv64) unofficial build support added, in addition to amd64, i386, arm64, armhf, ppc64el, s390x. (Though as a reminder, AMD64 is the only officially supported architecture with released ISOs. For more information, see Platform support on Finnix.) Replaced the running systemd finnix.target with the more traditional multi-user.target. This is not noticeable in regular live environment use, but makes it easier for people expanding upon Finnix." Additional information is provided in the project's release announcement.
GParted Live 1.4.0-1
Curtis Gedak has announced the release of GParted Live 1.4.0-1, a new stable release of the project's Debian-based specialist live CD designed for disk partitioning and data rescue task. This release updates the GParted partitioning utility to version 1.4.0: "The GParted team is pleased to announce a new stable release of GParted Live. This release includes GParted 1.4.0, updated packages and other improvements. Items of note include: includes GParted 1.4.0; add labelling of mounted Btrfs, ext2/3/4 and XFS file systems; fix detection of mount points for encrypted file systems; fix crash scrolling quickly in the drive selection combobox; add bcache detection; add JBD external ext3/4 journal detection; based on the Debian 'Sid' repository as of 2022-03-29; Linux kernel image updated to 5.16.14. This release of GParted Live has been successfully tested on VirtualBox, VMware, BIOS, UEFI and physical computers with AMD/ATI, NVIDIA and Intel graphics." Continue to the release announcement for further details.
deepin 20.5
deepin is a Deban-based desktop distribution featuring the Deepin Desktop Environment (DDE). The project's latest release introduces support requests to the software centre and provides facial recognition as an option for signing into accounts. "In deepin 20.5, a great number of practical features collected from user feedback are developed and released, The stable kernel is upgraded to version 5.15.24, underlying vulnerabilities are fixed, and system compatibility and security are enhanced further. Face recognition, one of the biometric authentication methods, is supported on adapted devices. After enrolling your face in Control Center, next time on the lock screen and the login interface, you can log in to deepin with your face ID. By clicking 'Pin Screenshots' before taking a screenshot, the captured screenshot will be sticky on top of windows, and its position can be moved. While 'pinning' this picture to the desktop, you can use other apps at the same time to improve work efficiency." Additional information and screenshots can be found in the release announcement.
deepin 20.5 -- The Deepin desktop and application menu
(full image size: 1.6MB, 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: 2,703
- Total data uploaded: 41.8TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
Is your home directory accessible from other user accounts?
In this week's Questions and Answers column we talked about home directory permissions. Many Linux distributions default to leaving each user's home directory open and readable to other users (often with permissions 755). People who don't want to leave their files exposed for other computer users to view will often lock down their home directory permissions so only the user has access (permissions 700) or only allow digging into directories without seeing specific files (permissions 711). Is your home directory locked down? Let us know why it is (or is not) in the comments.
You can see the results of our previous poll on using Nextcloud in last week's edition. All previous poll results can be found in our poll archives.
|
My home directory permissions...
| Allow others read and execute/browse permission: | 200 (21%) |
| Allow others execute/browse permission: | 41 (4%) |
| Block access to everyone but me: | 613 (63%) |
| Other: | 114 (12%) |
|
|
| Website News |
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 11 April 2022. Past articles and reviews can be found through our Article Search page. 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)
- Bruce Patterson (podcast)
|
|
| 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 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 |
| • Issue 1107 (2025-02-03): siduction 2024.1.0, timing tasks, Lomiri ported to postmarketOS, Alpine joins Open Collective, a new desktop for Linux called Orbitiny |
| • Issue 1106 (2025-01-27): Adelie Linux 1.0 Beta 6, Pop!_OS 24.04 Alpha 5, detecting whether a process is inside a virtual machine, drawing graphics to NetBSD terminal, Nix ported to FreeBSD, GhostBSD hosting desktop conference |
| • Issue 1105 (2025-01-20): CentOS 10 Stream, old Flatpak bundles in software centres, Haiku ports Iceweasel, Oracle shows off debugging tools, rsync vulnerability patched |
| • Issue 1104 (2025-01-13): DAT Linux 2.0, Silly things to do with a minimal computer, Budgie prepares Wayland only releases, SteamOS coming to third-party devices, Murena upgrades its base |
| • 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 | 
SharkOS
Shark Linux was a new distribution of a Linux-based operating system. The goal of Shark Linux was to provide a stable environment with easy administration, targeting 64-bit AMD Opteron and Athlon 64 processors. Shark Linux aims to become a hardware optimised operating system with its own unique set of management tools and new functionality of the ANSI console for administrator use. Combined with ease of use and optimised code, it should outperform other out-of-the-box systems from the start. Shark Linux was derived from the Gentoo Linux project.
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.
|
|
• 
• 
• 
• 
• 
• 
• 
