 DistroWatch Weekly |
| DistroWatch Weekly, Issue 983, 29 August 2022 |
Welcome to this year's 35th issue of DistroWatch Weekly!
Sometimes people ask why there are so many Linux distributions, hundreds of them. One of the reasons is there are so many different possible ways of doing things, so many different styles of computing which suit people, and so many different priorities on which people want to focus. This week we talk about a wide range of projects and priorities, starting with the Qubes OS platform. The Qubes project creates a platform which isolates components and tasks from each other, securing elements of an operating system from exploit from other parts. We also talk about Alchg Linux, an Arch-based project designed to use a small amount of resources while being run from removable media. In our News section we explore how some distributions, such as Quarkos, are adopting classic desktop environments like Trinity (a fork of KDE's legacy version 3.x series). Meanwhile, the Debian project is considering how to best handle firmware, specifically non-free firmware, in future versions of the distribution. We also report on an issue with Arch-based distributions which can prevent systems from booting. Plus we share background on immutable operating systems, what they are and why people use them. We're also pleased to share the releases of past week and list the torrents we are seeding. We wish you all a fantastic week and happy reading!
Content:
|
| Feature Story (by Jesse Smith) |
Qubes OS 4.1.1
Qubes OS is an unusual project which strives to perform two difficult tasks in parallel. First, it attempts to isolate various tasks and elements of the operating system to prevent the compromising of one component from affecting other components. Second, it attempts to make this experience virtually seamless for desktop users.
The idea here is that the user should be able to use their applications in a way which allows each application (or a group of applications) to be isolated from the rest of the system. If our web browser is hijacked it shouldn't give access to our office documents, for example.
I downloaded the latest version of Qubes OS, which is provided as a 5.4GB ISO for 64-bit (x86_64) computers. Booting from this ISO displays a boot menu where we can immediately launch the system installer or run a self-check on the media and then start the install process. There is no option to launch a live desktop environment.
By default, Qubes runs Fedora software. This includes getting up and running using the Anaconda system installer. The installing experience is virtually identical to setting up Fedora 36 Workstation with the exception the default software selection uses the Xfce desktop instead of GNOME.
The Anaconda installer presents the steps we take to set up the operating system as a series of modules we can access in the order of our choosing from a hub screen. After going through the modules and (mostly) taking the defaults, the installer refused to continue. At the bottom of the page a message informed me that I'd need to complete all the steps currently marked with an alert icon. The problem was none of the modules was marked with an icon.
I went through the modules again and ran into the same warning without the ability to continue. I restarted the computer and tried again. This time I took all the defaults. This caused the partitioning module to complain, saying the automated partition layout wouldn't work. I set up partitions for booting, swap, and root. Then returned to the hub screen where I was shown the same warning about completing all marked modules before continuing, despite no modules being marked.
I attempted another reboot and tried again. This time trying to take the defaults, apart from changing the disk layout to a Btrfs volume. Once again all modules showed clear and yet the installer refused to continue to proceed, reporting I had to address errors first.
At this point I gave up. There are few things worse than inaccurate error messages when trying to troubleshoot problems and I figured my time would be better spent elsewhere. To my mind this experience really highlights just how bad the notorious Anaconda installer is. It's inconsistent, slow, and (in this case) just plain buggy. I think it calls into question both why Fedora continues to use it and why Qubes insists on using the fast-moving Fedora as its default platform for software packages.
* * * * *
Alchg Linux
I decided to move on to one of the relatively young projects on the DistroWatch waiting list. Alchg Linux is an Arch-based Linux distribution which reportedly provides a minimal desktop environment which runs from a live disc. The operating system is intended to perform simple desktop tasks on 64-bit machines (an experimental 32-bit build is in testing at the time of writing). The distribution reportedly requires less than 1GB of RAM and is distributed as a 1.4GB ISO.
Early impressions
I found Alchg will boot in both Legacy BIOS and UEFI modes on my laptop. When starting in BIOS mode the system displays the Arch Linux boot screen with options to load the live desktop or load the whole operating system into RAM before launching the live desktop. When booting in UEFI mode the system displays a similar menu with less branding. The countdown timer on the menu is accompanied by a loud beeping sound from the speaker which will quickly draw attention (and anger) from anyone nearby.
When the system finished booting it presented me with the Openbox window manager which places a panel across the bottom of the screen to display the application menu, task switcher, and system tray. The user interface, I was surprised to find, used the Japanese language in most places. The application menu and most graphical tools displayed Japanese characters while the terminal (QTerminal) displayed most information using English.
This surprised me as the project's website, boot menu, and status messages during boot had been in English. I went back and restarted the system to discover that, during the boot process, a menu quickly appears and asks us to press "1" for Japanese or "2" for English. The default is to use Japanese after a few seconds if we do not manually make a selection.
Alchg Linux 2022.06.25 -- A mixture of English and Japanese text
(full image size: 143kB, resolution: 1920x1080 pixels)
This language selection prompt posed a problem when I was using my laptop because my keyboard was not yet initialized when the menu was displayed, meaning I could not make a selection before the menu timed out, resulting in the system using Japanese. When I booted the system in VirtualBox I could make the language selection. When I did this most of the desktop would display English menus and graphical components used English. However, whenever I visited websites in the default web browser (Vivaldi), any international websites such as YouTube, Google, and DistroWatch would be directed to display text in Japanese. This meant, despite me selecting English at boot time, I still ended up viewing many websites in Japanese. I suspect this is a bonus for people fluent in Japanese, but I am not among their number and it was frustrating to not have my language selection respected by the web browser.
Included software
As already mentioned, Alchg uses the Openbox window manager to provide its graphical user interface and the Vivaldi web browser. It also ships with the QTerminal for accessing a command line. There are a few other programs for configuring Openbox and a couple of applications which are buried in the application menu. They can be accessed by going to the Application menu -> Config -> Alchg -> All Applications. Some of the launchers work and some do not. The ones which do provide access to an image viewer and a remote desktop tool, and some configuration options.
Digging deeper we find manual pages for the command line tools, the systemd init software, and version 5.15 of the Linux kernel.
Additional software can be installed using the pacman command line package manager. To install new packages we need root access which is granted using the su command and the password "root". The sudo utility is installed, but does not appear to be set up to work with the default user.
I found it interesting that when I installed alternative web browsers, such as Firefox, they displayed international pages in English, while Vivaldi displayed these pages in Japanese.
Hardware
When running Alchg in a VirtualBox instance the system ran smoothly. It worked well, though did not integrate with the VirtualBox host. When running on my laptop Alchg mostly worked well. It could detect my wireless card, sound worked, and the system ran quickly. However, the keyboard did not initialize quickly enough to respond to the language selection prompt. As previously mentioned, booting in UEFI mode caused five loud beeps to accompany the boot menu countdown. I also discovered my laptop's media keys were not recognised when running Alchg.
The distribution is fairly light and runs a minimal window manager. This results in both fast performance and a small memory footprint of about 200MB.
Conclusions
Alchg Linux is still a young project and some rough edges are to be expected. In this case though there are a lot of rough edges. The basic functionality of a live medium is present. The distribution boots, can connect to local networks, and browse the web. However, that is about all it does and it does even these limited functions with some caveats. The language support is minimal and (on my laptop) buggy and, in the case of the Vivaldi browser, inconsistent. The loud beeping at boot time and the lack of support for media keys is unfortunate. The application menu is a bit disorganized.
Most of these problems are not deal breakers, but they are pretty standard bits of functionality which other live distributions usually handle gracefully. I think Alchg needs another few releases to get these items sorted out before I'd suggest using it. Though I will say that the lightweight Openbox environment is small and fast, making it an appealing feature of this project.
* * * * *
Visitor supplied rating
Qubes OS has a visitor supplied average rating of: 8.8/10 from 33 review(s).
Have you used Qubes OS? You can leave your own review of the project on our ratings page.
|
| Miscellaneous News (by Jesse Smith) |
Canonical offers Wayland implementations through Mir, Quarkos introduces new Trinity edition, Debian considers non-free firmware stance, Arch-based systems encounter GRUB issue
One of the in-house projects to appear in Canonical's line-up over the years is Mir, a display server which attempted to address issues with X.Org in a similar fashion to Wayland: by replacing it. Over time, Mir shifted focus from its own protocol, which was used in Ubuntu's Unity 8 interface, to being a more flexible display server. Mir is now capable of being a Wayland implementation and may provide key building blocks for developers of desktop environments which want to implement Wayland's protocol, but who lack the time or resources to start from scratch. Alan Griffiths explains: "The Mir project provides libraries for creating Wayland compositors. The design is intended to make it easy build something simple and easy to customize the compositor in a number of ways. Within the Mir codebase there are four different Wayland compositors each demonstrating a different behaviour. There are additional compositors maintained and written by the Mir team in a number of Snaps. Most notably, Ubuntu Frame. Outside the Mir codebase there are at least four compositors based on Mir that support different uses."
* * * * *
It might seem unlikely for any young Linux distributions to adopt a classic desktop environment which has been mostly static for over a decade. However, that is what the Quarkos (previously Quark) project is doing. Quarkos is introducing a new edition featuring the classic Trinity desktop, a fork of KDE 3, which will complement its existing KDE Plasma desktop. "At the occasion of the completely new Quarkos release, we have made a few important changes to the project. The project and operating system name has been slightly modified, it is no longer Quark, now Quarkos. New official dedicated Trinity desktop live media is now available too, so there are two download options for Quarkos, Ubuntu based Trinity 14.0.12 desktop and the still default Plasma desktop live media." The announcement offers details and download links.
* * * * *
The Debian project takes a strong stance in favour of open source and free software, choosing to avoid the use of software or firmware that is proprietary or not freely licensed. While beneficial in some ways, Debian's approach means there is no non-free firmware on the official Debian media. Since non-free firmware is often used to make wireless networking cards function, this effectively blocks many users from being able to get on-line. The project currently maintains unofficial install media with the non-free firmware included and many people use this alternative media, but it is not always obvious this alternative approach exists. The project is currently considering how best to approach the use and distribution of non-free firmware by way of a general resolution.
* * * * *
The EndeavourOS project is reporting on an issue users of Arch-based systems are facing. According to the Endeavour project, many people running distributions based on Arch Linux are running into a problem where their systems will no longer boot. "Since the recent grub issue has impacted a lot of people, we wanted to provide full transparency based on the information we have so far. The situation with this package is still evolving and we will update this post with more information as it becomes available. After updating to grub 2.06.r322 many users reported that their machines could fail to boot or booted directly into the BIOS or another OS." Details on what caused the issue and links to tips on fixing the problem are provided in the news post. At the time of writing no news post addressing the problem has appeared on the Arch Linux website, however there is a bug report filed against the issue.
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
All about immutable operating systems
No-desire-to-change asks: What is an immutable operating system and what benefits would one achieve by using such an OS? Would this be appropriate for the average desktop environment, or is it better suited to servers and containers? Other than Fedora Silverblue and openSUSE MicroOS what other distributions use this approach? Are security updates allowed with an immutable OS?
DistroWatch answers: In practical terms, an immutable operating system is one where the base system (the core of the operating system) is fixed and unchanging. The underlying operating system is not altered and the root filesystem is typically read-only, meaning you can't edit its files.
Rather than editing the core of the operating system to change its configuration or upgrade packages, changes to services, applications, and data files are added on top of the base operating system. Imagine the core of the operating system as an unchanging foundation and any customizations or new programs we run on it are layers we stack on top of the base.
The Fedora Silverblue project sums up the concept as follows:
Unlike other operating systems, Silverblue is immutable. This means that every installation is identical to every other installation of the same version. The operating system that is on disk is exactly the same from one machine to the next, and it never changes as it is used.
Silverblue's immutable design is intended to make it more stable, less prone to bugs, and easier to test and develop. Finally, Silverblue's immutable design also makes it an excellent platform for containerized applications as well as container-based software development. In each case, applications (apps) and containers are kept separate from the host system, improving stability and reliability.
The idea here is that, since the base operating system doesn't change, we can upgrade to a new version by simply overwriting the old copy with a new one. The base system gets swapped out, but the layers (our files, configuration, containerized services, and customizations) live in separate layers and are not mixed into the base operating system.
What is achieved by such a system? In theory there is an added layer of security since the core operating system is read-only. It's also easier to test and develop, in some aspects, because my copy of the immutable core should be identical to your copy of the immutable core. There are no blurred edges between the original operating system and changes I made to my copy because my changes are in a separate layer.
In theory this also makes updates a more simple concept because instead of checking each package for changes and then trying to upgrade them in place, we can throw away the old core layer and replace it with a new one.
Would this be appropriate for a desktop environment? Some people think so. Fedora Silverblue is intended to look and act very similar to Fedora's Workstation edition. Again, quoting from the Silverblue website: "Silverblue is a variant of Fedora Workstation. It looks, feels and behaves like a regular desktop operating system, and the experience is similar to what you find with using a standard Fedora Workstation."
While it is intended to work the same for most tasks, people who try Silverblue need to get used to doing some things a little differently. Package management and configuration changes are handled differently than on a traditional operating system. These differences are covered in the Silverblue documentation.
The openSUSE MicroOS team takes a different stance. openSUSE's immutable platform is intended specifically for servers and container platforms:
Installing openSUSE MicroOS you get a quick, small environment for deploying containers, or any other workload that benefits from transactional updates.
Which other distributions use this approach? I don't think there are many Linux distributions which run immutable operating systems. There is more of a draw to do this sort of thing on commercial platforms than community ones, probably in part due to the reduced variation between systems and associated support costs. Some NAS systems, like TrueNAS, tend to act like immutable operating systems (intending to act like a fixed platform), even if they are not entirely read-only, immutable platforms. Android and other mobile operating systems, such as Murena, are typically immutable. If you have an Android phone and look at its mount points you'll see its root filesystem is read-only and the base operating system is updated as a fixed image. Likewise, UBports, by default, uses a read-only filesystem though it is possible to override this and make changes to the underlying operating system.
Immutable operating systems can be applied anywhere, but they tend to be used in situations where people want a small, unchanging base operating system that will run containers or portable packages (like AppImages or Flatpaks) on top of the core operating system. This makes immutable platforms ideal for servers that run containers, mobile devices, and embedded devices.
As to whether an immutable operating system can receive updates, they can and typically do. The difference is, with a classic operating system the individual components or packages are updated. With immutable operating systems you'll typically get the entire base system updated as one big piece. Then the containers or portable packages you installed on top of the immutable base are updated separately. If you've ever updated an Android phone you will have experienced this where the apps are updated as separate components, but the base system is updated as one big change.
This process probably feels more familiar to people in the BSD communities as projects like FreeBSD, OpenBSD, and NetBSD (while not immutable) draw a distinct line between the core operating system and third-party packages which are added on top of the system. The base operating system is upgraded separately from the third-party programs which run on it.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Tails 5.4
The Amnesic Incognito Live System (Tails) is a Debian-based Linux live DVD/USB with the goal of providing complete Internet anonymity for the user. The project's latest release, Tails 5.4, introduces an updated kernel with newer hardware support, along with some kernel-related security hardening. This release also disables forced HTTPS connections to make it easier for users to connect to wi-fi networks where a sign-in is required. "Harden several aspects of our Linux kernel. Disable HTTPS-only mode in the Unsafe Browser to make it easier to sign in to Wi-Fi networks. Update Tor Browser to 11.5.2. Update tor to 0.4.7.10. Update the Linux kernel to 5.10.136. This should improve the support for newer hardware: graphics, Wi-Fi, and so on. It will also fix an important vulnerability. For more details, read our changelog." Additional information can be found in the project's release announcement.
* * * * *
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,762
- Total data uploaded: 42.4TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
Do you run an immutable operating system?
This week we talked about immutable operating systems in our Questions and Answers column. An immutable operating system can provide a number of benefits when it comes to security, stability, and testing. To date most immutable systems have been used on mobile devices and container servers, but they are slowly expanding to more servers and desktop systems. Do you currently run an immutable operating system on your laptop or desktop computer? If you are, let us know which one in the comments.
You can see the results of our previous poll on getting notifications about security updates in last week's edition. All previous poll results can be found in our poll archives.
|
Running immutable operating systems
| I run an immutable system on my laptop/workstation: | 60 (4%) |
| I run an immutable system on my phone: | 155 (10%) |
| I run an immutable system on both: | 18 (1%) |
| I do not run any immutable systems: | 1163 (76%) |
| I do not know if my systems are immutable: | 129 (8%) |
|
|
| Website News |
Donations and Sponsors
Each month we receive support and kindness from our readers in the forms of donations. These donations help us keep the web server running, pay contributors, and keep infrastructure like our torrent seed box running. We'd like to thank our generous readers and acknowledge how much their contributions mean to us.
This month we're grateful for the $1,514 in contributions from the following kind souls:
| Donor |
Amount |
|---|
| Anonymous | $1426 |
| Edgar C | $23 |
| Brian K | $11 |
| Kevin W | $10 |
| Sam C | $10 |
| Eric G | $9 |
| Adiel A | $5 |
| Chung T | $5 |
| DuCakedHare | $5 |
| Matt | $5 |
| J.D. L | $2 |
| PB C | $2 |
| Stephen M | $1 |
* * * * *
New distributions added to waiting list
- Metis Linux. Metis Linux is a fork of Artix Linux which strives to be more minimal and resource efficient.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 5 September 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)
|
|
| Tip Jar |
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 1, value: US$15.20) |
|
|
|
 bc1qtede6f7adcce4kjpgx0e5j68wwgtdxrek2qvc4  lnurl1dp68gurn8ghj7ampd3kx2ar0veekzar0wd5xjtnrdakj7tnhv4kxctttdehhwm30d3h82unvwqhhxarpw3jkc7tzw4ex6cfexyfua2nr  86fA3qPTeQtNb2k1vLwEQaAp3XxkvvvXt69gSG5LGunXXikK9koPWZaRQgfFPBPWhMgXjPjccy9LA9xRFchPWQAnPvxh5Le paypal.me/distrowatchweekly • patreon.com/distrowatch |
|
| Linux Foundation Training |
|
|
| 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 1046 (2023-11-20): Slackel 7.7 "Openbox", restricting CPU usage, Haiku improves font handling and software centre performance, Canonical launches MicroCloud |
| • Issue 1045 (2023-11-13): Fedora 39, how to trust software packages, ReactOS booting with UEFI, elementary OS plans to default to Wayland, Mir gaining ability to split work across video cards |
| • Issue 1044 (2023-11-06): Porteus 5.01, disabling IPv6, applications unique to a Linux distro, Linux merges bcachefs, OpenELA makes source packages available |
| • Issue 1043 (2023-10-30): Murena Two with privacy switches, where old files go when packages are updated, UBports on Volla phones, Mint testing Cinnamon on Wayland, Peppermint releases ARM build |
| • Issue 1042 (2023-10-23): Ubuntu Cinnamon compared with Linux Mint, extending battery life on Linux, Debian resumes /usr merge, Canonical publishes fixed install media |
| • Issue 1041 (2023-10-16): FydeOS 17.0, Dr.Parted 23.09, changing UIDs, Fedora partners with Slimbook, GNOME phasing out X11 sessions, Ubuntu revokes 23.10 install media |
| • Issue 1040 (2023-10-09): CROWZ 5.0, changing the location of default directories, Linux Mint updates its Edge edition, Murena crowdfunding new privacy phone, Debian publishes new install media |
| • Issue 1039 (2023-10-02): Zenwalk Current, finding the duration of media files, Peppermint OS tries out new edition, COSMIC gains new features, Canonical reports on security incident in Snap store |
| • Issue 1038 (2023-09-25): Mageia 9, trouble-shooting launchers, running desktop Linux in the cloud, New documentation for Nix, Linux phasing out ReiserFS, GNU celebrates 40 years |
| • Issue 1037 (2023-09-18): Bodhi Linux 7.0.0, finding specific distros and unified package managemnt, Zevenet replaced by two new forks, openSUSE introduces Slowroll branch, Fedora considering dropping Plasma X11 session |
| • Issue 1036 (2023-09-11): SDesk 2023.08.12, hiding command line passwords, openSUSE shares contributor survery results, Ubuntu plans seamless disk encryption, GNOME 45 to break extension compatibility |
| • Issue 1035 (2023-09-04): Debian GNU/Hurd 2023, PCLinuxOS 2023.07, do home users need a firewall, AlmaLinux introduces new repositories, Rocky Linux commits to RHEL compatibility, NetBSD machine runs unattended for nine years, Armbian runs wallpaper contest |
| • Issue 1034 (2023-08-28): Void 20230628, types of memory usage, FreeBSD receives port of Linux NVIDIA driver, Fedora plans improved theme handling for Qt applications, Canonical's plans for Ubuntu |
| • Issue 1033 (2023-08-21): MiniOS 20230606, system user accounts, how Red Hat clones are moving forward, Haiku improves WINE performance, Debian turns 30 |
| • Issue 1032 (2023-08-14): MX Linux 23, positioning new windows on the desktop, Linux Containers adopts LXD fork, Oracle, SUSE, and CIQ form OpenELA |
| • Issue 1031 (2023-08-07): Peppermint OS 2023-07-01, preventing a file from being changed, Asahi Linux partners with Fedora, Linux Mint plans new releases |
| • Issue 1030 (2023-07-31): Solus 4.4, Linux Mint 21.2, Debian introduces RISC-V support, Ubuntu patches custom kernel bugs, FreeBSD imports OpenSSL 3 |
| • Issue 1029 (2023-07-24): Running Murena on the Fairphone 4, Flatpak vs Snap sandboxing technologies, Redox OS plans to borrow Linux drivers to expand hardware support, Debian updates Bookworm media |
| • Issue 1028 (2023-07-17): KDE Connect; Oracle, SUSE, and AlmaLinux repsond to Red Hat's source code policy change, KaOS issues media fix, Slackware turns 30; security and immutable distributions |
| • Issue 1027 (2023-07-10): Crystal Linux 2023-03-16, StartOS (embassyOS 0.3.4.2), changing options on a mounted filesystem, Murena launches Fairphone 4 in North America, Fedora debates telemetry for desktop team |
| • Issue 1026 (2023-07-03): Kumander Linux 1.0, Red Hat changing its approach to sharing source code, TrueNAS offers SMB Multichannel, Zorin OS introduces upgrade utility |
| • Issue 1025 (2023-06-26): KaOS with Plasma 6, information which can leak from desktop environments, Red Hat closes door on sharing RHEL source code, SUSE introduces new security features |
| • Issue 1024 (2023-06-19): Debian 12, a safer way to use dd, Debian releases GNU/Hurd 2023, Ubuntu 22.10 nears its end of life, FreeBSD turns 30 |
| • Issue 1023 (2023-06-12): openSUSE 15.5 Leap, the differences between independent distributions, openSUSE lengthens Leap life, Murena offers new phone for North America |
| • Issue 1022 (2023-06-05): GetFreeOS 2023.05.01, Slint 15.0-3, Liya N4Si, cleaning up crowded directories, Ubuntu plans Snap-based variant, Red Hat dropping LireOffice RPM packages |
| • Issue 1021 (2023-05-29): rlxos GNU/Linux, colours in command line output, an overview of Void's unique features, how to use awk, Microsoft publishes a Linux distro |
| • Issue 1020 (2023-05-22): UBports 20.04, finding another machine's IP address, finding distros with a specific kernel, Debian prepares for Bookworm |
| • Issue 1019 (2023-05-15): Rhino Linux (Beta), checking which applications reply on a package, NethServer reborn, System76 improving application responsiveness |
| • Issue 1018 (2023-05-08): Fedora 38, finding relevant manual pages, merging audio files, Fedora plans new immutable edition, Mint works to fix Secure Boot issues |
| • Issue 1017 (2023-05-01): Xubuntu 23.04, Debian elects Project Leaders and updates media, systemd to speed up restarts, Guix System offering ground-up source builds, where package managers install files |
| • Issue 1016 (2023-04-24): Qubes OS 4.1.2, tracking bandwidth usage, Solus resuming development, FreeBSD publishes status report, KaOS offers preview of Plasma 6 |
| • Issue 1015 (2023-04-17): Manjaro Linux 22.0, Trisquel GNU/Linux 11.0, Arch Linux powering PINE64 tablets, Ubuntu offering live patching on HWE kernels, gaining compression on ex4 |
| • Issue 1014 (2023-04-10): Quick looks at carbonOS, LibreELEC, and Kodi, Mint polishes themes, Fedora rolls out more encryption plans, elementary OS improves sideloading experience |
| • Issue 1013 (2023-04-03): Alpine Linux 3.17.2, printing manual pages, Ubuntu Cinnamon becomes official flavour, Endeavour OS plans for new installer, HardenedBSD plans for outage |
| • Issue 1012 (2023-03-27): siduction 22.1.1, protecting privacy from proprietary applications, GNOME team shares new features, Canonical updates Ubuntu 20.04, politics and the Linux kernel |
| • Issue 1011 (2023-03-20): Serpent OS, Security Onion 2.3, Gentoo Live, replacing the scp utility, openSUSE sees surge in downloads, Debian runs elction with one candidate |
| • Issue 1010 (2023-03-13): blendOS 2023.01.26, keeping track of which files a package installs, improved network widget coming to elementary OS, Vanilla OS changes its base distro |
| • Issue 1009 (2023-03-06): Nemo Mobile and the PinePhone, matching the performance of one distro on another, Linux Mint adds performance boosts and security, custom Ubuntu and Debian builds through Cubic |
| • Issue 1008 (2023-02-27): elementary OS 7.0, the benefits of boot environments, Purism offers lapdock for Librem 5, Ubuntu community flavours directed to drop Flatpak support for Snap |
| • Issue 1007 (2023-02-20): helloSystem 0.8.0, underrated distributions, Solus team working to repair their website, SUSE testing Micro edition, Canonical publishes real-time edition of Ubuntu 22.04 |
| • Issue 1006 (2023-02-13): Playing music with UBports on a PinePhone, quick command line and shell scripting questions, Fedora expands third-party software support, Vanilla OS adds Nix package support |
| • Issue 1005 (2023-02-06): NuTyX 22.12.0 running CDE, user identification numbers, Pop!_OS shares COSMIC progress, Mint makes keyboard and mouse options more accessible |
| • Issue 1004 (2023-01-30): OpenMandriva ROME, checking the health of a disk, Debian adopting OpenSnitch, FreeBSD publishes status report |
| • Issue 1003 (2023-01-23): risiOS 37, mixing package types, Fedora seeks installer feedback, Sparky offers easier persistence with USB writer |
| • Issue 1002 (2023-01-16): Vanilla OS 22.10, Nobara Project 37, verifying torrent downloads, Haiku improvements, HAMMER2 being ports to NetBSD |
| • Issue 1001 (2023-01-09): Arch Linux, Ubuntu tests new system installer, porting KDE software to OpenBSD, verifying files copied properly |
| • Issue 1000 (2023-01-02): Our favourite projects of all time, Fedora trying out unified kernel images and trying to speed up shutdowns, Slackware tests new kernel, detecting what is taking up disk space |
| • Issue 999 (2022-12-19): Favourite distributions of 2022, Fedora plans Budgie spin, UBports releasing security patches for 16.04, Haiku working on new ports |
| • Issue 998 (2022-12-12): OpenBSD 7.2, Asahi Linux enages video hardware acceleration on Apple ARM computers, Manjaro drops proprietary codecs from Mesa package |
| • Issue 997 (2022-12-05): CachyOS 221023 and AgarimOS, working with filenames which contain special characters, elementary OS team fixes delta updates, new features coming to Xfce |
| • Issue 996 (2022-11-28): Void 20221001, remotely shutting down a machine, complex aliases, Fedora tests new web-based installer, Refox OS running on real hardware |
| • Issue 995 (2022-11-21): Fedora 37, swap files vs swap partitions, Unity running on Arch, UBports seeks testers, Murena adds support for more devices |
| • Issue 994 (2022-11-14): Redcore Linux 2201, changing the terminal font size, Fedora plans Phosh spin, openSUSE publishes on-line manual pages, disabling Snap auto-updates |
| • Issue 993 (2022-11-07): Static Linux, working with just a kernel, Mint streamlines Flatpak management, updates coming to elementary OS |
| • 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.
|
| Shells.com |
Your own personal Linux computer in the cloud, available on any device. Supported operating systems include Android, Debian, Fedora, KDE neon, Kubuntu, Linux Mint, Manjaro and Ubuntu, ready in minutes.
Starting at US$4.95 per month, 7-day money-back guarantee
|
| Random Distribution | 
Karamad Linux
Karamad was an openSUSE-based Iranian distribution. With support for the Persian language and other enhancements depicting Iran's history and culture, the distribution was designed for Iranian users and those interested in the language, history and culture of ancient Persia.
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.
|
|
• 
• 
• 
• 
• 
• 
• 
