Retirement of Prof. Andy Tanenbaum
cs.vu.nl
cs.vu.nl
Thanks Mr. Tanenbaum, your various works have been a huge inspiration as well as incredibly interesting to read or tinker with.
[1]: https://groups.google.com/forum/?fromgroups=#!topic/comp.os....
Of everything hypothesized-for-the-future in the thread, this turned out to be the least accurate prediction of them all :)
Hehehe.
- device drivers as processes (so you can actually debug them)
- increased security by isolating various parts of the core OS from each other
- easy scaling from single machine to cluster by message passing
- treating devices as networked resources
- file systems in userspace (which we have now with FUSE)
and so on.
The benefits of microkernels go a lot further than just being able to use multiple userlands.
The difficulties that microkernel projects ended up encountering were not easy to forecast and ended up taking virtually everyone by suprise.
It was in the spirit of progress towards better ways of architecture software that Tanenbaum and Stallman (as well as many others) chose to try a new architecture rather than just build yet another monolithic OS kernel. Being on the pointy end of technology means you often end up being the one to discover what doesn't work.
Haha :)
Since every microkernel in use (Windows NT and XNU, really) have taken much of their code monolithic, I think this is the true legacy of Tanenbaum's career.
Flamebait at its' worst, but acceptable because he was a respected member of the academic elite.
Also, it was Usenet. Flame wars were its bread and butter.
What is Tanenbaum's legacy? What microkernels are in use?
And in all honesty, Linux has adopted a number of elements over the years that would not have flown with the original fully monolithic kernels.
No, we don't have userspace drivers. (Apart from proprietary GPU drivers and a number of enterprise hardware systes .. and at least Canon printer drivers, and and and and ...) They're not isolated in the sense that microkernels would enforce but they provide a shim for the kernel and then do a lot of their processing in userland.
We can load and unload drivers at runtime. That's what insmod/rmmod do.
We don't do message passing between kernel components, but in order to prevent messaging from becoming a bottleneck we have signaling mechanisms, we have netlink, and we have $deity knows what else.
We DO have userspace filesystems: FUSE. I'm still waiting for userspace block device drivers but that's probably not going to happen. :)
What do we have with Linux then? Not a microkernel - just a very modular and runtime-modifiable mostly monolithic kernel instead. A hybrid? Ish?
I added a new question to my interview process a number of years ago. Anyone who put "computer science" on their resume get's asked "What do you think of Andrew Tanenbaum?" It's free-form question intended to see what about computer science interested them enough to remember; I have similar questions about Turing & Knuth. Our team requires a lot of broad knowledge and original thought.
If they don't know who AST is, the interview is probably over. We continue if they can discuss pretty much any of the 6-7 seminal, award winning CS textbooks he wrote, the other major projects he lead like the Amsterdam Compiler Kit or the Amoeba distributed operating system, or the other contributions he made to networking, distributed systems, languages, computer architecture, operating systems or information security (he did publish nearly 200 journal papers over 43 years as a professor). If they know about Electoral-vote.com, bonus points.
If all they can come up with is "Minix" and "that pissing contest with Linus", then I might see if the Linux devops guys have an opening. If they're that incurious, they'll do fine there; those guys think the world begins and ends with Linux, too.
Continuing in the "let me Google that for you" vein, both QNX and various L4 family microkernels are in use in a variety of embedded systems; QNX is also in the new Blackberry products. There's a number of very mature security oriented research microkernels (like L4se and K42) that could very well show up in commercial products eventually. But that's back to needing to know more about computer science than Windows and MacOS.
I'm sorry to be picking on you but this is one of the things that is absolutely wrong in our field: we don't learn anything from history. We don't know what was being researched in the 70's and proceed to reinvent the wheel over and over thinking we somehow have magical brains that are unearthing some concepts for the first time in human history.
The traditional CS curriculum should adopt a mentality of "ok, you now understand at which point in history we are in CS? Know most of the past inventions? Fine, now proceed to build on top of them and stop wasting everybody's time with your rediscoveries".
I pretty much agree with everything else you said, and I wish I knew more about the history of computing myself, since I've lost a lot of my memory of my college course on it to the sands of time. I wonder if there's a good survey book. Maybe AST wrote one...
Do you actually believe that someone is incurious simply because they don't share your own interest in Tanenbaum? Perhaps they've focused their curiosity on one of the many other luminaries in CS, or perhaps they're more interested in the topics themselves than the personalities behind them.
Your contempt for your own devops team is also disquieting. Based on your comment your company sounds like a toxic place to work.
As to devops, you may think whatever you want. I give them shit about the "all the worlds Linux" attitude, they give me shit about "fucking research projects" (e.g. anything that isn't Linux). We understand our respective views, and it works.
Well that's a lot more reasonable! Your original comment left no ambiguity that candidates insufficiently knowledgeable about Tanenbaum would be shunted over to devops.
> As to devops, you may think whatever you want. I give them shit about the "all the worlds Linux" attitude, they give me shit about "fucking research projects" (e.g. anything that isn't Linux). We understand our respective views, and it works.
That could be the basis of some good-natured ribbing, which would be OK. What's not OK for a healthy company culture is the suggestion that devops people are inherently incurious, and the strong whiff of intellectual elitism which came across in your original comment.
Let's be fair here. Your claim was that microkernels are "in general use". Ongoing research, however mature, does not support this claim. And Blackberry is hardly the heavy hitter they used to be. Meanwhile, the major OSs for computers as computers -- and as phones -- have backed away from the microkernel design. Maybe they shouldn't have; regardless, they did.
That leaves embedded systems. And there you have a point. So: microkernels are in common use in embedded systems. But let's not overstate their successes.
Actually, I don't think I disagreed with you, except to note that a research kernel that might be used someday, does not count as "general use".
You might count the insinuation of overstatement as a disagreement. The point of that is that context matters. When I talk about choice of OS, the Mac in my living room has rather more weight in my mind than the embedded controller in my garage; I know I'm not alone in this. So if we say only that microkernels are heavily used, then we are correct, but we will be misunderstood. It is better, I think, to make a statement that is both correct and understandable, than to make one that is merely correct, while looking down on those who misunderstand.
EDIT: A quote[1] from me, giving an example from a rather different topic:
> If I open up a restaurant that serves General Tso's chicken and chop suey and sweet and sour pork and fortune cookies, and I advertise that I serve "American food", then my description is accurate, but my customers will be confused.
[1] http://www.reddit.com/r/todayilearned/comments/25dji0/til_ge...
This is pretty much exactly what I'm selecting against. It's not that your concept of "general use" in computer science excludes embedded systems (frightening, considering you're apparently teaching this stuff). It's that when more than one poster tells you that you're wrong, and provide concrete examples of why, your response isn't "that's something I need to consider" or "perhaps my knowledge of the field isn't what I thought it was" or best "I've got more to learn". Nope, you decide the "context" of the discussion is whatever you want it to be and to trot out a contrived bit of sophistry which boils down to "I might be wrong, and I'm not saying I am, but because lots of other people would be wrong, I get to be right". Or something. Doesn't matter. We weren't opening a restaurant.
Double bonus points for focusing on a throwaway, tangential comment and pretending it's a central flaw of argument. This clearly isn't your first specious Internet argument.
Besides, QNX works very well on PC hardware and is used extensively in the communications industry.
Please do not take your own limited exposure to the world of IT as proof that certain things are true, especially when they are emphatically not. I know of several thousand QNX installs within 10 km from where I'm sitting.
Denying the success of micro kernels such as QNX by disqualifying applications is like claiming linux is a failure by excluding mobile devices.
Most things that use QNX or other OS's like that inside simply work rather than that they require constant upgrades and bug fixes. Reliability by design is so much better than reliability by trial and error, and the OS is a huge factor in that. It's a world where bugs are felt as 'egg on your face' rather than a 'wontfix'.
It should probably be Prof. Tanenbaum or at least Dr Tanenbaum.
Thanks for your comment!
Ever get so broke that the bank charges you money for not having enough money? The bank calls up and says "Hi, we're calling because you don't have enough money." And you go, "I know!" So they say, "You have insufficient funds." "Yep, that's a good way of putting it too, I'd agree with that. I find my funds to be grossly insufficient." "You only have $20, so we're going to have to charge you $15." Fifteen dollars, that's how much it costs to own $20. But here's the fucked-up part — now I only have five. Now I don't even have the money that I paid to have.
I think Tanenbaum's joke is a good example of this sort of humor.
It amazes me that the majority of computer related books I've read are really not fit for human consumption. It's really refreshing to see that he understood this and made his work and lectures - I've seen a few on YouTube - as engaging and entertaining as possible while still being clear and concise.
Code is for computers, but in the end, programming is for humans.
It would be nice if we could just plug a crystal ball into
a free PCI slot to help out with the prediction,
but so far this approach has not borne fruit.
Lacking such a peripheral,
various ways have been devised to do the prediction. [...]I remember him describing Intel's primary design consideration in developing the Pentium processor series as being "1. Backwards compatibility. 2. Backwards compatibility. 3. Backwards compatibility."
On another note, Linus Torvalds described "Operating Systems: Design and Implementation" as "the book that launched me to new heights".
Many people were standing in the back, but it looked like there was one seat left in the first row, a few seats in. I proceeded to walk up, force everyone to stand up and politely asked everyone to move so I could use the last seat. Some old crusty professor didn't hear me , so I had to explicitly ask him to move.
About 1 minute later the crusty old professor stood up, walked back behind me and started his speech :). Oops. All my classmates asked me afterward WTF was wrong with me...
So, I'm sitting there reading and a crowd starts to gather. I look up and a bunch of people are looking at me. There's this older gentleman closer than the others. Then, it dawned on me, it was Poul Anderson. Oops. There to sign copies of his new book.
>Hi Professor,
>I'm interested a PH.D in Amsterdam. I have worked in
>Accenture Italy since one year.
>There are a opportunity to PH.D in your study group?
>Best Regards ..
After 5 minutes
>I don't have any openings. Sorry
>Andy Tanenbaum
This is a simple mail, but I liked his courtesy and fast response
At the VU, Andy Tanenbaum gave a lecture on operating systems, and handed out floppy disks with Minix at the end. All I knew then was DOS. Mind blown. Thank you ast!
So, in all respect a well-deserved retirement... and I guess that retired or not doesn't stop him contributing to the CS field. Well, he will have less Ph.D.-students, so more time to writing, programming and lecturing!
Also, I had no idea that he was the creator of http://www.electoral-vote.com/
So is this book the type of OS book that is fantastic knowledge for technical people to really know about their computer or is it really just aimed at those that want to move into OS development?
Modern Operating Systems is an amazing book but it works at a somewhat higher level. You'll basically read about stuff that happens, or might happen, in an operating system. You'll learn about threading, the elevator algorithm, dining philosophers, how virtual memory works, how a memory allocator works, and a bunch of other stuff.
It's a very well written textbook. The thing that struck me was the way it introduces things at a theoretical or high level and then trusts students enough to present them with real C code and real problems to solve on the next page. Just an excellent textbook.
I teach OS using MOS, and give this advice to (several hundred by now) students.
It's an extraordinarily written textbook. For me there are 2 types of technical books - the ones that I have to plow through with sheer willpower, and the ones that I read kinda like an interesting novel. Tannenbaum's book falls in the latter category.
I have a clear memory of my first Minix[1] boot. It was in an old PC-XT (Intel 8088) with 640Kb of RAM and 10MB Hard drive. Coming from MS-DOS, this was pure black magic to me.
Minix3 has adopted/is adopting parts of the NetBSD codebase (packages, libc, coreutils, etc etc) and is closer to the *BSD platforms than ever before. It can be considered a BSD microkernel nowadays.
There's still a lot to do and packages to port/features to add, but it's getting there. Since the release of Minix3 (I think it was in 2007) the project has gone more towards the pragmatic and practical world, instead of just academia.
Good stuff.
Signing up for farewell lecture now...
My ageist perspective here is that what you're describing takes a bit of work and most "older" profs can't be arsed to do that work, so the simplest explanation is that he just still runs an old computer :)
From Computer Networks Book DNS section
"Take the pro domain,for example. It is for qualified professionals. But who is a professional? Doctors and lawyers clearly are professionals. But what about freelance photographers,piano teachers, magicians, plumbers, barbers, exterminators, tattoo artists, mercenaries, and prostitutes? Are these occupations eligible? According to whom?"
But his words still echo in my mind. Modern Operating Systems and Computer Networks , both extremely well written. They certainly did taught me alot.
Here is to Prof. Tanenbaum , Thank you sir , for teaching me .Even though i've never met you nor i may ever meet you in this life but you should know that some guy from South Asia is thanking you from the bottom of his heart.
Is that really true?
"In 1991, while attending the University of Helsinki, Torvalds became curious about operating systems[31] and frustrated by the licensing of MINIX, which limited it to educational use only. He began to work on his own operating system which eventually became the Linux kernel.
Torvalds began the development of the Linux kernel on MINIX and applications written for MINIX were also used on Linux. Later, Linux matured and further Linux kernel development took place on Linux systems.GNU applications also replaced all MINIX component" http://en.wikipedia.org/wiki/Linux#Creation
The Aula at the VU is pretty big and I hope there will be enough space for everybody, but regardless they won't complain if non-students join as well (at least I assume so).
I really wanted to attend as well, but unfortunately I will be away from the country in those dates, you can take "my place" if you want :P
And it would not surprise me if they relocate the lecture to a bigger auditorium nearby, if interest or registration goes way beyond 900.