@wagi last I looked, it couldn't do OpenPGP cards, so wasn't a suitable replacement for me yet. It may have changed since then.

@wagi It's a valid criticism of GnuPG, but it's not necessarily the fault of all OpenPGP implementations. Tools like Sequoia-PGP exist specifically as efforts to reimplement OpenPGP in a modern framework that's not bogged down by legacy decisions.

@mariusor that solution doesn't scale. I'll just pay $50 for an AI to render a good enough video of Linus saying the fingerprint.

Every time someone claims that they have replaced OpenPGP with "something easier," I always look to see how they handle key management and trust delegation, and usually discover that it's just handwaved away.

Questions like this are a reminder that key management and trust delegation are the exact thing that makes OpenPGP "too hard" in the eyes of most people.

https://www.reddit.com/r/linuxquestions/comments/16c16fu/how_can_i_verify_the_pgp_keys_for_linus_torvalds/

@neil Your reluctance to take questions certainly makes you Sir Cumspect.

@a1ba and "gun pew-pew"

@iliazeus FYI, tar will automatically recognized compressed archives. You don't need to add -z, -j, you can just do -xf.

Anyone else has `alias ungz=gunzip`?

@captainepoch mostly recovered, thank you! Still not testing negative, though, so keeping myself isolated when I can.

@arj sure. it's a bit outdated, but not obsolete.

The first of each month works as a regular reminder of how many mailman-2 servers there still are out there.

@noodles @nwalfield I'm curious what is your opposition to merge commits? For example, they make it easy to keep all logically grouped commits in one easily identifiable sequence, and the merge commit message can describe the purpose of the whole series.

Did you ever wonder how those kernel releases make it to a mirror near you? Wonder no more, I've documented the process of delivering the latest set of stable kernels.

https://youtu.be/_MnZdrBJOwI?si=kfzFgfjr_yi8F4md

@ioletsgo ignoring the blatant ageism, this person knew how to take a screenshot of their system info view, google for Linux kernel, find the email, attach the right screenshot, and send that in. They are tech-savvy, just not quite to the right depth.

Oh no.

Here is a hopefully-useful notice about Linux kernel security issues, as it seems like this knowledge isn't distributed very widely based on the number of emails I get on a weekly basis:

- The kernel security team does not have any "early notice"
announcement list for security fixes for anyone, as that would only
make things more insecure for everyone.

- The kernel community does not assign CVEs, nor do we deal with them
at all. This is documented in the kernel's security policy, yet we
still have a number of people asking for CVE numbers even after
reading that policy. See my longer "CVEs are dead..." talk for full
details about how the CVE process is broken for projects like Linux:
https://kernel-recipes.org/en/2019/talks/cves-are-dead-long-live-the-cve/

- You HAVE to take all of the stable/LTS releases in order to have a
secure and stable system. If you attempt to cherry-pick random
patches you will NOT fix all of the known, and unknown, problems,
but rather you will end up with a potentially more insecure system,
and one that contains known bugs. Reliance on an "enterprise"
distribution to provide this for your systems is up to you, discuss
it with them as to how they achieve this result as this is what you
are paying for. If you aren't paying for it, just use Debian, they
know what they are doing and track the stable kernels and have a
larger installed base than any other Linux distro. For embedded,
use Yocto, they track the stable releases, or keep your own
buildroot-based system up to date with the new releases.

- Test all stable/LTS releases on your workload and hardware before
putting the kernel into "production" as everyone runs a different %
of the kernel source code from everyone else (servers run about
1.5mil lines of code, embedded runs about 3.5mil lines of code, your
mileage will vary). If you can't test releases before moving them
into production, you might want to solve that problem first.

- A fix for a known bug is better than the potential of a fix causing a
future problem as future problems, when found, will be fixed then.

I think I need to give another talk about this issue to go into the above in more detail. So much for me giving a technical talk at Kernel Recipes this year...

@adnan apparently the latest variant is very good at avoiding the immune response from vaccines and previous infections by other strains. So, yeah, I would suggest masking up in poorly ventilated indoor spaces and taking a booster when one is available for the latest variant.

PSA: don't get COVID. It sucks.

@luis_in_brief oh, I'm back already. I was visiting my relatives in .kz

Dear Qatar Airlines. Everything was great, but providing "Avengers: Infinity Wars" without "Avengers: Endgame" in your entertainment options is just _mean_.