Linked by Hadrien Grasland on Fri 28th Jan 2011 20:37 UTC
OSNews, Generic OSes It's recently been a year since I started working on my pet OS project, and I often end up looking backwards at what I have done, wondering what made things difficult in the beginning. One of my conclusions is that while there's a lot of documentation on OS development from a technical point of view, more should be written about the project management aspect of it. Namely, how to go from a blurry "I want to code an OS" vision to either a precise vision of what you want to achieve, or the decision to stop following this path before you hit a wall. This article series aims at putting those interested in hobby OS development on the right track, while keeping this aspect of things in mind.
Permalink for comment 460542
To read all comments associated with this story, please click here.
by jibadeeha on Tue 1st Feb 2011 18:12 UTC
Member since:

I remember wanting to write my own Operating System years ago, and bought a book called "Developing your own 32-bit Operating System". It sounds sad, but I had never been so excited about a book and thought it was really good for step-by-step learning.

I then started to read a book on the x86 architecture and protected mode, but unfortunately only got far as writing a boot loader (like so many) that switch the machine into protected mode and then wrote my own code to output some text to the screen.

It took me many months to get to that stage, so much so that I hit a wall with it and gave up. Yet I had original ambitions to write my owner scheduler, memory management, and file system code.

I wasn't cut out for OS development, so really admire those who managed to write their own hobby OS - it takes a lot of your time and dedication.

Reply Score: 1