 DistroWatch Weekly |
| DistroWatch Weekly, Issue 938, 11 October 2021 |
Welcome to this year's 40th issue of DistroWatch Weekly!
Sometimes people come along and share ideas which seem completely strange. Maybe they want to decorate their home with pennies or construct a boat entirely from toothpicks. This week we begin with a look at the unusual Pyabr project. Pyabr seeks to build an operating system, including a desktop environment, almost entirely from Python code. Read on to learn how this curious experiment is progressing. In our News section we share efforts to make an alternative to the Snap portable package client which can pull in packages from third-party repositories. What do you think of a version of Snap that is not tied to Canonical? Let us know in this week's Opinion Poll. We also share a workaround from Redcore for a recent issue that corrupts the Portage software manager while Debian publishes updated install media. Plus we share new improvements coming to the elementary OS distribution, particularly the project's software centre. In our Questions and Answers column we explore whether compiling your own kernel from source carries any benefit or performance improvements. Do you compile your own kernel builds in order to gain improved performance or hardware support? Let us know about your customizations in the comments section. Plus we are pleased to share this week's releases and list the torrents we are seeding. We wish you all a fantastic week and happy reading!
Content:
- Review: Pyabr OS
- News: Alternative Snap implementation, Redcore provides a solution for Portage issue, elementary OS outlines software centre improvements, Debian publishes install media updates
- Questions and answers: Benefits to building your own kernel
- Released last week: IPFire 2.27 Core 160, Feren OS 2021.10
- Torrent corner: EasyOS, ExTiX, Feren OS, IPFire, KDE neon, Manjaro, PureOS, Snal, Tails
- Upcoming releases: Ubuntu 21.10
- Opinion poll: Would you use Snap if it connected to a community repository?
- Site news: Refreshing package download links
- Reader comments
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (18MB) and MP3 (14MB) formats.
|
| Feature Story (by Jesse Smith) |
Pyabr OS
Pyabr OS was one of the latest distributions to be added to the DistroWatch waiting list. The project refers to itself as a "Python Cloud Operating System", a Linux distribution mostly written in Python. The project, which declares it is developed in Iran with multilingual support, runs on x86_64 computers and 64-bit Raspberry Pi machines.
The project's website mentions that Pyabr is a platform written in Python which offers a desktop and applications which can be run on any Linux distribution while Pyabr OS is a Debian-based operating system that runs the Pyabr software. The operating system can reportedly be installed locally or run from live media like a thumb drive. The desktop environment resembles KDE Plasma but is a custom environment called Baran which the project says is written in Python using the Qt framework.
I was unsure going into this trial how all of this related to cloud computing or services. The term "cloud" gets thrown around on the project's website, but without a clear indication of how this affects the end user. I decided to give the project a test drive and see if I could find out.
The Pyabr OS ISO file is a small download of just 447MB. The live system always stalled early in the boot process for 90 seconds while waiting for systemd to sort out its infamous "A start job is running..." warning. After that, the distribution booted quickly and displayed the Baran desktop which does look a lot like KDE Plasma at first glance due to its shared Qt framework and theme.
Early impressions
The desktop environment uses a two-panel layout. A thin panel is placed at the top of the screen. It contains an application menu and a system menu to the left and a system tray to the right. The bottom panel is thicker and also includes an application menu to the left. Icons for launching applications are arrayed along the bottom panel.
One of the first things I noticed about Pyabr is that it consumes all available CPU, even when sitting idle at the desktop. I intended to find out why and so opened a terminal and tried to run commands like top, ps, and free which I hoped would shine light on what was running in the background. None of these commands exist on Pyabr OS. The man command and many other common command line programs are also missing. The ls command works, but does not recognize any command line flags ("ls" works, but "ls -l" does not). In other words there are virtually no useful Unix-like command line programs available to help do work or troubleshoot issues.
Pyabr OS -- Trying to run common command line programs
(full image size: 109kB, resolution: 1320x691 pixels)
Next I opened the distribution's process monitor. This tool lists desktop applications which are currently open and which have been opened in the past. I'm not sure if this indicates process information is not cleared periodically or if closed application windows are not truly terminated when they disappear. No CPU or memory usage is displayed in the process monitor, making it difficult to determine what was consuming all available CPU resources.
Installing
When the live desktop session first loads, a welcome window appears. This window offers to start the install process. The installer is graphical and started off well enough with clear invitations to make up a username and password. We are asked to pick our preferred language with options being English or (I believe) Farsi. We are given the chance to toggle a guest account on/off. The installer asked if we'd like to provide a name, e-mail address, and phone number. This last step is unusual and the reason for asking for this information is not given.
Pyabr OS -- Being greeted by the system installer
(full image size: 172kB, resolution: 1320x691 pixels)
The installer has a few inconvenient quirks. For example, pressing the Tab key usually moves focus back to the previous field on a screen rather than the next. Other times it seems to select a random location. This makes navigating the interface more awkward. A bigger issue is that when the installer closes, it immediately shuts down the operating system. This means if we close the window or click the Cancel button at any point, the system powers off. To make matters worse, completing all the install steps causes the installer to immediately terminate which, in turn, shuts off the computer. I ran through the installer's steps four times and, each time, upon reaching the final screen the installer shut down and took the rest of the system down with it.
In short, I was only able to use Pyabr OS when it was running from live media and the system installer window always had to be open in the background or the system would immediately power off.
Included applications
Pyabr OS ships with a small collection of applications, though most of them appear to be custom, trimmed down versions of popular programs. We are given tools like a calculator, calendar, and file browser, but the tools are quite simple. The file browser just lists present folders and files and seems to be view-only in its capabilities. The calendar likewise shows dates, but doesn't seem to be able to set appointments or sync with on-line services. There is a custom web browser that does a few things differently. The main buttons and address bar are placed at the bottom of the browser window. Entering an address in the bar, such as linux.com or distrowatch.com, triggers a search and shows us web search results rather than the site we asked for. This makes it impossible to directly visit a specific URL by typing or pasting an address into the browser.
Pyabr OS -- The settings panel
(full image size: 111kB, resolution: 1320x691 pixels)
The distribution has a settings panel which presents us with a handful of custom configuration modules. There tools to help us manage user accounts, connect to local wireless networks, change the system's screen resolution, and adjust the theme of the desktop. Adjusting either the desktop resolution or theme requires restarting the system for the changes to take effect.
Software management
There is a package manager included with Pyabr. This program shows all installed desktop applications in one tab and a list of available programs in a second tab. There are just two applications in the list of available applications: Bale and Shad. Both of these programs are described simply as being messaging applications. There doesn't appear to be any way to get software updates for the base system or desktop applications.
Pyabr OS -- The software manager
(full image size: 122kB, resolution: 1320x691 pixels)
Hardware
When I started my trial I was running Pyabr OS in a VirtualBox machine. The system, despite consuming all available CPU resources, was snappy and pleasantly quick to respond. New programs opened quickly enough I suspect the entire Pyabr software suite runs from RAM. The desktop was able to automatically resize to match the VirtualBox window, which was appreciated.
I was unable to check how much memory the distribution was using or what its underlying core software was, given the limited tools provided. However, having seen the systemd warning message at each boot and knowing the distribution is based on Debian 10, I think it's a fair guess to say systemd init and Linux 4.19 are probably being used.
Later in the week I tried to run Pyabr OS on my laptop, but was unable to get the operating system to boot in either Legacy BIOS or UEFI modes. This limited my trial to running Pyabr OS in a virtual machine.
Conclusions
When I first began exploring Pyabr OS the project made me think of snakeware, but with a stronger focus on desktop and web applications. Both projects rely heavily on Python to replace the userland programs and seem to seek to remake existing popular programs with Python code.
Replacing popular programs and desktop environments with Python is certainly an interesting concept and one which I'm sure presents some interesting challenges. It may even offer us some interesting solutions too, in the long run.
The trouble though with crafting an operating system where all the popular applications, command line programs, and desktop elements are replaced by new, experimental ones is that almost all the expected functionality is missing. Most modern Linux distributions have solved (or mostly solved) many of the complex problems of computing - booting on a range of hardware, installing the operating system, packaging a web browser, providing useful command line tools, shipping full featured desktop environments, office suites, and web browsers. Projects like Pyabr OS are throwing away all of those working tools, familiarity, and a supported ecosystem of software for alternatives that often don't work, or don't work well.
They have an installer that not only doesn't work, but cannot be closed, most command line tools are missing, hardware support is lacking, the system crashed about 10% of the time while I was exploring settings or the package manager. Many of the included tools certainly worked (and my hat is off to the people who built them), but the tools usually didn't offer the same functionality as corresponding utilities included with other desktop environments.
In short, Pyabr OS is an interesting concept - a desktop operating system running almost exclusively Python code, but I'm not sure it has any useful purpose. It doesn't do anything out of the grasp of other Linux distributions and frequently lacks functionality and stability offered by other Debian-based projects.
* * * * *
Hardware used in this review
My physical test equipment for this review was a de-branded HP laptop with the following
specifications:
- Processor: Intel i3 2.5GHz CPU
- Display: Intel integrated video
- Storage: Western Digital 700GB hard drive
- Memory: 6GB of RAM
- Wired network device: Realtek RTL8101E/RTL8102E PCI Express Fast
- Wireless network device: Realtek RTL8188EE Wireless network card
|
| Miscellaneous News (by Jesse Smith) |
Alternative Snap implementation, Redcore provides a solution for Portage issue, elementary OS outlines software centre improvements, Debian publishes install media updates
Canonical, the company behind the Ubuntu distribution, is also the developer of the Snap package format, along with the Snap command line client and official Snap repository. To date, Canonical has insisted on hard-coding the Snap client software to work only with Canonical's own, curated repository of Snap packages. This has put Snap in contrast with the portable Flatpak framework, which works with a variety of third-party repositories. A new project called lol has been created which provides an alternative client for Snap which can work with specified repositories. This could provide people who like using the portable Snap packages with the opportunity to acquire software from Snap repositories other than Canonical's.
* * * * *
The Redcore Linux project has shined a spotlight on a serious package management issue that has surfaced in Gentoo. The issue stems from corruption in the Portage software manager's database which can, in some cases, cause an upgrade to break the operating system. "We have observed in some cases corruption of Portage's internal database (VDB), where the libraries provided by a package are not recorded. This can break the "preserve-libs" functionality, and thus in rare cases break your system during much later updates (even if you do not use 'preserved-libs' now, but decide to switch it on later). The underlying problem occurs usually when glibc has been upgraded to a new major version, but pax-utils has not yet been upgraded to a version compatible with it (but at that moment stays undetected). The full technical details and investigation can be found on a wiki page and on Bugzilla." The Redcore blog post goes on to explain how to address the Portage bug.
* * * * *
The elementary OS team have published a project update which outlines the work they are doing to improve the software centre and desktop experience. Some of the changes to elementary's software centre include improved performance and presenting security and privacy information on an application's summary page. "For example, we've largely reworked the home page with banners featuring the most recently released and updated curated apps in a multi-touch swipable carousel. We've also added up to twelve more of the most recently-updated apps directly below. Rather than just showing the app's icon and name, we now also show each app's summary and an install button - including the developer's recommended price if it's a monetized app. Since we enforce accurate update information for curated apps, this data is populated locally from the apps' AppStream data rather than from a remote API as before. The result of this work is a faster home page with over three times the apps displayed, as well as the ability to purchase or install several apps with far fewer clicks. The categories remain below if you prefer that route for browsing. We've also spent significant time improving individual apps' info pages. Rather than displaying a generic 'explicit' warning dialog when installing an app with certain content warnings, we show this information ahead of time at the top of the page. We differentiate between and inform about several content warnings including things like violence, language, and nudity as well as privacy-related topics like online interactions and data collection."
* * * * *
The Debian project has published updated media for its Stable and Old Stable branches. Versions 10 and 11 of Debian now have refreshed media which includes security updates published since those respective versions were originally launched. "The Debian project is pleased to announce the first update of its stable distribution Debian 11 (codename Bullseye). This point release mainly adds corrections for security issues, along with a few adjustments for serious problems. Security advisories have already been published separately and are referenced where available. Please note that the point release does not constitute a new version of Debian 11 but only updates some of the packages included."
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
Benefits to building your own kernel
Tweaking-performance asks: When you install a distro it comes with its own kernel that supports lots of hardware. Would you gain any benefit to building your own kernel with just the drivers you need? Will compiling the kernel give you any performance advantage?
DistroWatch answers: You are correct that Linux distributions ship kernels that support a wide range of hardware. Usually the kernel shipped with a distribution will include as much common hardware support as possible and will be built for the lowest-end processors supported by a given architecture. For instance, an x86_64 build of the kernel will typically run on i3, i5, i7, etc CPUs rather than being optimized for one specific CPU.
Will building your own kernel with support for just your hardware offer a performance boost? It can, in some ways. Compiling a kernel for your specific CPU will allow the kernel to make use of instructions or features of the CPU to run a little more efficiently. The benefits of this will be small, but may be noticeable under heavy workloads. Day to day you probably won't notice a difference because most desktop and server computers spend a lot of their time idle anyway, so you're only likely to see the benefits of a performance boost when doing large batch jobs or gaming. The kernel may also end up being a little smaller in memory, though probably not enough for you to notice a difference.
The biggest change will probably be the amount of disk space consumed by the kernel modules. Most driver support built into Linux is stored in modules which are only loaded into memory when needed. This means your distribution's generic kernel ships with a big group of modules that usually just sit on the disk and never get used. How much space do these modules take up? It will vary from one system to another, but on one distribution I checked this week the modules took up about 250MB of disk space. Most of these will never be loaded into memory and so won't affect performance or memory consumption, but they do consume a bit of disk which could be avoided if I'd compiled my own kernel.
In short, you can get small improvements in kernel performance by building your own. You probably won't see a big difference, maybe just a few percentage points in gain, in most situations, but you can squeeze a little more performance from a custom kernel.
Most people don't compile their own kernels because it's a relatively long process that involves some technical knowledge and offers minor benefits. Usually you'll gain more of a boost by disabling unneeded background services, running a lighter desktop environment, or preloading applications you use regularly into RAM. These will be easier tasks which should offer larger performance gains. However, if you've done those already and still want to explore building your own kernel (for fun and performance perks) you can follow this tutorial on Linux.com which explains the steps.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
IPFire 2.27 Core 160
IPFire is a Linux distribution that focuses on easy setup, good handling and high level of security, intended for use in firewalls and routers. The project has published a new update which focuses on improving network throughput. "In recent days and months, the development team has spent a lot of time on finding bottlenecks and removing those. Our goal is to increase throughput on hardware and bringing latency down, for a faster network. This update brings a first change which will enable network interfaces that support it, to send packets that belong to the same stream to the same processor core. This allows taking advantage of better cache locality and the firewall engine as well as the Intrusion Prevention System benefit from this, especially with a large number of connections and especially on hardware with smaller CPU caches." The IPFire team is also continuing their work to remove Python 2 from their distribution. Additional information is provided in the project's release announcement.
Feren OS 2021.10
Feren OS is a desktop Linux distribution based on Ubuntu and featuring the KDE Plasma desktop. The project's latest snapshot is Feren OS 2021.10 which includes a new lock screen, new splash screen, and a customized Firefox experience. "The once scrapped configuration for Firefox has now made its way, now repurposed and improved for normal browser usage, into Firefox in Feren OS, both via a new package called firefox-config-feren, and an update to Web Browser Manager that now pre-installs this configuration of Firefox alongside the browser itself, effective starting Feren OS 2021.10. Enjoy Mozilla Firefox, now with: Compact Mode and no titlebar by default. None of that Stories stuff in New Tab (and other New Tab distractions). No Pocket by default. Library being in the toolbar (as was intended by Mozilla themselves during early Proton design ideas) instead of Pocket's button. Most, if not all, the Telemetry values being off, including the ones you can't change via Settings. Home button in the toolbar by default. Skipped Welcome Screens to allow you to get right into the action.... Additional information is provided in the project's release announcement.
Feren OS 2021.10 -- Running the KDE Plasma desktop
(full image size: 2.1MB, resolution: 1920x1080 pixels)
Redo Rescue 4.0.0
Zebradots Software has announced the release of Redo Rescue 4.0.0, a major update of the project's specialist distribution for bare metal backups and system restoration tasks. Although the version number does not indicate it, the release is considered beta quality software, the first build based on Debian 11 "Bullseye": "This is a beta release based on Debian 11. For this major upgrade, the only change applied is the base operating system and any package requirements required to complete the migration to Debian 'Bullseye'. The underlying application and all functionality remains identical to the last release (3.0.2). Please note that newer packages, particularly Partclone or sfdisk, may contain breaking changes we are not aware of. Many (if not most) of the issues reported with the 3.0 releases were focused on the Debian 10's lack of support in the kernel for more recent hardware, which shows a login prompt instead of the GUI. We are hoping this release based on Debian 11 will fix these issues for the majority of users. Here is the brief release announcement as published on the project's GitHub page.
* * * * *
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,621
- Total data uploaded: 40.4TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
Would you use Snap if it connected to a community repository?
In our News section this week we shared a report that an alternative version of the Snap software is being developed which allows users to pull from Snap package repositories other than the one controlled by Canonical. To date, Canonical has set up the Snap client to pull packages from only their own, proprietary Snap server with its curated repository. For years the Linux community has been lobbying for the ability to set up third-party repositories of Snap packages and it looks like the lol software will finally allow this to happen.
Now that it should be possible to set up community repositories for Snap packages, does this change your view of Snap? Are you more likely to adopt Snap packages if multiple repositories become available?
You can see the results of our previous poll on using multi-machine management tools such as Ansible in last week's edition. All previous poll results can be found in our poll archives.
|
Are you more likely to use Snap now that third-party repositories are possible?
| Are you more likely to use Snap now that third-party repositories are possible?|I already use Snap: | 227 (12%) |
| I did not use Snap but will now: | 67 (3%) |
| I will continue to avoid Snap: | 1341 (69%) |
| Undecided: | 322 (16%) |
|
|
| Website News |
Refreshing package download links
One of our long-running features is the DistroWatch Tracked Packages Collection. We maintain a list of 226 popular utilities, desktop environments, compilers, and desktop applications. These 226 packages are tracked across each Linux distribution and we publish links to the latest stable versions of these packages on our front page when new releases become available.
We believe this list of software is helpful, not only to people looking to discover some of the more powerful programs Linux has to offer, but also to help people keep abreast of changes to their favourite applications.
Twenty years ago, back when we first started tracking these packages and publishing links to the latest source code on our front page, the FTP protocol was still one of the more popular (and reliable) ways to transfer files across the Internet. Over the years FTP has gradually fallen out of favour and most projects these days publish web links using the HTTP protocol. Still, the old FTP links continued to work and so they were left in place.
This past year some of the larger browsers - such as Firefox, Chrome, and Brave - have announced plans to remove support for the FTP protocol. In short, this meant that the FTP links on our Packages page would no longer work in those browsers. In order to change with the times, we have gone through our Packages database and upgraded the lingering FTP links to use the newer HTTP (or HTTPS where available) protocols.
There are still five projects which insist on using FTP exclusively and/or do not provide direct links to source packages over the newer protocols. In these cases we have had to keep the old FTP links which should still work with file transfer clients such as FileZilla. In a few instances projects do provide HTTP download options, just not direct URLs. Visiting main website of a project which still uses FTP will sometimes provide alternative HTTP downloads through redirects which will work in the modern versions of mainstream web browsers.
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 18 October 2021. 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 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 | 
Swift Linux
Swift Linux is a lightweight, MX Linux-based distribution featuring the Xfce desktop environment. While Swift previously included forensic analysis and data recovery utilities, since version 16 the distribution has presented itself as MX Linux with alternative wallpaper.
Status: Dormant
|
| 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.
|
|
• 
• 
• 
• 
• 
• 
• 
