os-tutorial VS buildroot

How to create an OS from scratch

My dude. Your functions have exactly the same names as his. Copying it from a different tutorial based on James Molloy's tutorial does not make it any less James Molloy's code.

I started out with this tutorial: https://github.com/cfenollosa/os-tutorial. It doesn't get you too far but it explains the basics very well, so check it out. After that I looked up James Molloy's kernel tutorials (look it up on Google, it's all on a website). Be advised that he's got a bunch of errors and bugs in the tutorial, there is a whole page on it on the osdev wiki titled known bugs in the JamesM kernel all something like that, but it's still great and gets you pretty far. After that, I chose to develop a FAT32 driver on my own, I can link some sources or my own code for you as well, but it's really up to you to follow what you like. I also found a great youtube series (https://youtube.com/@poncho2364?feature=share9), check out his osdev series, he also has some cool stuff there. And as I said, good luck on your journey and you can ask me in a DM as well if you get stuck somewhere!

tutorial : here

Yeah, I'm following cfenollosa's OS tutorial for guidance. You mentioned that you've seen the same code, with the same bug? What was the solution there?

hey, just in case you actually want to write an operating system, you should check out cfenollosa/os-tutorial: How to create an OS from scratch, it is an amazing tutorial that will get you from basic printing all the way to a command line interface!

You might be able to sink your teeth into something like this if you're interested in real os development, haven't got far myself but it's fun and you'll learn a lot https://github.com/cfenollosa/os-tutorial

So I made a 16-bit x86 toy OS in pure assembly. 3 months ago, I found a very fun tutorial on github that is about Operating system development. I read the first few chapter and from there I made a very simple, extensible (?) toy operating system that could run on hardware (yes, it is madness).

I did it few times. It's so much easier nowadays with https://buildroot.org/

If you dig through the rootfs of the K1 it becomes clear that Creality is using buildroot so we should be able to do that ourselves - at least some of us.

An embedded system like Roku doesn't need to "run everything", it just needs to run their "platform", which is probably quite small. It's pretty trivial to assemble your own OS from "off-the-shelf" components. You can use something like buildroot to spin up a new OS in half a day, using only the components you want. You can also use "smaller" components that have far fewer features, meaning less bugs and less updates.

https://github.com/buildroot/buildroot

> I do this for every Windows installation that is used for similar purposes, like embedded machines that has to run a single application, virtual machines, etc.

Have you tried running Linux for these use cases? This sort of thing is an area Linux excels, in my experience.

When you run Windows, you're in for the whole kit and caboodle. Most of the components are proprietary, closed-source black boxes. You can only poke and prod and test and hope things don't break in unexpected ways.

Conversely, Linux can be easy stripped down to a bare bones kernel and a single statically-linked binary. I can run a useful application on top of Linux with the whole system weighing in smaller than bootmgfw.efi.

Something more complex, but still custom, is easily crafted with Buildroot.

https://buildroot.org/

Have a look at the commit history of Linux or buildroot for nice readable commit histories.

Gentoo could teach you more about what is involved in dependency handling and actual ‘construction’ of a Linux system. But Linux From Scratch is a much better teaching tool for learning this, and even things like Buildroot are arguably better than Gentoo for this because they generally force you to care about a lot of the stuff that Gentoo hides away to make the system nicer to use.