git-remote-gcrypt VS linux

Are you aware of https://spwhitton.name/tech/code/git-remote-gcrypt/?

We use a modified https://github.com/spwhitton/git-remote-gcrypt on some of our git repos and employ the GPG Keychain app (from https://gpgtools.org) to help us manage the associated keys.

I used to rely heavily of Keybase reops, but since the takeover I'm no longer confident in their longevity. An alternative option is to encrypt files yourself and use a mainstream git provider. There are utils like gcrypt specifically for this use case. That way you can be confident in the encryption AND availability.

Yes, git-annex is perfect for this. It can do this with encryption via the rsync special remote. To store the git branches themselves, you can use git-remote-gcrypt. For backups, you can store the files on external hdds (additional to rsync.net) and keep them mostly offline/powered off. git-annex works really well with offline drives. Alternatively you can backup to another cloud provider that is supported as a special-remote.

Those other flashy distros like mint and ubuntus are designed with rich people with very fresh machines in mind, they don't care if you have an AMDx4 or core2duo or even 32bit older machine. Even Mint and ubuntu people will tell you, if you have an old machine with little ram, use antiX. It still works very well with machines not even released yet, buy one in May 2024 and I "guaranty you" antiX will run fine. That's because kernels, even 6.1 have code for machines not yet released in the market, this is where manufacturers of new hardware send their prototypes to be tested, to kernel.org Some are even industrial machines we will never see in the market.

The memory_order_relaxed explanation on the kernel.org documentation heavily implies (never explicitly) that the direct memory load is implicit in the barrier(so by preventing it's reordering we are also forcing a LOAD from main), and that THIS specific barrier (relaxed) is what we NEED for these type of scenarios, so I am not entirely sure if a loadLoadFence() would prevent the hoisting... maybe it will prevent the reordering but not the hoisting/caching... in which case we would still have a visibility issue.

Are all versions of the kernel from kernel.org called mainline kernels or only 6.6-rc4 as shown in the picture?

Devuan is a fork of Debian GNU+Linux without systemd.

I built the dev env on Devuan GNU+Linux, a fork of Debian without systemd. It resembles my past trial on Artix Linux.

Devuan GNU+Linux is a fork of Debian without systemd and hence Snaps (Snapd). Even on it, it's easy to install Android Studio and start to develop Android mobile apps.

kernel.org