 DistroWatch Weekly |
| DistroWatch Weekly, Issue 1001, 9 January 2023 |
Welcome to this year's 2nd issue of DistroWatch Weekly!
While many developers and open source enthusiasts were taking the last two weeks of December off work to enjoy a holiday, our Jesse Smith had other ideas. He decided to dedicate the time to playing with Arch Linux, one of the more well known rolling release distributions and the parent to over two dozen child distributions and spins. Arch has a reputation for technical simplicity and being a challenge to install and we explore those tropes in this week's Feature Story. Do you use Arch Linux or one of its many children? Let us know in this week's Opinion Poll. In our News section we discuss efforts to port KDE desktop software to OpenBSD along with a look back at the history of the HardenedBSD project. Meanwhile the Edubuntu distribution, which has been dormant for years, may be making a comeback in 2023. Did you use Edubuntu in the past? Let us know about your experiences with Edubuntu in the comments section. Plus we talk about the Slax distribution gaining faster access to persistent storage while Ubuntu tests out a new system installer. We also comment on OpenMandriva's new rolling release branch which is called ROME. Then, in our Questions and Answers column, we talk about verifying files, which were copied between storage drives, were transferred without any errors. 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:
|
| Feature Story (by Jesse Smith) |
Arch Linux at the end of 2022
Arch Linux is an independent Linux distribution and one of the more well known examples of the "keep it simple" (KIS) philosophy. In this case, "keep it simple" refers to simplicity from an engineering point of view. It refers to a technical simplicity rather than an uncluttered or an easy to use system from the user's point of view.
Arch is probably the world's most famous (or infamous) rolling release distribution. Its heavy focus on do-it-yourself computing, lack of a graphical system installer, and buyer beware attitude toward package upgrades has made running this project a rite of passage for many Linux users. People often talk about running Arch the same way they'd discuss earning a merit badge.
Personally, I have some complex views when it comes to the Arch Linux project. On one hand, I appreciate the concept of a technically clean, minimal distribution on which we can build things. I like having the option of starting light and adding components as needed, at least in theory. However, I often get the impression Arch Linux is trying to make things harder just for the sake of making things harder.
Arch Linux is intended to be installed via manual commands from a shell, the install media has no graphical interface and no graphical installer. Technically, there is a command line system installer, but, as I've pointed out before, it's buggy and limited. This makes it more effort to try to use the installer than to set up Arch by hand.
There doesn't seem to be any technical reason for this hands-on approach to installing Arch. There are over a dozen distributions in the DistroWatch database which are, essentially, "Arch Linux, but set up with the Calamares system installer and your option of desktop environment." Philosophically, Arch seems to want users to do more work, more reading, and more editing configuration files by hand. This approach isn't bad, necessarily, but it is more work and rarely offers an improved experience. It's similar to building your own kit car: if you have fun doing that sort of thing, that's great, but in the end it doesn't give you a benefit when you're driving on the road.
One more thought, before I talk more about my latest experience setting up and running Arch Linux: part of my mixed view with regards to Arch comes from not being sure if it is a distribution. Arch supplies a lot of packages, including the Linux kernel. It also supplies support forums, rich documentation, and a place for users to upload recipes for installing third-party software, similar to the BSD concept of ports. All of these things make Arch seem like a Linux distribution. On the other hand, Arch Linux, as an operating system, doesn't really have a design or layout of its own. It is like a box of Lego bricks we can assemble into a shape of our choosing - aided by detailed instructions - but without any automated help. It feels like a bunch of parts we can use, or not, as we like. This makes Arch more of a meta distribution than a regular Linux distribution.
These characteristics make it difficult to review Arch Linux because it doesn't really have a structure so much as optional pieces. As a reviewer, I'm basically tasked on building my own operating system from parts and then asked my opinion of it. I feel like I'm grading my own art project.
Getting started
I started experimenting with Arch in the middle of December to give myself a few weeks to experiment with the project. The Arch Linux install media at the time was 818MB in size. Before making use of it I recommend people check out the project's installation guide and its associated resources which walk the user through the steps necessary to prepare the computer's hard drive, set up time zones, enable networking, set the system clock, set a root password, install a boot loader, configure the boot loader, and add more packages.
There are a lot of manual steps, most of them covered in detail in the project's documentation. I say most, because the documentation tends to provide generic or least-tool-for-the-job instructions. There are personal preferences we can make, for example which text editor to use. We might also prefer to use more friendly tools than what the documentation suggests. For instance, I used the relatively friendly, menu-driven cfdisk partitioning tool while the wiki mentions fdisk.
At any rate, once the install steps have been completed we can reboot and load up our new copy of Arch. By default, Arch boots to a text console where we can sign in as the root user.
Post-install steps
Once I got signed into my new copy of Arch, I wanted to install software to get utilities and a desktop set up on my system. The first thing I noticed was networking wasn't enabled, though it had been working on the live disc. It turned out Network Manager was installed, but not enabled. Once the Network Manager service was enabled I was able to connect to my local network. Then I went to work installing new packages.
A quick note here on package management. Arch uses the pacman package manager which has a short, unusual command line syntax. The pacman utility is fast though and handled my requests to add, remove, and find software without problems. I sometimes found pacman to be a bit too literal with its searches where APT or DNF might be more forgiving, but on the whole it worked well.
Once I had a few command line utilities installed I set about performing the larger task of installing the X.Org display software, a desktop environment (Xfce), and a display manager. A display manager provides, among other things, a graphical login screen. Looking through the list of available display managers, I decided to go with LightDM as it is relatively independent of desktop environments. Others, such as GDM and SDDM, are often associated with specific desktops and will pull in dependencies from those desktops. LightDM seemed like safe, neutral territory.
At first, the graphical environment was not launching successfully. I thought it was perhaps because I'd freshly installed video drivers and they hadn't been detected yet. After a reboot, the graphical display still failed to launch and the LightDM service failed to start. I was still stuck at the command line.
After some troubleshooting which involved installing more generic video drivers, looking through the X.Org logs, and confirming the Xfce desktop environment would start if launched manually, I realized the issue was the LightDM service. It was crashing when launched, preventing me from getting to a graphical environment. I disabled it and installed GDM (the GNOME Display Manager) in its place. The GDM service started without problems and I was able to login to start enjoying my Xfce desktop.
Arch Linux 2022.12.01 -- Confirming Xfce runs
(full image size: 228kB, resolution: 1920x1080 pixels)
Well, at first GDM logged me into GNOME rather than Xfce. The display manager had pulled in a working GNOME desktop session (two, if you count the Wayland option) and I had to switch the session option to Xfce from the login screen.
Installing Xfce and its associated xfce4-goodies package provided me with the Xfce desktop, a terminal, the Thunar file manager, a settings panel, image viewer, task monitor, screenshot tool, and the Parole music player. This is about it, as we haven't yet installed a web browser, video player, office suite, or other applications. These can be fetched using pacman.
Making it feel like home
Since Arch is largely a do-it-yourself project with a lot of options and alternatives for those options, each step we take in setting up Arch branches us further away from other people's installs of the distribution. Each time we pick a login manager, a desktop environment, an office suite, or even a text editor our setup becomes more customized and less like someone else's version of Arch.
I feel this distinction, this path toward uniqueness, accelerates after we get a graphical environment installed and start acquiring desktop applications. At this point we're less likely to be following a guide which provides suggestions for boot loaders, drivers, and desktops and more likely to be installing whatever it is we want. Earlier I mentioned setting up and then reviewing Arch feels like making my own art project and then evaluating it. This impression really kicked into high gear at this stage because I was rapidly customizing my own system and key bits of information I'd usually record became more blurry.
How much disk space does a new copy of Arch use? It depends on which software we install. How much memory does it use? It depends on which services we enable and which desktop is installed. Does Arch work with my hardware? It does if I installed the proper drivers. Does Arch support filesystem snapshots? It can if I set up the right filesystem and utilities. Can I run Flatpaks on Arch? Yes, if I install the Flatpak framework. You get the idea; with Arch virtually nothing exists or works "out of the box", it's a manual, customized experience.
At the heart of the setup process is pacman. It's a blissfully fast, if frustratingly cryptic, package manager. Both the syntax and the options it offers while working are oddly arcane compared to other package managers. It works, but in an oddly terse way. By using pacman and the official Arch repositories we can get a good deal of popular software, such as text editors, LibreOffice, the VLC media player, and Firefox. Where I find the Arch experience falls down a bit is the official repositories are not particularly large. At the time of writing, Arch's website lists just over 13,500 packages. For comparison's sake, Debian's last stable release offered 60,000 packages and Fedora was offering about 67,700. This leaves some gaps in Arch's functionality.
Arch Linux 2022.12.01 -- Running the pacman package manager
(full image size: 500kB, resolution: 1920x1080 pixels)
We have the option of using third-party repositories to fill in the gaps in Arch's official offerings. The Flatpak framework, for example, is available as a package. Installing Flatpak on Arch automatically sets up the Flathub repository, giving us access to a wide range of desktop software.
Another alternative is the Arch User Repository (AUR). This is a collection of install scripts which are provided by the Arch community to fetch and install software not available in the official repositories.
While the AUR provides access to a great range of software and is often praised by the Arch community, there are warnings about using it in the Arch wiki and there is a strong "use at your own risk" tone in the guide providing instructions on using it. This is with good reason, this software is not verified or officially supported.
To start using the AUR we usually would want to install a package manager for building the available software. To do this, we'd first build one of the AUR's package managers (there are several options) as they all appear to be part of the AUR and not in the official repositories. There is a certain "chicken and the egg" issue here where we need to build software from the AUR in order to have easy access to the AUR. It serves to underline the separation between the official project and the community maintained AUR.
We can install the necessary packages, such as fakeroot, git, make, and gcc) to get started with the AUR. Then install one of the AUR package managers and use that to then fetch additional software. I took the popular yay AUR package manager as it works quickly and has a syntax which matches pacman.
Arch Linux 2022.12.01 -- The settings panel and Thunar file manager
(full image size: 216kB, resolution: 1920x1080 pixels)
I find using the AUR to supply third-party software usually works well, particularly for smaller utilities. However, I found it inconvenient when it came to desktop software and I much preferred using Flatpak when possible. Software installed from the AUR is usually compiled from source code and this means large programs may take several minutes, or in some cases, a few hours to compile. The same software can sometimes be fetched in a minute from Flatpak.
Major upgrades
One interesting characteristic of Arch Linux is its rolling release nature. Arch is constantly on the cutting edge of open source software and frequently publishes new versions of packages within a day or two of new releases becoming available upstream. I was hoping to get to try a few big upgrades during my three weeks with the distribution and I happily got my chance about a week into my trail when a new stable release of Xfce (version 4.18) became available at the same time as a kernel upgrade.
When I installed Arch, Xfce 4.16 was still the latest version of my chosen desktop environment, but within days 4.18 (the first new release of Xfce in a few years) became available. I performed a full system upgrade using pacman which pulled in a minor kernel upgrade and the new version of Xfce. The experience went smoothly and, following a reboot, I was able to enjoy the latest version of the Linux kernel and shiny new Xfce 4.18 packages.
Arch Linux 2022.12.01 -- Running the latest version of Xfce
(full image size: 389kB, resolution: 1920x1080 pixels)
One of the few issues I ran into when performing regular updates was pacman would sometimes ask me if I wanted to substitute packages I had already installed with alternatives. Which, to me, seems unnecessary and counter-intuitive. I specifically picked the packages I wanted, often from a list of alternatives. Offering to remove my selected package and replace it with an alternative I've already rejected seems pointless and risks breaking my workflow when the two packages are not compatible.
Conclusions
Eventually, I managed to fetch all the software I wanted and customized the Xfce desktop to my liking. I ended up with what I wanted - something fairly light in memory, no frills, with just the applications I wanted. Well, the applications I wanted, plus a few gigabytes of Flatpak and build dependencies which come from using non-official repositories.
Since Arch requires us to set almost everything up manually, I ended up with just the items I felt I needed (and the dependencies they needed). All the software was up to date, thanks to Arch's rolling release nature. Most software worked as expected, with the exception of the vim text editor which kept crashing when run with root privileges.
As you might expect, where I basically crafted the operating system from raw parts (parts that generally worked well), I ended up with something I liked. The issue I have with this experience, if I have any complaints, is that getting to this point takes so long. I could have installed Artix or EndeavourOS in under 15 minutes and ended up with a nearly identical user experience and collection of applications with fewer build dependencies and fewer helper tools. In short, using one of Arch's popular child distributions would take about four hours less time (including compile times for components from the AUR) and would result in a system that was about 3GB smaller on the disk.
Arch Linux 2022.12.01 -- Exploring the Xfce menu
(full image size: 312kB, resolution: 1920x1080 pixels)
This isn't to say using Arch is a bad idea, it is just that it's likely to appeal to a few very specific types of people. People who like to do everything manually, who like to be involved with the low-level processes, who want to read all the documentation, turn every knob, and tweak every file by hand. If you prefer building remote control helicopters to flying them, if you'd rather change your own car tyres rather than taking it into the shop, if you made your own cups from pottery clay, then Arch is probably ideal for you.
Arch Linux also appears to appeal to people who see doing things the hard way as a badge of honour or a rite of passage. Linux forums are often home to people who want to build Linux From Scratch just to try it, or who installed Arch just because they heard it was hard and wanted a challenge. These are perfectly valid approaches, but neither of them personally appeal to me. I can get the same result through faster, easier methods - such as one of Arch's many children with a graphical system installer and pre-configured desktop.
This isn't to say Arch is bad or unpleasant to use. The quality of the packages, the cutting edge software, and the documentation are all stellar selling points. It's just a system that is time consuming to get going compared to other projects and requires a certain amount of reading and patience. In the end though, you end up with an operating system made, in a sense, in your own image. To paraphrase Yoda, the Arch experience contains only what you take with you.
* * * * *
Visitor supplied rating
Arch Linux has a visitor supplied average rating of: 9.2/10 from 229 review(s).
Have you used Arch Linux? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
Porting KDE software to OpenBSD, history of HardenedBSD, Ubuntu tests new graphical installer, Slax gets faster persistent storage, Edubuntu makes a comeback, OpenMandriva publishes rolling-release branch
Rafael Sadowski has published a status update regarding KDE Plasma running on OpenBSD. The efforts to keep KDE Plasma and its related software up to date on OpenBSD are ongoing. "This will come as a surprise to some, but I was able to port (almost) all KDE Plasma components to OpenBSD. You can find all my work on GitHub in the sizeofvoid/wip-ports repository, branch kde-plasma-wip, directory x11/kde-plasma. I've been working on it for a very long time. At some point I was so frustrated that we don't have uDev and libInput. Read more here: OpenBSD and Wayland." The full overview can be found in this blog post.
* * * * *
The HardenedBSD project is a security-enhanced fork of FreeBSD which implements and tests new security features. Shawn Webb, one of the project's founders, shares a look back on the past decade of work on the project, lessons learned, and challenges faced. "This was the first large kernel development work I had ever done, so I had a lot to learn. Oliver and I worked in separate personal repos in GitHub for a while until Oliver created the HardenedBSD repo to unify our work. Our intent was to do initial development in the HardenedBSD repo with the goal of upstreaming to FreeBSD. History would take us on a different path. As we worked on our ASLR implementation, we updated our submission in FreeBSD's patch review system to solicit feedback from the FreeBSD project's official development team. With this being our first real foray into FreeBSD kernel development, we learned a lot through this review process. After two years of the development and review process, it was apparent that we differed with FreeBSD on the technical merits of our patch. Our work was not to be upstreamed due to a variety of reasons, some technical, some political. I eventually became overwhelmed and burned out and opted to abruptly discontinue the attempt at upstreaming our work."
* * * * *
The Ubuntu team is testing a new graphical installer which may soon replace the distribution's long lived Ubiquity installer. The Phoronix website has a write-up on what it is like to use the new Ubuntu installer along with screenshots of the experience. "When testing some Ubuntu 23.04 daily builds over the holidays on various test systems, I was pleased to see the new installer finally being used by default. This is making use of the Subiquity/Curtin install tech already used by Ubuntu Server and leveraging Google's Flutter SDK for the user-interface. Previously this new installer was available via an alternate ISO while the latest Ubuntu 23.04 daily builds are using it by default in place of the older Ubiquity with GTK interface. The user interface in my opinion is pleasant and subtly improved over the older Ubiquity installer."
* * * * *
The Slax distribution will soon be getting a new filesystem for persistent storage. DynFileFS was providing persistent storage for the distribution in the past, but the filesystem had some performance issues which are being addressed in DynFileFS 3.0. The author warns the new filesystem is not backward compatible with previous versions due to on-disk format changes. " I decided to review the code and as a result I rewrote the filesystem's internal logic completely. New DynFileFS version 3.0 is now available at GitHub. It uses different file format on disk, so it is not backward compatible, but I believe it is worth it. How does it work? Simply said, it provides a virtual file called 'virtual.dat' after mounting it to some directory. This file can be of any specified size, like 30GB, but it does not need to pre-allocate this huge amount of disk space on mount. All changes made to this virtual file are stored in an indexed storage in a different file on disk, for example called 'changes.dat', and this file grows in time as your changes are made. As a result, it stores only the changes on disk, and not the free space between them." Additional details are discussed in the Slax blog post.
* * * * *
The Edubuntu distribution was once a community edition of Ubuntu which was geared toward educational environments and computer labs. Though discontinued several years ago, the Edubuntu project may soon make a comeback. In an announcement on the Ubuntu Discourse forum, an outline of what the new Edubuntu flavour will look like was shared: "We're using the GNOME desktop. Edubuntu will simply, from a .iso image standpoint, be built on-top of the Ubuntu Desktop. This will ensure ease of configurability and administration as we won't have to 'reinvent the wheel' and instead use what the Ubuntu Desktop team has already established for workstations." The Discourse post includes additional information.
* * * * *
People who like using the OpenMandriva distribution, but who may not want to wait a year between releases or use the bleeding edge Cooker branch of the project are in luck. The OpenMandriva team now provides a rolling release branch intended for regular use, not just development and testing. The young branch is called ROME and is available in both KDE Plasma and GNOME editions. "ROME is the rolling release designed for individual users, it will receive the most up-to-date packages including recent security and bug fix upgrades. Our development branch, Cooker, will continue as the main point of development. It can break at any time, so if you are using Cooker and you will not get scared if your system will break every now and then, nothing changes for you. But if you are a user who needs a system to remain working, while still wanting to get the latest and greatest features without having to wait for a new point release, ROME is for you." Details on ROME can be found in the project's announcement.
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
Verifying a disk's contents was copied properly
Verifying-correctness asks: Let's say I have two disks, Disk A and Disk B. I copy the contents of Disk A to Disk B. How can I confirm Disk B is now identical to Disk A without comparing the files, like with a checksum, one at a time?
DistroWatch answers: It sounds like you're wondering if you can just take a single checksum of a hard drive and confirm its entire contents is identical to another drive's checksum. This probably will not work. Even if you clone one hard drive to another, using a tool such as dd or Clonezilla Live, the two drives might not share the same checksum because they can still have different sizes. Most drives, even if they are labelled as having the same capacity, may not be exactly identical down to the byte.
If you're not cloning the drives, instead using regular copy tools, then the location of files on the drive will depend on which filesystems you're using, fragmentation, and partition layout.
In short, whether you're copying files individually or cloning a disk, you're unlikely to end up with a perfectly identical copy of your original disk on the new drive. Which means, unfortunately, to confirm each file has copied correctly you're going to need to compare and verify each file on Disk B to confirm it is the same as the corresponding file on Disk A.
One of the easiest ways to automate confirming the files in two locations match exactly is to use a tool called rsync. The rsync utility is usually used to archive files or synchronize files between two locations. By default, rsync will do a few quick checks to see if two files look to be identical. It does this by comparing the sizes and modification times of the two files. If the files have the same name, size, and modification time then rsync will assume the files are a match.
However, if we want to make really sure the files are identical then we can instruct rsync to look at the checksums of each file. This basically compares the "fingerprints" of the file in both locations and confirms they match. When rsync finds a file where the checksums do not match it will either print the name of the file that isn't identical or copy the original file to overwrite the new file.
Let's look at an example. In this instance, I'm going to assume I have two hard drives attached to my computer. One is mounted at the location /media/disk_a and the other is mounted at /media/disk_b. Using the following command, I will ask rsync to check the contents of both disks. Since I'm using the "--dry-run" flag, rsync will print out any mismatched files between the two disks, but not do anything about the files not matching. Basically, it just reports it found an issue and will not try to fix it.
rsync -av --checksum --dry-run /media/disk_a/ /media/disk_b/
Going over the flags listed here, briefly, the "-av" part means rsync should pretend it is archiving or syncing files between the two disks and print out status messages along the way. The "--checksum" flag means we want to use a checksum to verify all the files match, not just guess files match based on their size and modification times. The "--dry-run" flag tells rsync to print out the names of any mismatched files, but not take any action.
We can omit the "--dry-run" flag. This will unleash rsync to copy or overwrite any files on Drive B which do not match the contents of Drive A. In short, when rsync is done, all of the files on Drive A should be copied to (and verified on) Drive B:
rsync -av --checksum /media/disk_a/ /media/disk_b/
The "--checksum" flag, and other options the rsync command understands, are covered in detail in the rsync manual page.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Archcraft 2023.01.01
Aditya Shakya has announced the release of Archcraft 2023.01.01, a brand-new version of the project's lightweight, Arch-based Linux distribution that ships with Openbox and bspwm window managers (both highly customised) and a careful selection of lightweight applications: "January 2023 release available. You need to re-install Archcraft for this update. After that, you can update to the next release with pacman. Changelog: created the ISO image base from scratch; better network manager support, various VPN plugins; better Bluetooth support; Pipewire for sound/audio (systemwide, Bluetooth, jack); better printer support; almost all audio, video and image codecs; better file manager functionality (mounting, networking, archiving); better multi-monitor support; CJK fonts pre-installed; new themes for both Openbox and bspwm; creating user themes is super easy now; many minor changes." Here is the brief release announcement.
Archcraft 2023.01.01 -- Greeted by the welcome screen
(full image size: 3.0MB, resolution: 3840x2400 pixels)
DragonFly BSD 6.4.0
The DragonFly BSD project has published a new release, version 6.4.0, which provides the latest evolution of the 6.x series. The release announcement highlights some of the key features, particularly advancements made to the operating system's drivers. "DragonFly version 6.4 is the next step in the 6.x release series. This version has hardware support for type-2 hypervisors with NVMM, an amdgpu driver, the experimental ability to remote-mount HAMMER2 volumes, and many other changes. The details of all commits between the 6.2 and 6.4 releases are available in the associated commit messages for 6.4.0. Changes: recommend updating all systems, a locally-exploitable kernel vulnerability was fixed for this release; fix execvPe()s environment passing; fix ktrace's handling of 'long' system call return values; fix a sysv semaphore panic related to an exit race; fix a namecache bloating issue related to dead entries that could slow systems down over time...." Additional details can be found in the project's release notes for DragonFly BSD 6.4.0.
Nitrux d5c7cdff
Nitrux is a Linux distribution based on Debian's Unstable (sid) branch with additional packages pulled in from Ubuntu repositories. The distribution's latest release (which is alternatively labelled "2.6.0", "ff", and "d5c7cdff") includes version 6.1.0 of the Linux kernel, KDE Plasma 5.26.4, Pipewire, and includes Wayland as a session option. "We've updated the following components of the distribution. For other information, see Notes. KDE Plasma to version 5.26.4, KDE Frameworks to version 5.101.0, and KDE Gear to version 22.12.0. Firefox to version 108.0.1. We've updated MESA to version 23.0git. Disclaimer: We do not develop or package MESA. To file bugs against MESA, please use their bug tracker. We've added PipeWire and Wayland by default. Plasma (Wayland) is available to select from SDDM. Important: If using an NVIDIA GPU, check the KDE Wiki instructions here to use the Plasma (Wayland) session, YMMV. Disclaimer: We do not develop KWin, Wayland, Plasma Wayland or the NVIDIA proprietary driver. For the best experience using the Plasma (Wayland) session, use a Linux-friendly GPU and driver such as Intel or AMD. The Plasma (Wayland) session is not the default; the Plasma (X11) session is still the default." Additional information is provided in the release announcement.
OpenMandriva Lx 23.01 "ROME"
OpenMandriva's grand entry to the world of "rolling-release" distributions comes to fruition today with the initial release the project's "ROME" edition. It aims to continually provide the most up-to-date software packages without compromising the system stability. "To make sure you do not fall behind, we are announcing a new way to keep you up to date - ROME, the OpenMandriva rolling edition. ROME is the rolling release, designed for individual users; it will receive the most up-to-date packages, including recent security and bug-fix updates. A lot of interesting things have happened in the rolling branch since the traditional point release. Among others, KDE Frameworks 5.101, Plasma Desktop 5.26.4, KDE Applications 22.12.0 are in, and everything has been rebuilt with the Clang 15.06 compiler. Linux kernel 6.1.1 (Clang-compiled kernel as default, with the option to install GCC-compiled kernel easily from the om-welcome module)." See the release announcement and the release notes for further information.
Nobara Project 37
Nobara Project is a modified version of Fedora Linux with user-friendly fixes added to it. The distribution comes with certain features that do not ship with the regular Fedora, such as WINE dependencies, OBS Studio, 3rd party codec packages for GStreamer, NVIDIA drivers, and some package fixes. Nobara's latest release is based on Fedora 37: "Nobara packages rebased on top of Fedora 37. Notable package updates: Linux kernel updated to 6.0.16, all previous patches included, gamescope HDR patches added; glibc updated to 2.36 (still includes all previous fixes); GameScope updated to latest git; MangoHud updated to 0.6.8; GOverlay updated to 0.9.1; Blender updated to 3.4.1; ROCM OpenCL/HIP packages updated to 5.4.1; Steam Tinker Launch updated to 12.0 and re-added to Base OS; vkBasalt updated to 0.3.2.8; supergfxctl updated to 5.0.1 (removes broken/invalid 'dedicated' mode); asusctl updated to 4.5.8; AppArmor dnsmasq profile updated to allow WayDroid...." Here is the complete changelog.
Nobara Project 37 -- Exploring the application menu
(full image size: 7.9MB, resolution: 3840x2400 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,815
- Total data uploaded: 42.7TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
Arch Linux and its children
We began this week's Weekly newsletter with a discussion on Arch Linux, a popular rolling release distribution which has become an increasingly popular parent distribution in recent years. There are a lot of child distributions which use Arch as a base along with the Calamares system installer and a pre-configured desktop environment.
We'd like to hear how many of our readers use Arch or one of Arch's children. Let us know your reasons for choosing a member of the Arch Linux family in the comments.
You can see the results of our previous poll on the number of partitions on our readers' hard drives in last week's edition. All previous poll results can be found in our poll archives.
|
Are you running Arch?
| I am running Arch Linux: | 433 (17%) |
| I run a child of Arch Linux: | 773 (30%) |
| I do not run a member of the Arch family: | 1407 (54%) |
|
|
| Website News |
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 16 January 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:
|
|
| 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 1100 (2024-12-09): Oreon 9.3, differences in speed, IPFire's new appliance, Fedora Asahi Remix gets new video drivers, openSUSE Leap Micro updated, Redox OS running Redox OS |
| • Issue 1099 (2024-12-02): AnduinOS 1.0.1, measuring RAM usage, SUSE continues rebranding efforts, UBports prepares for next major version, Murena offering non-NFC phone |
| • Issue 1098 (2024-11-25): Linux Lite 7.2, backing up specific folders, Murena and Fairphone partner in fair trade deal, Arch installer gets new text interface, Ubuntu security tool patched |
| • Issue 1097 (2024-11-18): Chimera Linux vs Chimera OS, choosing between AlmaLinux and Debian, Fedora elevates KDE spin to an edition, Fedora previews new installer, KDE testing its own distro, Qubes-style isolation coming to FreeBSD |
| • Issue 1096 (2024-11-11): Bazzite 40, Playtron OS Alpha 1, Tucana Linux 3.1, detecting Screen sessions, Redox imports COSMIC software centre, FreeBSD booting on the PinePhone Pro, LXQt supports Wayland window managers |
| • Issue 1095 (2024-11-04): Fedora 41 Kinoite, transferring applications between computers, openSUSE Tumbleweed receives multiple upgrades, Ubuntu testing compiler optimizations, Mint partners with Framework |
| • Issue 1094 (2024-10-28): DebLight OS 1, backing up crontab, AlmaLinux introduces Litten branch, openSUSE unveils refreshed look, Ubuntu turns 20
| | • Issue 1093 (2024-10-21): Kubuntu 24.10, atomic vs immutable distributions, Debian upgrading Perl packages, UBports adding VoLTE support, Android to gain native GNU/Linux application support |
| • Issue 1092 (2024-10-14): FunOS 24.04.1, a home directory inside a file, work starts of openSUSE Leap 16.0, improvements in Haiku, KDE neon upgrades its base |
| • Issue 1091 (2024-10-07): Redox OS 0.9.0, Unified package management vs universal package formats, Redox begins RISC-V port, Mint polishes interface, Qubes certifies new laptop |
| • Issue 1090 (2024-09-30): Rhino Linux 2024.2, commercial distros with alternative desktops, Valve seeks to improve Wayland performance, HardenedBSD parterns with Protectli, Tails merges with Tor Project, Quantum Leap partners with the FreeBSD Foundation |
| • Issue 1089 (2024-09-23): Expirion 6.0, openKylin 2.0, managing configuration files, the future of Linux development, fixing bugs in Haiku, Slackware packages dracut |
| • Issue 1088 (2024-09-16): PorteuX 1.6, migrating from Windows 10 to which Linux distro, making NetBSD immutable, AlmaLinux offers hardware certification, Mint updates old APT tools |
| • Issue 1087 (2024-09-09): COSMIC desktop, running cron jobs at variable times, UBports highlights new apps, HardenedBSD offers work around for FreeBSD change, Debian considers how to cull old packages, systemd ported to musl |
| • Issue 1086 (2024-09-02): Vanilla OS 2, command line tips for simple tasks, FreeBSD receives investment from STF, openSUSE Tumbleweed update can break network connections, Debian refreshes media |
| • Issue 1085 (2024-08-26): Nobara 40, OpenMandriva 24.07 "ROME", distros which include source code, FreeBSD publishes quarterly report, Microsoft updates breaks Linux in dual-boot environments |
| • Issue 1084 (2024-08-19): Liya 2.0, dual boot with encryption, Haiku introduces performance improvements, Gentoo dropping IA-64, Redcore merges major upgrade |
| • Issue 1083 (2024-08-12): TrueNAS 24.04.2 "SCALE", Linux distros for smartphones, Redox OS introduces web server, PipeWire exposes battery drain on Linux, Canonical updates kernel version policy |
| • Issue 1082 (2024-08-05): Linux Mint 22, taking snapshots of UFS on FreeBSD, openSUSE updates Tumbleweed and Aeon, Debian creates Tiny QA Tasks, Manjaro testing immutable images |
| • Issue 1081 (2024-07-29): SysLinuxOS 12.4, OpenBSD gain hardware acceleration, Slackware changes kernel naming, Mint publishes upgrade instructions |
| • Issue 1080 (2024-07-22): Running GNU/Linux on Android with Andronix, protecting network services, Solus dropping AppArmor and Snap, openSUSE Aeon Desktop gaining full disk encryption, SUSE asks openSUSE to change its branding |
| • Issue 1079 (2024-07-15): Ubuntu Core 24, hiding files on Linux, Fedora dropping X11 packages on Workstation, Red Hat phasing out GRUB, new OpenSSH vulnerability, FreeBSD speeds up release cycle, UBports testing new first-run wizard |
| • Issue 1078 (2024-07-08): Changing init software, server machines running desktop environments, OpenSSH vulnerability patched, Peppermint launches new edition, HardenedBSD updates ports |
| • Issue 1077 (2024-07-01): The Unity and Lomiri interfaces, different distros for different tasks, Ubuntu plans to run Wayland on NVIDIA cards, openSUSE updates Leap Micro, Debian releases refreshed media, UBports gaining contact synchronisation, FreeDOS celebrates its 30th anniversary |
| • Issue 1076 (2024-06-24): openSUSE 15.6, what makes Linux unique, SUSE Liberty Linux to support CentOS Linux 7, SLE receives 19 years of support, openSUSE testing Leap Micro edition |
| • Issue 1075 (2024-06-17): Redox OS, X11 and Wayland on the BSDs, AlmaLinux releases Pi build, Canonical announces RISC-V laptop with Ubuntu, key changes in systemd |
| • Issue 1074 (2024-06-10): Endless OS 6.0.0, distros with init diversity, Mint to filter unverified Flatpaks, Debian adds systemd-boot options, Redox adopts COSMIC desktop, OpenSSH gains new security features |
| • Issue 1073 (2024-06-03): LXQt 2.0.0, an overview of Linux desktop environments, Canonical partners with Milk-V, openSUSE introduces new features in Aeon Desktop, Fedora mirrors see rise in traffic, Wayland adds OpenBSD support |
| • Issue 1072 (2024-05-27): Manjaro 24.0, comparing init software, OpenBSD ports Plasma 6, Arch community debates mirror requirements, ThinOS to upgrade its FreeBSD core |
| • Issue 1071 (2024-05-20): Archcraft 2024.04.06, common command line mistakes, ReactOS imports WINE improvements, Haiku makes adjusting themes easier, NetBSD takes a stand against code generated by chatbots |
| • Issue 1070 (2024-05-13): Damn Small Linux 2024, hiding kernel messages during boot, Red Hat offers AI edition, new web browser for UBports, Fedora Asahi Remix 40 released, Qubes extends support for version 4.1 |
| • Issue 1069 (2024-05-06): Ubuntu 24.04, installing packages in alternative locations, systemd creates sudo alternative, Mint encourages XApps collaboration, FreeBSD publishes quarterly update |
| • Issue 1068 (2024-04-29): Fedora 40, transforming one distro into another, Debian elects new Project Leader, Red Hat extends support cycle, Emmabuntus adds accessibility features, Canonical's new security features |
| • Issue 1067 (2024-04-22): LocalSend for transferring files, detecting supported CPU architecure levels, new visual design for APT, Fedora and openSUSE working on reproducible builds, LXQt released, AlmaLinux re-adds hardware support |
| • Issue 1066 (2024-04-15): Fun projects to do with the Raspberry Pi and PinePhone, installing new software on fixed-release distributions, improving GNOME Terminal performance, Mint testing new repository mirrors, Gentoo becomes a Software In the Public Interest project |
| • Issue 1065 (2024-04-08): Dr.Parted Live 24.03, answering questions about the xz exploit, Linux Mint to ship HWE kernel, AlmaLinux patches flaw ahead of upstream Red Hat, Calculate changes release model |
| • Issue 1064 (2024-04-01): NixOS 23.11, the status of Hurd, liblzma compromised upstream, FreeBSD Foundation focuses on improving wireless networking, Ubuntu Pro offers 12 years of support |
| • Issue 1063 (2024-03-25): Redcore Linux 2401, how slowly can a rolling release update, Debian starts new Project Leader election, Red Hat creating new NVIDIA driver, Snap store hit with more malware |
| • Issue 1062 (2024-03-18): KDE neon 20240304, changing file permissions, Canonical turns 20, Pop!_OS creates new software centre, openSUSE packages Plasma 6 |
| • Issue 1061 (2024-03-11): Using a PinePhone as a workstation, restarting background services on a schedule, NixBSD ports Nix to FreeBSD, Fedora packaging COSMIC, postmarketOS to adopt systemd, Linux Mint replacing HexChat |
| • Issue 1060 (2024-03-04): AV Linux MX-23.1, bootstrapping a network connection, key OpenBSD features, Qubes certifies new hardware, LXQt and Plasma migrate to Qt 6 |
| • Issue 1059 (2024-02-26): Warp Terminal, navigating manual pages, malware found in the Snap store, Red Hat considering CPU requirement update, UBports organizes ongoing work |
| • Issue 1058 (2024-02-19): Drauger OS 7.6, how much disk space to allocate, System76 prepares to launch COSMIC desktop, UBports changes its version scheme, TrueNAS to offer faster deduplication |
| • Issue 1057 (2024-02-12): Adelie Linux 1.0 Beta, rolling release vs fixed for a smoother experience, Debian working on 2038 bug, elementary OS to split applications from base system updates, Fedora announces Atomic Desktops |
| • Issue 1056 (2024-02-05): wattOS R13, the various write speeds of ISO writing tools, DSL returns, Mint faces Wayland challenges, HardenedBSD blocks foreign USB devices, Gentoo publishes new repository, Linux distros patch glibc flaw |
| • Issue 1055 (2024-01-29): CNIX OS 231204, distributions patching packages the most, Gentoo team presents ongoing work, UBports introduces connectivity and battery improvements, interview with Haiku developer |
| • Issue 1054 (2024-01-22): Solus 4.5, comparing dd and cp when writing ISO files, openSUSE plans new major Leap version, XeroLinux shutting down, HardenedBSD changes its build schedule |
| • Issue 1053 (2024-01-15): Linux AI voice assistants, some distributions running hotter than others, UBports talks about coming changes, Qubes certifies StarBook laptops, Asahi Linux improves energy savings |
| • Issue 1052 (2024-01-08): OpenMandriva Lx 5.0, keeping shell commands running when theterminal closes, Mint upgrades Edge kernel, Vanilla OS plans big changes, Canonical working to make Snap more cross-platform |
| • Issue 1051 (2024-01-01): Favourite distros of 2023, reloading shell settings, Asahi Linux releases Fedora remix, Gentoo offers binary packages, openSUSE provides full disk encryption |
| • Issue 1050 (2023-12-18): rlxos 2023.11, renaming files and opening terminal windows in specific directories, TrueNAS publishes ZFS fixes, Debian publishes delayed install media, Haiku polishes desktop experience |
| • Issue 1049 (2023-12-11): Lernstick 12, alternatives to WINE, openSUSE updates its branding, Mint unveils new features, Lubuntu team plans for 24.04 |
| • Issue 1048 (2023-12-04): openSUSE MicroOS, the transition from X11 to Wayland, Red Hat phasing out X11 packages, UBports making mobile development easier |
| • Issue 1047 (2023-11-27): GhostBSD 23.10.1, Why Linux uses swap when memory is free, Ubuntu Budgie may benefit from Wayland work in Xfce, early issues with FreeBSD 14.0 |
| • Issue 1046 (2023-11-20): Slackel 7.7 "Openbox", restricting CPU usage, Haiku improves font handling and software centre performance, Canonical launches MicroCloud |
| • 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 | 
OpenGroupware.org Knoppix CD
The OpenGroupware.org (OGo) Knoppix CD was a bootable CD which contains a complete Debian GNU/Linux system, a fully configured OGo installation, a Cyrus server and some more Linux software. It's based on the original Knoppix CD created by Knopper.Net Consulting. It's certainly the fastest way to get a usable OpenGroupware.org demo up and running!
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.
|
|
• 
• 
• 
• 
• 
• 
• 
