Lately I have seen quite a few LinkedIn posts about Ginux, a Linux-compatible kernel written in Rust during an 11-day OpenAI Codex session.
It boots a Rocky Linux userspace, which is genuinely impressive.
The usual "AI experts" promptly declared Linux dead, since anyone can now ask an LLM for a Linux-compatible kernel.

So I took a look. Ginux is an interesting experiment, and I recommend reading the paper (link below), because many people did not understand what it actually is.

What I found in the code:

👉 Lots of global state. Even signal handling goes through global variables.
👉 Everything assumes exactly one CPU. Critical sections are "protected" by disabling interrupts. There is no SMP and no locking.
👉 The code does not look designed. It looks like it grew organically until the test cases passed. The x86-64 CPU module alone is a single 44,000-line file.

Rust does not make it automatically secure either. Two examples:

☠ On x86-64, the SYSCALL instruction does not switch stacks. The kernel's first few instructions after SYSCALL run in ring 0 with the stack pointer still provided by userspace. Every kernel has this window. Linux handles it by giving NMI and machine check exceptions their own interrupt stack (IST), because those are the only events that can fire while interrupts are masked. Ginux gives only the double fault an IST. If an NMI or machine check arrives in that window, ring 0 code runs on a user-controlled stack.

☠ When the kernel copies data from or to userspace, there is no fault recovery. Linux uses exception tables, so a bad user pointer becomes EFAULT. In Ginux, the address is validated in software first and then accessed directly. If the validation and the real page tables ever disagree, the result is a kernel panic. And the validation does have a fallback path that trusts software bookkeeping where the hardware page-table walk just said no. It is not exploitable today, but only because of invariants spread across other modules, not because of the check itself.

Ginux is a cool demonstration of how far you can get with human-directed agentic engineering. It is not proof that everyone can now have their own Linux-compatible Rust kernel with minimal effort.

Links:
https://zenodo.org/records/23682548/files/ginux-ai-systems-report.pdf

https://github.com/gmkurtzer/ginux/

https://github.com/gmkurtzer/ginux

Irish pubs in Italy know what's the good stuff.

Simon Legner has released Maplair, an open-source JavaScript library for interactive maps, forked from Leaflet.

https://maplair.org/2026/10/19/maplair-4.0.0.html

#osmweekly #OpenStreetMap

I just want to say thanks to the Debian Security Team for making my life sooooo much easier. For the most part, if I keep my system up to date I can switch my brain off.

In years of running many Debian systems for many people, I've never had a serious incident involving something that the Debian security team could've done anything about. Really stellar work and I'm sure many people don't even realise how much they benefit from it!

Note the gcc compile farm can be used anyone for any open source project. Not just gcc or any part of the gnu toolchain. Can be used for an example for llvm development or development of some library . It has machines for aarch64, x86, sparc, powerpc and more .

See https://gcc.gnu.org/wiki/CompileFarm for more information

I don't know who needs to hear this, but probably all of you.

[$] SUSE's efforts to disable setuid system-wide

Setuid (and setgid) binaries have long been a source of headaches, and security vulnerabilities, on Linux systems. They are largely seen as something to be avoided; SUSE's security [...]

https://lwn.net/Articles/1100257/

#LWN #Linux #SUSE #glibc #systemd #FUSE

Found a bug

Dear Lazyweb, I'm looking for a hard copy of the book "Der Phrasenprüfer: Szenen aus dem Leben von Wau Holland, Mitbegründer des Chaos Computer Club". If you own a copy and want to sell it, please contact me.

Dear Lazyweb, I'm looking for a hard copy of the book "Der Phrasenprüfer: Szenen aus dem Leben von Wau Holland, Mitbegründer des Chaos Computer Club". If you own a copy and want to sell it, please contact me.

RIP leap seconds.

https://www.bipm.org/en/cgpm-2026/resolution-5

People who find LLMs useful when "used correctly" don’t understand that they manage to use them correctly because they spent 20 years of there life learning their craft without LLMs.

LLMs is the only tool where the less you use it, the better you become at using it.

[$] Collaborating with out-of-tree tracers

LTTng creator Mathieu Desnoyers seems a bit trapped in something of a catch-22. At the 2026 Linux Plumbers Conference (LPC), he led a discussion on the problem he is having in tryi [...]

https://lwn.net/Articles/1099300/

#LWN #Linux #kernel #BPF #OSS #LPC

RE: https://mograph.social/@dilmandila/117432072219819451

Please help finance GIMP, Inkscape and Krita instead of spending your money on trying to get Claude to make you a Photoshop clone.

https://www.gimp.org/donating/
https://inkscape.org/support-us/donate/
https://krita.org/fr/donations/

Nein, niemand hat mit AI einen Adobe oder Office Klon gebaut. Jemand hat Geld und Tokens rausgerotzt um die Fassade einer Software zu bauen die oberflächlich das gleiche tut, untendrunter buggy wie Sau ist und garantiert nicht maintained und repariert werden wird.

Das nennt man übrigens Slop, aber scheinbar wird es gefeiert, wenn man glaubt, dass es Big Tech weh tut (tut es nicht).

Und es scheißt einfach auf die Leute hinter OpenOffice und Co, die sowas seit Jahren pflegen und bauen