 DistroWatch Weekly |
| DistroWatch Weekly, Issue 937, 4 October 2021 |
|
Welcome to this year's 39th issue of DistroWatch Weekly!
Computers are great at automating tasks. Doing something quickly over and over again the same way is where computers really shine. However, any system administrator can tell you that some tasks become more difficult when they are spread out over multiple machines. Installing the same software on multiple computers and keeping a fleet of machines up to date can be tedious. Fortunately there are tools like Ansible which will help run the same commands across multiple machines. In this week's Feature Story Bruce Patterson talks about Ansible and how to get it set up in order to control multiple machines. This can be useful in an office or even on a small home network where you don't want to manually keep each machine in sync with the others. Do you use Ansible or another multi-machine management utility? Let us know about it in our Opinion Poll. In our News section we talk about portable packages, such as Flatpak and Snap, and share a case against using these increasingly popular package formats. We also share an overview of Btrfs from Ars Technica which points out some issues with the advanced filesystem. Meanwhile some open source projects, such as Void and DragonFly BSD, are facing problems with their package managers and we explain why. Then, in our Questions and Answers column, we talk about the Wayland display technology and how to clean out old history files from the command line. 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:
- Review: Getting started with Ansible
- News: A case against portable packages, diving into the status of Btrfs, multiple projects fixing certificate issues
- Questions and answers: Wayland and clearing up history
- Released last week: Q4OS 4.6
- Torrent corner: 4MLinux, Bluestar, GhostBSD, KDE neon, Linux Kodachi, Nitrux, Q4OS, SystemRescue, Thinstation
- Upcoming releases: Tails 4.23
- Opinion poll: Ansible and other computer management tools
- New additions: LockBox
- Reader comments
Listen to the Podcast edition of this week's DistroWatch Weekly in OGG (12MB) and MP3 (9MB) formats.
|
| Feature Story (by Bruce Patterson) |
Getting started with Ansible
Ansible is a Red Hat owned tool for automating system administration tasks. It is typically used in environments where an administrator wants to perform the same task, such as deploying security updates, on many computers without logging into each computer manually. Unlike many automation tools, Ansible does not require any special software to be installed on each client machine. Each client just needs the OpenSSH service to be installed on the clients and all the work and configuration is handled by one central server.
There are a lot of reasons for working with Ansible and this guide is meant to get you up and running quickly. If you're like me, I have a terrible habit of not reading the fine manual. To quote the Simpsons character Renier Wolfcastle, "I was elected to lead not to read". To follow along with this tutorial here are the basics you will need:
- Enough RAM and disk space for your virtual machines.
- Virtual apps such as VirtualBox, VMware, KVM or whatever your preference.
- Minimum number of required VMs are two, one as the primary where all the scripts/playbooks are kept and a secondary machine that will receive the changes pushed from the primary machine.
For this example I am using VirtualBox and Rocky Linux as my operating system. You can set up Ansible with almost any operating systems you want. As my reasons for doing things in this example are due to my job, which will require me to update various Red Hat servers, I am sticking with a Red Hat clone.
Getting started
Before you do anything, you need to setup an environment to use Ansible. In VirtualBox I created a primary machine named Bullwinkle and four secondary machines named Rocky One, Rocky Two, etc. Naming is not important, you can name it whatever you want. Machine One, Bruins One, etc. Again, you only need one secondary machine, for this example I created four.
Note: I did not install desktops on any of these VMs, they were strictly command line only because it is rare that you will find servers with desktops. Also, without desktops the VMs have a much smaller resource footprint.
The quickest way to create multiple VMs: create the first one in VirtualBox and once you have created the VM and updated the operating system, you can clone the first one to as many machines as you want, just be sure to rename them with unique names. Once you have the VMs in place, you will have to make sure each one has a unique IP address because the first thing you will notice is they all have the same IP address. I used the following tutorial from our friends at Dedoimedo.
Installing
I used the following instructions from Linux Techie. The steps are below:
- On your primary machine log in and make sure the operating system is up to date. For me I used the command "sudo dnf update -y".
- If there are updates, reboot your machine.
- Install Python 3.8 and other dependencies with the following command:
"sudo dnf module -y install python38"
- Next you will run the following config command:
"sudo alternatives --config python"
- You will then be prompted to choose one of three options:
There are three programs which provide Python:
1. /usr/libexec/no-python
2. /usr/bin/python3
3. /usr/bin/python3.8
Please select number 3.
- Verify the version of Python installed, it should be Python 3.8
- Following the instructions I used pip to install Ansible. This next part will take roughly 3 to 5 minutes to run depending on your machine. I ran the following three commands separately:
sudo pip3 install setuptools-rust wheel
sudo pip3 install --upgrade pip
sudo python -m pip install ansible
At this point, I stopped here in the instructions because the next steps included generating an RSA secure key and pushing it to the secondary machines. I struggled through this section without any success.
Note: The creation of secure keys is a best practice and should not be overlooked, especially if you plan to execute this in production! I was working in a controlled environment at home and I skipped this part, but the work around is provided in the video below in the next paragraph.
Once Ansible is installed you need to create an inventory file and for this I went to the folks at Simplilearn - Ansible Tutorial For Beginners | What Is Ansible And How It Works? The demo begins at the 8 minute mark of the video.
Your Ansible directory is found at /etc/ansible/ and the following files should be found in this directory:
ansible.cfg
hosts
roles (a directory)
The hosts file should have been placed in the roles directory so if you are seeing this outside of the directory just move it to the correct location. The hosts file is where you will list your managed secondary machines. You will need to update this file to create a reference point for your playbook which will follow shortly. The default hosts file has three distinct examples (Ex 1: ungrouped hosts, Ex 2: web servers, Ex 3: db servers. As my example didn't fit the last two examples, I chose the first group and labeled it "ansible_clients" The sample of what this looks like is below. I have added two of my secondary machines as noted in the lines "#rocky one machine" and "#rocky two machine" and under each commented line you see the following:
#rocky one machine
10.0.2.15 ansible_ssh_user=root ansible_ssh_pass=rockyone
#rocky two machine
10.0.2.5 ansible_ssh_user=root ansible_ssh_pass=rockytwo
A sample Ansible hosts file
(full image size: 17kB, resolution: 569x537 pixels)
Now that the hosts file has been updated we'll create a playbook. A playbook is what will push down commands to your secondary machines. The playbooks are written in YAML and is very easy to write but spacing is important so note that in the screenshot. I wanted to create a playbook that updates my secondary machines with the latest updates and also to install the EPEL repository. Using the vi editor I created the following playbook: server_updates_all_playbook.yml. It makes sense to name the playbook with what you want to run. In this case as I want to push updates to all machines, the name server_updates_all makes sense to me. Remember when you save the file, be sure the file is a dot yml file (server_updates_all_playbook.yml) The example of this playbook is below:
Instructions for installing updates through Ansible
(full image size: 8kB, resolution: 597x477 pixels)
Now that your file is in place, you always want to test it to make sure it will run properly so you will need to run the following command using my playbook as the file to check:
ansible-playbook server_updates_all_playbook.yml -syntax-check
If there are any errors you will see it in the output.
If the file is fine you will see the following result in the command line:
Playbook: ansible-playbook server_updates_all_playbook.yml.
Now it's ready to run. From the command line put in the following command:
ansible-playbook server_updates_all_playbook.yml
The screenshot below shows a successful execution of the playbook. Please keep in mind the last line of output is important because if the playbook had failed you would get output letting you know where it failed.
Progress and status report from Ansible
(full image size: 11kB, resolution: 796x594 pixels)
That is it!
|
| Miscellaneous News (by Jesse Smith) |
A case against portable packages, diving into the status of Btrfs, multiple projects fixing certificate issues
Drew DeVault is perhaps best known for working on such software projects as sway, wlroots, and the Alpine Linux distribution. In an interesting blog post on software packaging, DeVault suggests portable packages and third-party repositories is not the best way to go. "There are hundreds of Linux distros and each does things differently - the package maintainers are the experts who save you the burden of learning how all of them work. Instead of cramming all of your files into /opt, they will carefully sort it into the right place, make sure all of your dependencies are sorted upon installation, and make the installation of your software a single command (or click) away. They also serve an important role as the user's advocate. If an update breaks a bunch of other packages, they'll be in the trenches dealing with it so that the users don't face the breakage themselves. They are also the first line of defense preventing the installation of malware on the user's system. Many sideloaded packages for Linux include telemetry spyware or adware from the upstream distributor, which is usually patched out by the distribution."
* * * * *
Btrfs is an advanced filesystem which allows for multi-device storage, snapshots, and boot environments. It is a powerful technology that is now the default filesystem for openSUSE and Fedora. However, despite its many capabilities, Btrfs has been criticised over the years for its reliability issues, especially when compared next to ZFS. Ars Technica has published an article which explores some of the lingering issues with Btrfs. "Although Btrfs wiki users have repeatedly struggled to soften [the] warnings - saying it should be fine for data, although not metadata, assuming you explicitly scrub after any power outage or other unclean shutdown - senior Btrfs dev and maintainer Josef Bacik wrote a much stronger warning in btrfs-progs. SUSE maintainer David Sterba merged Bacik's warning in March: 'RAID5/6 support has known problems is strongly discouraged to be used besides testing or evaluation (sic).' When a filesystem's own senior developers and maintainers tell you not to use a feature, please do not use that feature."
* * * * *
Let's Encrypt is an organization which provides free security certificates for servers and websites. Let's Encrypt provides tools to automate the installation and renewal of globally recognized certificates which is, in large part, responsible for the explosion of secure HTTPS connections becoming available for most websites in recent years. One of the Let's Encrypt root certificates expired this past week which blocks some security certificates from being recognized, especially by older networking programs and web browsers. This has affected some open source package managers with DragonFly BSD and Void users reporting their package manager no longer works due to the expired certificate. Antonio Huete Jiménez wrote for DragonFly BSD: "As you may be already aware, a Let's Encrypt root CA certificate expired today. That is causing problems with our base LibreSSL but not with the DPorts one, we don't know why yet."
* * * * *
These and other news stories can be found on our Headlines page.
|
| Questions and Answers (by Jesse Smith) |
Wayland and clearing up history
Moving-forward asks: I've been hearing a lot about Wayland and how it's going to be great for the Linux desktop. What's the practical benefit for non-techies like me?
DistroWatch answers: For most of the past 40 years, Linux and UNIX-like operating systems (including the BSDs) have used a technology called X to display the desktop. The X display software was quite an amazing piece of technology for its time. In particular, it was really good at being network transparent. Which basically means you could run your desktop applications on one computer (like a central server) and have them show up on another computer. This was especially useful in computer labs and education centres. Since X could also run and display applications on the same machine it was practical in a lot of environments and became the default for most UNIX-like operating systems.
While X is flexible and powerful, it has some design flaws. Some approaches which made sense 40 years ago make less sense today. These days people want a consistent look for their desktop, performance over flexibility, and security is a bigger concern. Wayland is a protocol designed to address these modern concerns.
What tends to confuse people is Wayland is not a single piece of technology. Wayland is a protocol, a specification which can be implemented. As a result, each desktop environment (KDE Plasma, GNOME, etc) has its own version of Wayland.
The result is each implementation of Wayland on each desktop is slightly different. It should follow, at the least, the core Wayland protocol and be able to run applications built to support Wayland, but each desktop running the Wayland protocol will have its own quirks and features.
All of this is more theory than a practical overview. From a practical point of view, once your desktop's Wayland implementation is complete, you shouldn't notice any difference. The idea here is to basically replace X with something that, to the person using the technology, looks and acts exactly the same. Under the hood, Wayland-powered desktops will hopefully be more secure and offer better (and smoother) performance. However, whether this is true in practice will vary depending on how polished your desktop's implementation of Wayland is.
In short, you probably won't find there is any practical benefit (or drawback) to using a mature version of your desktop's Wayland session. However, behind the scenes your desktop will hopefully become more efficient and secure.
* * * * *
Forgetting-the-past asks: I've read that if I want to remove my shell's history I can run "history -c" and it'll be wiped. But when I then check my .bash_history file all my history is still there. Why doesn't it get erased?
DistroWatch answers: Assuming you are using the bash shell and that is why you're checking the .bash_history file to confirm whether your past commands have been forgotten, then I believe you're just missing one step.
The command you are using, "history -c", clears the current shell's memory of recent history commands. However, it does not wipe the contents of the history file, only the copy of your history stored in memory.
To both wipe the contents of your shell's history from memory and from the .bash_history file you need to first clear your history from memory and then write the blank history to disk. To do this you can run:
history -c && history -w
Some people might be wondering why those two commands cannot simply be combined, using "history -cw". I haven't looked into the details as to why this doesn't work, but I can confirm it will not have the desired effect. Perhaps it is a bug or the history command may write its memory to disk before wiping memory. Either way, be sure to split the history purge commands into two parts as shown above.
* * * * *
Additional answers can be found in our Questions and Answers archive.
|
| Released Last Week |
Q4OS 4.6
Q4OS is a lightweight, Debian-based distribution featuring the KDE Plasma and Trinity desktops. The project's latest version is Q4OS 4.6 which is based on Debian 11 "Bullseye". One of the project's aims is to allow both desktops to be installed alongside each other, a rare feature given the shared history of the two desktops. "Q4OS Gemini is based on Debian Bullseye 11 and Plasma 5.20, optionally Trinity 14.0.10 desktop environment, and it's available for 64bit/x64 and 32bit/i686pae computers, as well as for older i386 systems without PAE extension. We are working hard to bring it for ARM devices as well. Desktop profiler, an exclusive Q4OS tool, has custom profiles support now, so a user can export the current desktop status snapshot, modify it and even create customized profiles on his own. Any profile is importable, so a user can import and apply it later on another hardware, getting a unique possibility of easy installation and configuration of the pre-defined set of applications and packages at once. In other words, a user easily gets a fresh operating system installation configured and ready to work with a minimal post installation effort. In addition, each desktop environment may keep its own applications profiles." 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,612
- Total data uploaded: 40.2TB
|
| Upcoming Releases and Announcements |
|
Summary of expected upcoming releases
|
| Opinion Poll (by Jesse Smith) |
Ansible and other computer management tools
In this week's Feature Story we shared some tips on getting Ansible set up. Ansible is a computer management utility which allows a central server to send commands to many remote machines. Ansible is one tool for managing large deployments of computers and can be used to publish new packages and keep systems up to date.
Do you use a tool like Ansible to manage multiple computers, or perhaps another management tool to administer many machines? Let us know your preferred tool in the comments.
You can see the results of our previous poll on using virtual PDF printers in last week's edition. All previous poll results can be found in our poll archives.
|
Remote multi-machine management tools
| I use Ansible: | 102 (9%) |
| I use Chef: | 4 (0%) |
| I use ClusterSSH: | 17 (1%) |
| I use Puppet: | 20 (2%) |
| I use Salt: | 16 (1%) |
| I use another management tool: | 29 (2%) |
| I do not use a multi-machine management tool: | 983 (84%) |
|
|
| Website News |
New distributions added to database
LockBox
LockBox (LBX) is a Linux distribution derived from Debian, Ubuntu and elementary OS. It is especially designed for storing and managing cryptocurrencies. It includes several hardened configuration changes for security purposes, a highly restrictive firewall setup, several applications designed for data backups, a password manager, and the Brave internet browser. It also ships with BTCRecover which is an open-source Bitcoin wallet password and seed recovery tool.
LockBox 1.0 -- Running the Pantheon desktop
(full image size: 2.5MB, resolution: 2560x1600 pixels)
* * * * *
DistroWatch database summary
* * * * *
This concludes this week's issue of DistroWatch Weekly. The next instalment will be published on Monday, 11 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: 1, value: US$9.56) |
|
|
|
 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 |
| • Ussye 1118 (2025-04-21): Fedora 42, strange characters in Vim, Nitrux introduces new package tools, Fedora extends reproducibility efforts, PINE64 updates multiple devices running Debian |
| • Issue 1117 (2025-04-14): Shebang 25.0, EndeavourOS 2025.03.19, running applications from other distros on the desktop, Debian gets APT upgrade, Mint introduces OEM options for LMDE, postmarketOS packages GNOME 48 and COSMIC, Redox testing USB support |
| • Issue 1116 (2025-04-07): The Sense HAT, Android and mobile operating systems, FreeBSD improves on laptops, openSUSE publishes many new updates, Fedora appoints new Project Leader, UBports testing VoLTE |
| • Issue 1115 (2025-03-31): GrapheneOS 2025, the rise of portable package formats, MidnightBSD and openSUSE experiment with new package management features, Plank dock reborn, key infrastructure projects lose funding, postmarketOS to focus on reliability |
| • Issue 1114 (2025-03-24): Bazzite 41, checking which processes are writing to disk, Rocky unveils new Hardened branch, GNOME 48 released, generating images for the Raspberry Pi |
| • Issue 1113 (2025-03-17): MocaccinoOS 1.8.1, how to contribute to open source, Murena extends on-line installer, Garuda tests COSMIC edition, Ubuntu to replace coreutils with Rust alternatives, Chimera Linux drops RISC-V builds |
| • Issue 1112 (2025-03-10): Solus 4.7, distros which work with Secure Boot, UBports publishes bug fix, postmarketOS considers a new name, Debian running on Android |
| • Issue 1111 (2025-03-03): Orbitiny 0.01, the effect of Ubuntu Core Desktop, Gentoo offers disk images, elementary OS invites feature ideas, FreeBSD starts PinePhone Pro port, Mint warns of upcoming Firefox issue |
| • Issue 1110 (2025-02-24): iodeOS 6.0, learning to program, Arch retiring old repositories, openSUSE makes progress on reproducible builds, Fedora is getting more serious about open hardware, Tails changes its install instructions to offer better privacy, Murena's de-Googled tablet goes on sale |
| • Issue 1109 (2025-02-17): Rhino Linux 2025.1, MX Linux 23.5 with Xfce 4.20, replacing X.Org tools with Wayland tools, GhostBSD moving its base to FreeBSD -RELEASE, Redox stabilizes its ABI, UBports testing 24.04, Asahi changing its leadership, OBS in dispute with Fedora |
| • Issue 1108 (2025-02-10): Serpent OS 0.24.6, Aurora, sharing swap between distros, Peppermint tries Void base, GTK removinglegacy technologies, Red Hat plans more AI tools for Fedora, TrueNAS merges its editions |
| • Issue 1107 (2025-02-03): siduction 2024.1.0, timing tasks, Lomiri ported to postmarketOS, Alpine joins Open Collective, a new desktop for Linux called Orbitiny |
| • Issue 1106 (2025-01-27): Adelie Linux 1.0 Beta 6, Pop!_OS 24.04 Alpha 5, detecting whether a process is inside a virtual machine, drawing graphics to NetBSD terminal, Nix ported to FreeBSD, GhostBSD hosting desktop conference |
| • Issue 1105 (2025-01-20): CentOS 10 Stream, old Flatpak bundles in software centres, Haiku ports Iceweasel, Oracle shows off debugging tools, rsync vulnerability patched |
| • Issue 1104 (2025-01-13): DAT Linux 2.0, Silly things to do with a minimal computer, Budgie prepares Wayland only releases, SteamOS coming to third-party devices, Murena upgrades its base |
| • Issue 1103 (2025-01-06): elementary OS 8.0, filtering ads with Pi-hole, Debian testing its installer, Pop!_OS faces delays, Ubuntu Studio upgrades not working, Absolute discontinued |
| • Issue 1102 (2024-12-23): Best distros of 2024, changing a process name, Fedora to expand Btrfs support and releases Asahi Remix 41, openSUSE patches out security sandbox and donations from Bottles while ending support for Leap 15.5 |
| • Issue 1101 (2024-12-16): GhostBSD 24.10.1, sending attachments from the command line, openSUSE shows off GPU assignment tool, UBports publishes security update, Murena launches its first tablet, Xfce 4.20 released |
| • 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 |
| • 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 | 
Oracle Linux
Oracle Linux is an enterprise-class Linux distribution supported by Oracle and built from source packages for Red Hat Enterprise Linux (RHEL). Some of the special features of Oracle Linux include a custom-build and rigorously-tested Linux kernel called "Oracle Unbreakable Kernel", tight integration with Oracle's hardware and software products including most database applications, and "zero downtime patching" - a feature that enables administrators to update the kernel without a reboot.
Status: Active
|
| 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.
|
|
• 
• 
• 
• 
• 
• 
• 
