OSDev.org

Hi, everyone!


I'm going to write a new operating system tutorial!
With all the information that is needed to write a os.
Like paging,gdt,idt,tss,multi processor support and so on.
I've only one problem, how should this tutorial be?

So my questions to everyone are:

What is important for you, more source code examples with short expliantions or
rather long explations with a little bit of source code?

Or should I mix it up. So it depends on the topic ?

I say an in-depth tutorial would be very good. But make sure you explain things fully, source code is always a good idea. Also when you start talking about things, IE memory address - try to provde a link that so that if the reader doesn't quite understand, there is always a link for him/her to read and get more of a understanding of what is going on.

Any type of tutorial is a good tutorial, usually Esp. when it comes to osdev.

Personally, I say anything that keeps the language basic and understandable, with clear and concise code behind it is good. You don't need to give code for everything, just the key points, in my opinion.

I think it's important to show all possibilities. Several tutorials concentrate only on what the developer chose and don't explore the alternatives. At the very least, mention alternatives and why you went with the approach you did.

I'm actually in the process of setting up to tut's myself. Sometimes their just as much challenge as writting the actual code

--Jeff

I hope i will finish the first part of tutorial in the
middle of december!