The Design and Implementation of the FreeBSD OS
n0dez writes "Peter H. Salus has written a review of The Design and Implementation of the FreeBSD Operating System on UnixReview.
"If you need to understand just how a kernel works, you need this book. McKusick and Neville-Neil have done the community a favor, and this book deserves to be a best seller." This book is an update to The Design and Implementation of the 4.4BSD Operating System by Marshall Kirk McKusick."
I was considering getting the 4.4 version of this book so I'm glad I waited. I've been working through the Tanenbaum OS Book and it's a bit dry. I've been working through the 2.4 Linux Kernel as well. It's amazing the quality that goes into these open source offerings.
I just wish someone would make a linux distro that is more like OS X. It would bring Linux to the desktop faster and give grandma an interface she could easily understand.
Is this book mainly code, or is it mainly theory? I'd like to get a book that explains the guts, but I really don't want to spend days looking at page after page of code on paper.
However, no amount of hinting got me this as a birthday present.
However, my gf *did* get me a mess of other cool stuff- a new GeForce video card, a pile of video games for PC and PS2 (she's always telling me that i need to play more games....), some Lego...
No worries though.. I'm sure to pick this up myself anyways.
do() || do_not();
"I'm looking at running a modified linux kernel on x86, x86-64, PPC & Itanium"
Assuming your goal is to create a pretty desktop OS like OS X, why would you run it on Itanium? Itanium is designed specifically as a "RISC killer" for high-end RISC/UNIX shops (and it's failing miserably, I might add). To my understanding, OS X Server isn't even the same code-base as normal OS X. Supposedly it's more NeXTish. The point is that Apple's servers don't really run the same OS that their desktops and laptops do.
It always strikes me as funny when Linux people whine about the lack of a Linux distribution that works like OS X. Hmmm, maybe that's because Apple pays developers market wage to create their interface, rather than relying on community contributions by random, unaccountable people? Also, it seems that the Enlightenment WM is really supposed to mimmic OS X, so perhaps the lament should be "I wish there was a WM..." rather than "I wish there was a distro...". Besides, if you recognize that OS X is so much better, why don't you just buy a system with OS X? Do you not believe in paying for quality, or should everything just be handed to you on a silver platter?
Then again, that's the problem with the Linux community. Instead of contributing towards a common project and common goals, everyone goes off and totally duplicates the effort of everyone else. You end up with dozens of WMs, dozens of text editors, dozens of e-mail clients, a dozen web browsers, hundreds of OSs (that's what a distro is, after all) and not ONE of them approaches the quality of a commercial OS.
If free software is ever going to approach the quality of commercial software, people have to stop this assinine "I'll start my own ___" mentality and learn to work in productive teams. The Apache web server and OpenSSL should be examples of how to do things. There aren't 10 different common SSL implementations in Open Source.
Getting slightly back on topic, BSD should serve as a good example for how to do OSS right. Have large groups of developers working on an integrated project, i.e. a whole OS. Pick one default for everything, and don't duplicate effort all over the place. There are only really four free BSDs (Dragonfly, Free, Net, Open) and they share code heavily. The default installations have one sane selection for each task, and you can add more from ports if you really, really feel like it. Development is a lot more cohesive and as a result, the BSD releases tend to work a lot more reliably. Imagine that!
Someone is WRONG on the Internet!
I saw it in a "complete family tree of UNIX", which I'm furiously trying to locate. I also found http://www.macintouch.com/mxs.html which near the very top is talking about how the interface is heavily NeXT and not like traditional Mac OS, granted it's quite old information, but that tends to confirm what I gathered informally from other sources.
Note that both OS X and OS X server are heavily based on BSD, but it seems (again, from informal observation) that the consumer version is much more FreeBSDish and the server version is much more Machish.
I'll try to find some better info when I get home.
Someone is WRONG on the Internet!
To my understanding, OS X Server isn't even the same code-base as normal OS X. Supposedly it's more NeXTish.
.edu) and Unlimited-client for $1000 ($500 .edu). Client restrictions only affect simulataneous Mac and Win file sharing, so many shops just use the 10-client version.
OS X Server 1.0 came out over a year before the OS X Client. At the time of Server's original release it was basiclly a Mac-flavored version of NeXT OPENSTEP. Apple's client OS at the time was still classic Mac OS 9 (or was it 8.6?).
When Apple released Mac OS X 10.0, with the Aqua GUI and all of its refined NeXTisms, they replaced the original OS X Server with one based on 10.0. This trend has continued today with 10.3 and soon, 10.4.
The only differences between Server and Client today are the inclusion of more open source daemons and apps, optimized configurations, and some (really snazzy) closed source management tools. Remote admin can be done via a remote shell (BSD derrived), web interface, or from another Mac using the management apps. Server comes in two flavors: 10-client for $500 ($250
http://www.apple.com/server/macosx/
If you have an older Mac that doesn't support Mac OS X, or if you have an x86 PC (or if you have a semi-modern Mac but don't want to pay for an upgrade to 10.3 Client or Server), you can install Darwin, the open-source core of Mac OS X. It's basiclly Apple's NeXTish BSD distribution, but based on the Mach kernel and using NetInfo to manage configuration. You won't get the Aqua GUI (but you can use straight X11) nor the GUI admin tools, but everything else will be about the same.
Perhaps the coolest thing about Darwin is the fact it's opensource -- driver and utility coders love this, there aren't too many secrets when the core OS has open code.
So falling $13B short of expected sales and shipping less than 6,000 units in Q2 is considered a success? The only vendor to ship over 300 units was HP. Compare that to say, Apple who shipped 13,000 Xserves, which arguably are the biggest competitor to Itanic in the clustering market for universities and super-computer centers. If we look at the Opteron, that shipped 60,000 (of course it's usually not a direct one to one vs. Itanic, but you get the idea).
For over a decade of R&D and combine billions from Intel and HP, that has to be a major failure. Just the fact that they're adding 64bit extensions to Xeon shows you that Itanium is failing to gain the server market share that they planned on and now they have to plug the holes by beefing up their low-end server gear.
Now comes news from IDF that HP is adding more Opteron kits to it's lineup with 4 way boxes and blades. Hmmm, that doesn't sound like a company that has faith in Itanium to me, and they were the second largest investor!
There is of course the old saying "no one ever got fired for buying IBM", but I wonder if in a few years there won't be a rash of firings for "buying Intel" when Itanics platform support is still lagging terribly behind other architectures.
Someone is WRONG on the Internet!
so, where's the edonkey/bittorrent/... link to a pdf version?
That's not a surprise. Everyone knows mandrake is 'linux for your granny.'
cheap labor conservatives - they want to keep you hungry enough to be thankful for minimum wage.
Here's a sample chapter about process management.
cpghost at Cordula's Web.
When the book came out in Germany, I got my pre-ordered copy. It's a great book, not for its choice of OS, but for its writing style.
;)
I have no problem with FreeBSD, or anti-BSD bias, I'm just trying to say that this is surely the best-written book about a recent operating system kernel available, and I'm enjoying reading it.
It certainly beats "Understanding the Linux kernel", again not for its choice of OS, but for its style. It explains more, and doesn't hassle you with platform dependent assembler code. After all, most of the OSs are written C, why bother in an "introductory" book?
Given how much fun I have reading this book, I'm not pleased with this quick, incomplete review I cannot make anything of. Do I learn anything about the book? I guess not. There are great reviews out there, like for "Embedding Linux", where you get a detailed list of things the reviewer notes about the book, and where he found issues with it, and what he liked. Man, this is for sure shorter than the Amazon sales pitch, and sadly enough, not very relevant as well. Sampling a few facts from a book is not a review!
Oh, buy this book! It's worth every penny! Since I'm not a reviewer I do not bother adding any evidence to this statement, as this are only my 2 cents.