Page 1 of 1

Book Recommendation

Posted: Sat Apr 27, 2002 11:40 pm
by ACK
Hey, I was referred to your forum from a user of another. I am looking into creating an operating system and instead of re-typing all of the details again please see this thread: http://www.visualbasicforum.com/showthr ... adid=25337

I am looking for a book that will deal with the concepts of operating systems, if it is any help to choosing a recommendation I am a visual learner. As a result graphics and diagrams would aide me greatly!

Re:Book Recommendation

Posted: Sun Apr 28, 2002 1:26 am
by hrr
A great book for OS programming is :
"Operating Systems - Design & Implementation 2nd Edition" by Andrew Tanenbaum & Albert Woodhull. It is the same book used by the creator of Linux. It comes with a CD which contains the source & binaries of MINIX 2.0. The book also contains printed source-code of MINIX. The book is good for beginners as well as experienced programmers.

Re:Book Recommendation

Posted: Sun Apr 28, 2002 11:01 pm
by K.J.
Not a book recomendation, but a "how-is-this-book" question(since this post is about books).

Is Modern Operating Systems by Andrew S. Tanenbaum a good book?

http://www.amazon.com/exec/obidos/ASIN/ ... 06-5630356

Thanks in advance,
K.J.

Re:Book Recommendation

Posted: Mon Apr 29, 2002 7:01 pm
by Tim
I can't admit to having read it, but I flicked through it in the bookshop the other day. It looks like an updated version of OS:D&I: no Minix source code, but a lot of details on modern operating systems.

Re:Book Recommendation

Posted: Tue Apr 30, 2002 8:54 am
by ACK
I will get a copy of Operating Systems - Design & Implementation 2nd Edition ASAP.

Thank you for your recommendations.

By the way, this is a great community for OS developement!

Re:Book Recommendation

Posted: Sat May 18, 2002 1:20 pm
by crazybuddha
Beware. There are two very distinct issues in hobby OS development. One is controlling the hardware. The other is "higher level" issues of task control. You will experience a lot of frustration tackling the second without having a solid codebase for the first.

The problem (in my view) with learning from *nixes is that they are very much concerned with process control. I say start with monotasking DOS and learn to love the idiosyncracies of Intel architecture.

In either case, there are a ton of examples out there to be learned from.