os01 VS posts

Write an OS from scratch

(Here is the link - didn't quite get the image/link combo right in the original post!). I'm writing a series of posts about coding your own operating system. After reading Operating Systems: From 0 to 1 I found that some of the code does not work, so this first post walks you through writing a bootloader similar to that of chapter 7. It also adds some context that I would have found useful when I originally read the book, such as how 16-bit real mode works and some assembly programming information. I'm hoping to take a different approach to posts in the series by borrowing pieces of other operating systems and discussing how they are implemented in an effort to keep things simple and focus on fundamentals (even Linus started out with a detailed reading of MINIX).

Starting a series about writing your own operating system. After reading Operating Systems: From 0 to 1 I found that some of the code does not work, so this first post walks you through writing a bootloader similar to that of chapter 7. I'm hoping to take a different approach to posts in the series by borrowing pieces of other operating systems (even Linus started out with a detailed reading of MINIX).

Very quickly skimming through the various chapters, it appears that this is gentle introduction as attention has been made on clear and verbose explanations, supplemented with diagrams. Comparable other "courses" could be osdev101 [1] and "Writing an operating system from scratch" [2].

[1] https://github.com/tuhdo/os01/blob/master/Operating_Systems_...

[2] https://www.cs.bham.ac.uk/~exr/lectures/opsys/10_11/lectures...

You need to be aware of how it works on a hardware level but probably not an expert, for a better explanation see: https://github.com/tuhdo/os01

Operating Systems from 0 to 1

Arkency http://blog.arkency.com/

I'd recommend Jason Swett. I listen to his podcast more often than I read his blog, but I might need to go back and read some more of his blog articles. I've also found Honeybadger.io's blog to be really informative. I'd also recommend Arkency, with some caveats. They promote a pretty specific architecture style using concepts from Domain Driven Design, Event Driven architecture, and CQRS. I believe these styles are powerful and can help tame a large, complex project, but I wouldn't recommend them in every case, so IMO, keep that in mind when reading their stuff.

I'm an indivudual but I love being part of the team where we can support each other. That's why the success of the Arkency blog (listed as top-10 ruby blogs in the world) - we help each other, we trust each other, we embrace our differences.

Thanks for commenting, because I think I didn't make it clear enough in the original post — that it's not meant to stay a do-nothing script, but gradually transition towards a do-something script. I have now updated the blogpost. It also assures me that do-nothing script is a bad name for it. I now think I prefer Puts-First Automation.

I updated the post to make it clearer since.