I have some questions:
Q1. What is the actual roadmap for OS development (a simple working desktop ) like making bootloader , file systems etc
Q2. Best resources and books.
Q3. How to go about overall architecture(basically i have in mind) and GUI design howz that done
thanks a lot [/b]
Getting started
Getting started
I havent failed but has found 10,000 ways the things won't work
Good Questions for begginers.Q1. What is the actual roadmap for OS development (a simple working desktop ) like making bootloader , file systems etc
Q2. Best resources and books.
Q3. How to go about overall architecture(basically i have in mind) and GUI design howz that done
Reflect Desktop Operating System - ' You only remember the name of the OS when it crashes '
Skip bootloader, and use Grub instead as writing a good bootloader is a project as big as writing a basic kernel. As for development roadmap, start with basic kernel memory management, interrupt setup and multi-threading. Once those work, you can go with device drivers, filesystems, process memory management, userspace issues, maybe networking, and then at some point user interface.osdp.vnx wrote:Q1. What is the actual roadmap for OS development (a simple working desktop ) like making bootloader , file systems etc
Q2. Best resources and books.
Q3. How to go about overall architecture(basically i have in mind) and GUI design howz that done
Our Wiki is good resource, Wikipedia is another good resource, Google is a wonderful resource, and then there's variety of books which you probably wanna check out in libraries.. or something..
As for architecture, it's up to you, but GUI design is pretty much a separate issue, which isn't anywhere near the first thing you should start with if you want to design a full operating system. If you simply wanna do GUI design, you should probably consider doing that on top of an existing OS. Linux is one possible choice..
The real problem with goto is not with the control transfer, but with environments. Properly tail-recursive closures get both right.
Getting Started
Thanx for the replies
My road map would be now :
1. To print "Hello World" on the screen using some BOSCH or VMWARE simulators ..so that gives u a better confidence that things are actually working
2. Memory Management or File System implementtaion
i hope that is reasonable enough..rather than digging unnecessarily into bootloader....GRUB would be choice
My road map would be now :
1. To print "Hello World" on the screen using some BOSCH or VMWARE simulators ..so that gives u a better confidence that things are actually working
2. Memory Management or File System implementtaion
i hope that is reasonable enough..rather than digging unnecessarily into bootloader....GRUB would be choice
I havent failed but has found 10,000 ways the things won't work
- mathematician
- Member
- Posts: 437
- Joined: Fri Dec 15, 2006 5:26 pm
- Location: Church Stretton Uk
Forget about the file system until you have got some device drivers, at least for the floppy disk. In my humble opinion there is no other way to build an operating system than from the bottom up, and at the bottom there is the hardware with the accompanying device drivers.
As for resources, there is no end to the reams of documentation you can download from Intel, AMD and others. To date I think I have got about twenty lever arch files full of the stuff, and I doubt if I'm finished yet.
As for resources, there is no end to the reams of documentation you can download from Intel, AMD and others. To date I think I have got about twenty lever arch files full of the stuff, and I doubt if I'm finished yet.