To view parent comment, click here.
To read all comments associated with this story, please click here.
For instance, you can see how x86 cpus are handled - loading the OS into protected mode, switching tasks, security rings. Interrupts are handled almost exactly like in any other Unix like system. Drivers tend to be different at a high level, but if you look at them close up they would be similar. There's a primitive scheduler. Etc.
If you're looking at the overall architecture then maybe it wouldn't be the best place to start, but there are tons of details that are more interesting IMHO. After all, you can learn the basic architecture really quickly - it is the details of how things work that takes a while to learn.
Edit:
I have to admit I never really read through the book itself - the class I took spent most of our time going through the code at the end with the rest spent on slides/lectures my professor made. So perhaps if I was just going through the text I would think differently.
Edited 2007-03-02 00:02
If you're looking at the overall architecture then maybe it wouldn't be the best place to start
Can you reccomend somewhere better, then? Right now, my primary goal is learning architecture.
If I ever want to create my own OS or work for someone else on theirs, I need to be able to understand architecture. If I know what I am doing, even if I write bad code to start, I can work on it it and improve it until it is good code; but if I can't see the 'big picture' to understand what my code needs to be doing, then all my work will be in vain.







Member since:
2007-02-22
Luckily, Mr. Tanenbaum's book is not the only one available to me. Operating System Concepts has been a much better reference, and compares more concepts in cleaner language, instead of presenting the-One-True-Design.
I dare hope that it's not that I'm not trying hard enough; this is what I've wanted to do since I was a little kid, and it's what I'm paying $50K/year to get a degree for!