Tux Machines
Posted by Roy Schestowitz on Apr 18, 2023
=> LibreArts Weekly Recap and Chat With Mastodon CEO | Devices: Cameras, Robotics, and Linaro
=> ↺ CentOS Board Meeting Recap, April 2023
The recording of the April CentOS Board meeting is now available. Watch the recording Read the minutes The recording has timestamps so you can skip to the parts that interest you.
=> ↺ Thorsten Leemhuis: Package names can be false friends, too, as (linux|kernel)-headers show
TLDR: Thekernel-headers
packages in Fedora, RHEL, or CentOS do not carry the files you get by installinglinux-headers-$(uname -r)
on Debian based distros. If you want to build add-on modules for the kernels in Fedora, RHEL, or CentOS, you need to installkernel-devel
instead. Fun fact: I consider both approaches to package naming flawed.
Packages in different, unrelated distros sometimes have similar names, but nevertheless contain something entirely different. People that don't keep this in mind are sometimes going to have a bad time.
=> ↺ Fabio Alessandro Locati: GitHub Actions and containers
GitHub Actions allows the use of containers with different Operating Systems. Although, it does not mean that everything is seamless when you are using them. I’ve discovered this the hard way! Below are my findings and the process I followed to make the GitHub Action pipeline work properly with containers. It all started with the addition of a new tool in the pipeline, which was not installable on Ubuntu (the GitHub Actions default operating system), due to a packaging issue.
=> ↺ Fedora Magazine: Linux bcache with writeback cache (how it works and doesn’t work)
bcache is a simple and good way to have large disks (typically rotary and slow) exhibit performance quite similar to an SSD disk, using a small SSD disk or a small part of an SDD. In general, bcache is a system for having devices composed of slow and large disks, with fast and small disks attached as a cache.
This article will discuss performance and some optimization tips as well as configuration of bcache.
=> ↺ Still struggling with the Flatpak sandbox
I have posted that Flatpak does not work with ext4 fscrypt:
https://bkhome.org/news/202304/flatpak-does-not-work-with-ext4-folder-encryption.html
=> ↺ https://bkhome.org/news/202304/flatpak-does-not-work-with-ext4-folder-encryption.html
I have hunted, found some discussion, but no solution. For example:
https://github.com/flatpak/flatpak/issues/4281
=> ↺ https://github.com/flatpak/flatpak/issues/4281
So for Easy 5.2.2, had to resort to placing the app home path in an unencrypted folder.
=> ↺ https://bkhome.org/news/202304/flatpak-does-not-work-with-ext4-folder-encryption.html | ↺ https://github.com/flatpak/flatpak/issues/4281
The saga continues. Previous post:
https://bkhome.org/news/202304/still-struggling-with-the-flatpak-sandbox.html
=> ↺ https://bkhome.org/news/202304/still-struggling-with-the-flatpak-sandbox.html
Starting some flatpaks from a terminal, they reported SSL errors. Microsoft-Teams-for-Linux Flatpak starts, but only a blank window. Errors, cutdown:
[...]
=> ↺ https://bkhome.org/news/202304/still-struggling-with-the-flatpak-sandbox.html
=> gemini.tuxmachines.org This content has been proxied by September (ba2dc).Proxy Information
text/gemini;lang=en-GB