Notices by Ludovic Courtès (civodul@toot.aquilenet.fr), page 2

I’ve now deployed the 🐑 Shepherd 1.0 on most servers I (co-)administer, and it feels much nicer than before, especially providing better insight into what’s happening on the system.

(It may sound like self-congratulation, and that’s kind of what it is, but it’s undoubtedly the surest way to be congratulated. :-))

#Guix channel containing packages for symbolic execution engines:
https://github.com/agra-uni-bremen/guix-symex

Rootless #Guix build daemon merged! 🎉
https://guix.gnu.org/manual/devel/en/html_node/Build-Environment-Setup.html

The two-month long review process was key in making this more solid, thanks to the rigorous analyses by fellow hacker Reepca Russelstein:
https://issues.guix.gnu.org/75810

Next step is to provide a way to turn it on on Guix System:
https://issues.guix.gnu.org/77288

This whole story is unbelievable…
https://www.theatlantic.com/politics/archive/2025/03/trump-administration-accidentally-texted-me-its-war-plans/682151/

But besides the amateur behavior, what’s astonishing is the lightheartedness and childishness with which these people trigger killings far away from their place and celebrate them.

📢 #Guix team members: 10 days left on the deliberation period of GCD 003, “Set search paths without program wrappers”.
https://issues.guix.gnu.org/76428#10

The way NixOS handles releases keeps inspiring me:
https://chaos.social/@leona/114179910849295139

There’s a single-mandate team of release managers + editors (two distinct roles), with a schedule showing important events and affected branches. 👍

Nice guide on writing 🐑 #Shepherd services for #Guix 👇
https://tannerhoelzel.com/gnu-shepherd-simple-service.html

It would make a good Cookbook section!

C is terrible and Rust is so much better, but I don’t think memory safety is the only justification for having ‘ls’ in Rust.

Some of those active in this effort worked on replacing GCC with Clang in distros before.

Bye, copyleft. Hello, corporate interests.
https://fosstodon.org/@gnutools/114168573791483805

I have an Atheros (ath9k) WiFi device and I just discovered it has a “regulatory domain” hard-coded to China in EEPROM, and the ath9k Linux driver blindly follows that, ignoring the regdomain userland asks for.

Seems the driver can be hacked to work around that, but I’m not fully convinced:
https://github.com/twisteroidambassador/arch-linux-ath-user-regd?tab=readme-ov-file

(And really, why am I doing this to myself?)

Unprivileged #Guix daemon close to landing 👇
https://issues.guix.gnu.org/75810

@janneke Haha, another perfect headline, you must have learned from top-notch journalists! :-)
@socallinuxexpo

Formally submitted GCD 002: “Migrating repositories, issues, and patches to Codeberg”. 🎉
https://issues.guix.gnu.org/76503

Check it out, #Guix people, and share your thoughts!

If you missed it, #Guix adopted the “Guix Consensus Document” (GCD) process two weeks ago:
https://git.savannah.gnu.org/cgit/guix/guix-consensus-documents.git/tree/001-gcd-process.md

This is a collective decision-making process that aims to build consensus on important decisions among contributors. It’s a major milestone for the project.

A couple of GCDs have already been submitted; looking forward to the outcome!

People often say: “what if someone disagrees with a proposed GCD?”.

The process is not about agreeing/disagreeing on an immutable proposal; it is about collectively building a solution that addresses all concerns.

Message to fellow #Guix hackers writing 🐑 #Shepherd services: do not call ‘waitpid’. Thank you.
https://issues.guix.gnu.org/76262

The 🐑 #Shepherd was at #FOSDEM and now it’s on TV! 📺
https://www.gnu.org/software/shepherd/news/2025/02/the-shepherd-on-tv/

Check out my talk on the beauty (and dangers!) of #Fibers for concurrent programming and that of Juliana on porting it to #Goblins and starting the plan9ification of #Guix. 🤯

📢 The new Guix-HPC annual report is out!
https://hpc.guix.info/blog/2025/02/guix-hpc-activity-report-2024/

Check out what we’re up to with #Guix in support of #HPC, #ReproducibleResearch, and #OpenScience.

I was reminded of the importance of the “no asshole rule” in free software communities—you know, ensuring that borderline behavior that’s not clearly a CoC violation yet that demonstrates a lack of empathy or downright hostility doesn’t spoil the whole group’s endeavors.

(I think I saw a great talk or blog post about this some time ago, but I can’t remember where that was.)