@geert side-note: I recently doubled the % in a password included in my .pwclientrc. I’m sure it worked with a single % before.

@geert I think you have to press and hold Shift (or was it Ctrl?) while clicking shutdown to make Windows not hibernate but shut down properly. /!\ half-knowledge

@spanezz That post didn’t age well :-\

@monsieuricon My initial thought was you found a biiiig prime number that got named after you. I wondered why you added that to your name and guessed you’re proud of your finding :-D

@monsieuricon So at most 18 mails before you handle this patch and also this patch? Awesome.

#OpenPGP keysigning party at #LPC and #OSSummit in Prague this October. See the announcement for more details.

You’re coming to @embeddedrecipes and missed the registration deadline for the PGP keysigning? No big issue 😅, join the session anyway and bring paperslips with your UIDs and fingerprint.

At #embeddedrecipes 2026 (May 27-28) in Nice (France) there will be another #PGP keysigning session. Help to improve the kernel’s WoT.

How come that for each bank I need an app specific to this financial institution to login? There are open standards for secure login (e.g. FIDO2) and I bet using one of them is more secure in most cases than their self-rolled crypto.

@geert You wanna say this sign doesn’t mean “Don’t park your bike here with the handle bar on the right side.”?

@geert I already did

@brauner I wonder about the CfP deadline for the kernel devroom. The announcement says it’s Sunday, 10 December 2025, but 2025-12-10 is a Wednesday?!

I’m going to #fosdem26!

Michal Wilczynski wrote about his quest to add Rust support to the PWM subsystem. Thanks for going through that.

@kdave this should indicate which standard is used. C99 (which is quite the norm today in my bubble) has some more: inline, restrict, _Complex and _imaginary. Other than that: 30/32

@geert There is a relevant difference (and today’s situation is again different, see below):

$ time make kernelrelease
2.6.14

real	0m0.044s
user	0m0.039s
sys	0m0.006s

$ time cat include/generated/utsrelease.h
cat: include/generated/utsrelease.h: No such file or directory

real	0m0.002s
user	0m0.000s
sys	0m0.002s

That is, make kernelrelease only emitted the version determined by the source (in Makefile), while utsrelease.h also accounts for .config.

Today there are two make targets: kernelrelease and kernelversion. The first depends on .config (and thus takes CONFIG_LOCALVERSION, CONFIG_LOCALVERSION_AUTO etc. into account), the latter has the same semantic that I introduced for kernelrelease back then. See commits 6b6a462c4ab7 (“[PATCH] KERNELRELEASE depends on CONFIG_LOCALVERSION”) and cb58455c48dc (“kbuild: KERNELRELEASE is only re-defined when buiding the kernel”).

And FTR: I think the semantic and names are swapped. For me the kernel release is 6.18.0-rc4 and the version can be something like 6.18.0-rc4-00155-g4a0c9b339199.

@gregkh Oh damn, I forgot to git add

Feeling both old and proud: My first kernel patch was accepted yesterday 20 years ago!

@otte_homan @publicvoit This is how /usr as we know it today was born. “In the original Unix implementations, /usr was where the home directories of the users were placed (that is to say, /usr/someone was then the directory now known as /home/someone).” (from FHS). Your chance to keep /home/cache/apt and coin how Linux look in the future 😆

@geert @acb If the random person in Nebraska is taken out the top part might become horizontal again. I think this is where the metaphor stops … :-)