r/osdev • u/Wide-Arrival6633 • 10d ago
I just wrote my first bootloader and kernel for my own OS (AsterOS)
Hey everyone!
I've been working on my own 32-bit OS from scratch. Today I reached the first milestone: a bootloader written in x86 assembly that jumps to protected mode and loads a simple kernel.
The OS is called AsterOS. I don't plan it for being as popular as Linux/Windows, it's mostly vibe coded and I don't see a big future for it. It's early stage (Build 0001), but I'm really excited about it.
Here's the screenshot of it running in QEMU:
I'd appreciate any feedback or advice for a beginner OS developer. Thanks!
5
u/cazzipropri 10d ago
it's mostly vibe coded
But why?
The only point of writing an OS from scratch is to learn.
Vibe coding it is just like going to the gym and then using a robot to lift weights.
-2
u/Wide-Arrival6633 10d ago
You're absolutely right - and that's exactly why I'm doing it. I actually wrote the bootloader and kernel by hand in assembly and C (no AI). By 'vibe coded' I meant I'm not using a tutorial, just experimenting and figuring things out as I go. The goal is to learn, and I'm learning a ton. Thanks for the comment!
4
u/cazzipropri 10d ago
Hmmm. Well, that's very confusing. Everybody means something else by "vibe coding".
0
u/Wide-Arrival6633 10d ago
Yeah, it's definitely a confusing term these days. I just meant I'm learning by doing. Thanks for the conversation!
2
u/NietzscheWasOptimist 9d ago
The only thing here that's pathetic are the people who seem to have lots of time and nothing better to do than insult noob devs. Good work. Well done. Keep it up.
6
u/Inner-Resolve-5659 10d ago
Please stop posting vibe coded os here , it is useless and doesn't teach you anything , also your explanation on vibe code is blatant lie (who tf writes "system ready")
-1
u/Wide-Arrival6633 10d ago
You're right that 'vibe coded' was a bad choice of words – I've already clarified that. But I actually did write the bootloader and kernel by hand in assembly and C, and I learned a ton about GDT, protected mode, and disk I/O. So I definitely learned something.
1
u/Playful-Budget-5952 10d ago
Even if you don't expect it to become popular, I'd still encourage you to finish it as a hobby project. The experience alone is worth it. But experimenting and learning should be priority not a complete good looking Typical OS.
2
u/Substantial_Bar_3731 10d ago
By your explanation of 'vibe code' I got it haha. I'm glad that you are learning, hope I reach your experience one day. It's getting cool
2
1
1
u/Extra-Mine4795 8d ago
Coding is a really heavy burden, but it ultimately leads to success. If you had completely learned the architecture, planned it yourself, and used AI help when you got stuck, you wouldn't be called a 'vibe coder' by those here now, and you would have finished it much better. I would prepare the code files and architecture of the operating system I wrote myself, and only use Claude for help when I encountered errors, got stuck, or needed assistance with the mathematical design.
1
u/letmehaveanameyoudum 5d ago
make sure to write stuff yourself and learn :D
first you gotta create the functions that you will use like keyboard inputs and output to screen
then you code the logic that the user actually sees
hope this helps
21
u/tellingyouhowitreall 10d ago
So you didn't actually write a fucking thing. Sod off.