In the UK, university research departments are assessed base on the Research Excellence Framework (REF, formerly the Research Assessment Exercise [RAE]). Each faculty member is required to submit 4 things demonstrating impact. These are typically top-tier conference or journal papers, but can also be artefacts or examples of successful technology transfer. The exercise happens every four years, so to get the top ranking you need to write one good paper a year. The only incentive for publishing in second-tier venues is meeting other people who might lead to interesting collaborations.

Reproducing work is often a good thing to set for first-year PhD students to do. If they reproduce something successfully, then they've learned about the state of the art and are in a good position to start original research. If they can't reproduce it, then they've got a paper for one of the debunking workshops that are increasingly attached to major conferences and that's their first publication done...

They're the most current available...

X86 went away fifteen years ago. Every "x86" COU built since the last 1990s runs an x86 layer, but underneath is a very different bear.

At the time, the closest the DOS world had to multitasking was TSRs. Beside my first PC was my CoCo 3 with OS/9 level 2 with 512k of RAM with a true preemptive multitasking kernel running on an 8 but 6809 CPU. Microsoft's dominance at the time meant in many ways the most common 16 bit opposing system in the world was only marginally better than a CPM machine from 1980.

Predicting that x86 would go away was more wishful thinking than anything else. At the time, Intel had just switched from pushing the i960 to pushing the i860 and would later push Itanium as x86 replacements (their first attempt at producing a CPU that it was impossible to efficiently compile code for, the iAPX432, had already died). Given that Intel was on its second attempt to kill x86 (the 432 largely predated anyone caring seriously about x86), it wasn't hard to imagine that it would go away soon...

I found Modern Operating Systems better than the Minix book. The Minix book tells you exactly how a toy OS works in detail. Kirk McKusick's Design and Implementation of the FreeBSD OS (new version due out in a month or two) tells you how a real modern OS works in detail. Modern Operating Systems gives you a high-level overview of how modern operating systems work and how they should work. If you want to learn about operating systems, I'd recommend reading the FreeBSD D&I book and Tanenbaum's Modern Operating Systems and skipping the Minix book (which was also a bit too heavy on code listings for my tastes).

Minix has been BSD licensed for well over a decade. I'm not sure exactly how long, but it was when I was an undergrad and that was a depressingly long time ago now. As the kids today say: Old troll is old.

While this is true, it's worth noting that a lot of the compartmentalisation and sandboxing ideas that most of the userland programs on OS X employ (either directly or via standard APIs) have roots in microkernel research. OS X is in the somewhat odd situation of having userspace processes that are a lot more like multiserver microkernels than its kernel...

This is confusing in Brussels, because there is Université libre de Bruxelles (Free University of Brussels), but there is also Vrije Universiteit Brussel (Free University of Brussels), a different university.

Minix was really the first of its kind; a Unix-like OS that you could run on cheap (relatively speaking at the time) commodity hardware and that you could get the source code for. A lot of the computing we take for granted now comes from Tanenbaum's work.

My first Minix install was on a 386-SX with a whopping 4mb of RAM I borrowed from work back in the early 1990s. I quickly abandoned Minix for Linux once it came out, but for several years I had Minix running on an old 386 laptop just for fun.

I really miss the good old days when technical debates were over the merits and faults of such simple things as different kinds of kernels, and not about whether or not every single thing you do online is being stacked into half a dozen nation's permanent data storage facilities.

The Linus vs. Tanenbaum dustup is from a simpler, more positive age.

They're good at the animations and the easter eggs, but they lack things like a pause button which is really irritating if the phone or doorbell rings a little way into the video.

That's rubbish. Most of the major platforms have had Java ported to them. Including various obscure systems is ludicrous. If I want a program that I'm almost guaranteed will run without recompile on Linux, Windows, BSD and even many mainframes, then Java remains the best solution. I'm not saying, from a programming perspective, that it's all that great, but from a platform neutral perspective for most of the systems that a programmer will encounter, it remains the best.

Have fun running an x86-64 Linux binary natively on a Windows 8 machine. I can. however, write a Java program that I can almost guarantee will in fact run on x64 Linux or Windows.

No, it is popular because, despite a good many flaws, it remains the best cross platform solution we have.