OSDev.org

Hey guy I know all the OS concepts, I want to start development but failing, I want to know how should I start, I am a good programmer, but I am not able to understand on where to start and get going.
Should I refer some guide? or a book?
Please help/guide me.

emfader wrote:I know all the OS concepts

I would be careful not to use that expression. It may turn out to be false when you actually get something done. I do not know what is the best way to start. I think it does not even matter much. Whatever low-level related you study and try, it helps. A boot loader is one easy way to get started. I think you cannot directly start making an OS. Do many experiments on some simple "freestanding" programs.

Oh lol, this will be funny.

emfader wrote:Hey guy

Which one?

I know all the OS concepts

No, you don't.

I want to start development but failing

This part can be easily interpreted as "I want to start failing development"; I assume this isn't what you meant.

I want to know how should I start, I am a good programmer, but I am not able to understand on where to start and get going.

If you were a good programmer, you would know where to start.

Should I refer some guide? or a book?
Please help/guide me.

I would suggest looking for the biggest link on this page.

I am not able to understand on where to start and get going.

Well, you know all the OS concepts, so it should be fairly obvious. Are you going to use paging? Then you'll want to set up the page tables pretty damn quickly. How about interrupts? There's something else you'll need to deal with right away. Set up a timer as part of that so that you can think about process switching. Then you'll want to print to the screen and read from the keyboard. Reading and writing disks will be handy, but you can probably leave that a while. Memory management will be pretty essential from the start, and then you can think about task switching.

That should keep you busy for the first week or so. You'll probably learn enough from that to sit down and think about what design you want for your OS. Monolithic; microkernel; somewhere in between?

I think you probably want to learn a bit more and come back when you have some specific questions. "Where to start" is just a little vague and shows a worrying misunderstanding of what you are trying to achieve. Think about what an OS is, what it does, and it should be easy (easy to know what needs to be done, but not necessarily to work out the best way to do it and then to implement that solution). You have read the Wiki, haven't you?

Here's a hint: When starting, you basically have two options:
Read over documentation,tutorials, etc. for a year before writing any working code (I picked this one, trust me, it starts out really frustrating), or quit (most common).

Also,

Hey guy I know all the OS concepts

You should write a book.

I want to know how should I start

Obviously, otherwise you wouldn't have come here.

I am a good programmer

Definition, please

Should I refer some guide? or a book?

It's the fourth link from the top of the page, giant text. Can't miss it.

Useful links:
wiki.osdev.org
Learn about os development
http://forum.osdev.org/viewtopic.php?f=1&t=16944
Forum rules, you broke 5 of 8
http://www.englishgrammarsecrets.com/
Learn english
http://www.google.com
You might find it useful

are we not allowed to link to the wiki?

Hi,

You can do http://wiki.osdev.org, or use the wiki tag like -- Main_Page.

Works here.

Regards,
Shikhin!

Hey, "find wiki link on this page" is kind of an IQ test, why link it directly?

I think we should add a "noob questions" subforum, and make it autodelete

Turns out this is his 7th topic with pretty much the exact same question.

I call a troll. At the very least he's consistently wasting our time.

You're right. I think the most telling thing is that each time he makes an OP then never returns to acknowledge any replies. Ah well, I suppose some people get their kicks that way.