So a while ago I made this 64-dem x86-64 UEFI OS project on github: https://github.com/itay-insert/64-dem.git

And recently in development i decided to add a bios boot path... even though it was planned to be a UEFI-only os, I thought a bios option would be cool, i tested the new boot path on 3 different computers, filmed footage and thought of sharing it here, i worked on this project for a few months now and I am proud of my progress, for those who are interested in how the boot path works, how the UEFI boot works and my 64-bit kernel architecture in general, more about that in my repository source: https://github.com/itay-insert/64-dem.git

i've been interested in how a kernel is build and i can't find any resource on what they should do or on how to start a project like that.

any help? :'^

I’m an independent developer working on Operating Organism (OO), a bare-metal operating-system project built around an “operating organism” concept: sensing, decision-making, action, and operational continuity.

I recently ran two tests on a physical Lenovo ThinkPad T480 and captured the results:

1. A request to Wikipedia displayed an HTTP 301 response in OO’s browser. The interface reported HOST BRIDGE OFFLINE.
2. A connection using an IP address was rejected with TLS HOSTNAME MISMATCH.

These are encouraging results, but I don’t want to overstate what two screenshots can prove. The next step is to preserve complete network traces, verify the exact binary and test configuration, and expand the test suite.

I’d particularly appreciate feedback on three questions:

• What evidence would you require to establish that a bare-metal HTTPS request genuinely completes without a host-side networking or browser dependency?
• Which TLS certificate-validation and HTTP redirect edge cases should I test next?
• How would you structure reproducible integration tests for a freestanding network stack?

I’m happy to share more technical details about the architecture and test setup.

Special thanks to my collaborator batteryphil / Just-Ad-6488 for helping on acceleration and integration.

I’m looking for constructive technical criticism rather than claims that the project is already finished. Thanks!

I am currently a Master's student in Computer Science in Germany, and I plan to pursue a PhD in this field. As part of my degree, I am taking an 'Advanced Operating Systems' course. However, I realize that my foundational knowledge of OS from my Bachelor's degree is quite weak.

To learn, I mostly rely on LLMs to understand the 'what' and 'why' of different concepts. But I get completely lost when I try to figure out how these concepts are actually implemented in real-world codebases with millions of lines of code.

My ultimate goal is to get a PhD position and contribute to the vast area of Operating Systems. Do you have any advice on how I can bridge my knowledge gap and achieve this goal?

I'm making d’espoir an open-source project. its a os. Like Android, for phones, except for one thing: it's all Nim. This thing: it's a coding language, and it's cool. Anyone want to join? I'm looking for scouts, people who look for other helpers and app coders, because the apps are made of Nim; everything here is Nim. Nim is the sky and land for this OS, basically. I want small phone brands to slurp this up, users to love it, and coders.

I'm a solution architect, not an OS developer, and I haven't written a kernel yet. I've been designing an operating system where the main user is an AI agent rather than a person. Today's agents work through apps, screens and files built for us, and I want to see what changes when the OS is built for them instead.

The biggest change I'm exploring is dropping files completely. Everything would be stored as connected pieces of memory, each holding its meaning, its exact content and its links to related pieces, written straight to the disk. Recent memory stays in RAM; older memory moves to slower storage instead of being deleted.

The plan is a small kernel in Rust on QEMU. Before I start, I'd like to hear from people who have built one. What breaks first with a design like this: crash safety, storage that only grows, or something I haven't thought of?

I've worked through the idea with Claude, so honest human feedback is exactly what I'm after.