Ideas for a book
Posted: Wed Jan 11, 2012 11:12 am
Hi,
Since whenever I became a little more experienced in OS Dev (not that I am much experienced now, but I guess I've improved), I've been toying with the idea of writing a lengthy tutorial to get someone started well in OS Dev. However, my idea wasn't to write something which was standalone - one could pick it up, and write a OS in a week. My idea was to write something which taught how to make important design decisions - such as Own bootloader vs GRUB, and benefits of both. Then, I'd branch off to: A one-stage bootloader vs a multi-stage bootloader or something; and a Intermediate Loader after GRUB vs simply the kernel and so on and so forth. Similarly, for the kernel, I could do Microkernel vs Monolithic and the benefits and such.
Of course, the above would be a very very thick book, and would be time consuming. What I was thinking was to base it on my OS - so, I describe the other alternative briefly, and then dive into the alternative I choose. Currently, I do maintain a small notebook, in which I keep my ideas and stuff. I draw flowcharts to think about algorithms and write about decisions I made that day. Similarly, I could maintain another notebook which would be this "book", in which I'd add major designs each day.
tl;dr I'm thinking of writing a book on OS Dev - more of a long tutorial on DESIGNING a OS, and not WRITING one. What do you think about the idea?
Regards,
Shikhin
Since whenever I became a little more experienced in OS Dev (not that I am much experienced now, but I guess I've improved), I've been toying with the idea of writing a lengthy tutorial to get someone started well in OS Dev. However, my idea wasn't to write something which was standalone - one could pick it up, and write a OS in a week. My idea was to write something which taught how to make important design decisions - such as Own bootloader vs GRUB, and benefits of both. Then, I'd branch off to: A one-stage bootloader vs a multi-stage bootloader or something; and a Intermediate Loader after GRUB vs simply the kernel and so on and so forth. Similarly, for the kernel, I could do Microkernel vs Monolithic and the benefits and such.
Of course, the above would be a very very thick book, and would be time consuming. What I was thinking was to base it on my OS - so, I describe the other alternative briefly, and then dive into the alternative I choose. Currently, I do maintain a small notebook, in which I keep my ideas and stuff. I draw flowcharts to think about algorithms and write about decisions I made that day. Similarly, I could maintain another notebook which would be this "book", in which I'd add major designs each day.
tl;dr I'm thinking of writing a book on OS Dev - more of a long tutorial on DESIGNING a OS, and not WRITING one. What do you think about the idea?
Regards,
Shikhin