Ginux: A New Kernel Runs Linux Userspace, Made via Human-Directed AI Engineering

INTPenis

Why does it seem like HDAE is just a new term to distract from terms like "vibecoded" and "AI slop"? Because the bigger the project, the more unlikely it is for a human to review all the code. And in this case we're talking about re-making the Linux kernel.

leothetechguy

I do not trust most research published on zenodo, in my experience almost everything there equates to AI Slop.

asmnzxklopqw

Let me help you here: you want to say “Made via AI slop”.

rvz

> "Made via Human-Directed AI Engineering" So vibe coded then.

nign

Ever heard of gvisor...?

codetiger

I recently built a concept Linux OS with the entire UI generated by a local AI model based on the user's intend. https://github.com/codetiger/velliangiri

ForHackernews

For context, the author of this is one of the creators of Rocky Linux, so it's probably not just vibecoded rubbish. https://gmkurtzer.github.io/ https://x.com/gmkurtzer/status/2114958282481910115 > Ginux is a research prototype, not a production kernel or Linux replacement. The larger lesson is that AI can generate complex systems software, but compatibility, security, hardware support, standards, community, and long-term maintenance remain the real moat.

flossly

Most of the comments here are super salty. Agentic coding is here to stay, and the authors are here to make it better. And as a test case they built a Linux-compatibe thing in Rust! Al of this is cool to me, but what I read here in the comments: slop, stealing, evil people, no trust, etc. Linux is open source: the license says that it can be used for any purpose, which includes training an LLM. LLMs have made developers more powerful (like IDEs did, or CI/CD did, or better programming languages did, or Github did, or ...), but all I hear is nagging.

hn_submit

"Human directed A.I. engineering" is a euphemism for slop.

gdgghhhhh

An initial review found a few things: https://social.kernel.org/notice/BBry0fMLEodHRiUqGW Apparently they got fixed by now.

brainless

LLMs will eat software. Much, not all, of software is taking ideas into a strict language, compile to a stricter language and check if the processing unit will run it. There are a ton of algorithms and many can be combined with many others. A token prediction system that has built a multi-dimensional model of all tokens on the Internet should be good at generating a bunch of algorithm combinations. Then it is about a loop to test, find out other combinations, find a winner.

jonhohle

Project includes an Apache license, but code created by an AI is not copyrightable and it’s output is in the public domain. > Ginux is available under the Apache License 2.0. See LICENSE and NOTICE. Zarya of the Dawn concludes that human direction and selection is not enough to produce a copyrightable work from AI generated content. Without copyright, there is no legal basis to offer a license. The code is public domain or worse, mislicensed, AI washed GPL or BSD.

axegon_

"Made via Human-Directed AI Engineering" JFC... The world does not have enough psychiatrists to fix the current catastrophe.

vikramkr

Y'all I get that the term "vibe coding" feels derogatory and that it took off as a term before it took over regular dev work too. But we're kinda stuck with the name and running away from it with "Agentic Engineering" or "Human-Directed AI Engineering" to try and distinguish from some normie asking Claude to make a random app iw just not gonna stick. Maybe if we go with "vibe engineering" as a tongue in cheek sort of name but I think running away from the "vibe" part of vibe coding to describe agentic dev is just not gonna work nobody's gonna let us get away with it

InsidiousWombat

Just vibe your app to run directly on CPU, why bother with vibed in kernel ?

hideki_okumura

Tasks like ×× that are compatible with 〇〇 are what AI excels at most. This is because the process of expanding compatibility can be improved incrementally, and the acceptance criteria are clear. 1. Prepare one item that works with 〇〇 2. Make it work with ×× 3. Return to (1) until it is deemed sufficient 4. Prepare 100 items that work with 〇〇 5. Measure performance with ×× 6. Measure performance with 〇〇 7. Consider several performance improvement measures 8. Implement improvement measures while verifying that compatibility is not compromised 9. Return to (4) until it is determined that performance has improved sufficiently 10. Completion of ××, which is sufficiently compatible with 〇〇 and not inferior in performance

sega_sai

On this, I was recently wondering if Anthropic at some point will make an announcement of full re-implementation of Linux kernel in Rust. But maybe that would be a too-niche of a news to affect their IPO.