Slashdot Mirror


Andy Tanenbaum on 'Who Wrote Linux'

Andy Tanenbaum writes "Ken Brown has just released a book on open source code. In it, he claims (1) to have interviewed me, and (2) that Linus Torvalds didn't write Linux. I think Brown is batting .500, which is not bad for an amateur (for people other than Americans, Japanese, and Cubans, this is an obscure reference to baseball). Since I am one of the principals in this matter, I thought it might be useful for me to put my 2 eurocents' worth into the hopper. If you were weren't hacking much code in the 1980s, you might learn something." Tanenbaum's description of the interview process with Brown is classic. See also Slashdot's original story and Linus' reply.

668 comments

  1. I like the last bit by gowen · · Score: 4, Interesting

    where, ten years after he first had this argument, he still feels obliged to rag on Linux's design as a monolithic kernel as a bad design decision. This from a man who describes true multitasking and multi-threaded I/O as "a performance hack."

    Bitter much?

    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    1. Re:I like the last bit by Anonymous Coward · · Score: 0, Funny

      hmm, shall i listen to gowen's opinion, some guy I've never heard of or Andrew Tanenbaum, UNIX god.

    2. Re:I like the last bit by Anonymous Coward · · Score: 0

      His .0s is down after 3 minutes and 3 posts. Talk about multi-threading.

    3. Re:I like the last bit by madprof · · Score: 2, Insightful

      And there are no well-respected programmers who would agree with that point of view then?

    4. Re:I like the last bit by MemoryDragon · · Score: 5, Interesting

      Actually, since the interview is not reachable anymore, I assume it is right what you said. But Tannenbaum is right in his sense, a Makrokernel does not really make that much sense, it is easier to program because you simply have method calls instead of messages, but you run into driver compiles, crashes due to the strong binding etc... Mach at least in its early incarnations was not the best example of a Microkernel, neither is the vaporware hurd, which probably will be finished in about 100 years, but improved Mach kernels derived from newer incarnations already have shown how powerful and stable the concept can be, Two words:AIX and MacOSX both based on Mach kernels and both excellent and fast operating systems.

    5. Re:I like the last bit by Anonymous Coward · · Score: 5, Informative

      ...and to make them perform reasonably well, both of these have hacks (server collocation, etc.) that remove the whole reason for microkernels in the first place.

      Don't fall for the hype.

      On the other hand, QNX is actually pretty true to the concept.

    6. Re:I like the last bit by 91degrees · · Score: 1

      where, ten years after he first had this argument, he still feels obliged to rag on Linux's design as a monolithic kernel as a bad design decision

      Well, a lot of people will argue that microkernels are better.

      This from a man who describes true multitasking and multi-threaded I/O as "a performance hack."

      And you disagree with this? Why?

    7. Re:I like the last bit by gowen · · Score: 5, Insightful

      Well, there are certainly benefits to a modular micro-kernel design. I wouldn't deny it (and haven't). But there are also drawbacks (message passing is terribly hard to make secure in a multi-tasking context, and is frequently slower than dirt. Add to that some of the braindead design decisions of the x386 w.r.t. privileged processes...) Yuck.

      Treating the micro v. monolithic debate as a solved problem ("microkernels win!") is as idiotic as suggesting that object orientation is the ideal solution to all programming problems.

      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    8. Re:I like the last bit by gowen · · Score: 5, Insightful
      And you disagree with this? Why?
      Because if you want any kind of decent performance out of a server system you need both those things. Otherwise you've got a couple of designed-in bottlenecks to throughput. Now *that's* a braindead design decision. Of course, its completely understandable in the context of MINIX's design as a teaching system, but to deride those features in other OS's as "a hack" is just pure prejudice.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    9. Re:I like the last bit by Anonymous Coward · · Score: 0, Flamebait

      I disagree that OS X is an "excellent and fast" operating system, after having used it in a server environment for the past 18 months. They are quite crash-prone.

    10. Re:I like the last bit by brunson · · Score: 4, Insightful


      I think he made such a big stink about it during the infamous flame war that, even if it was somehow proven that a macro-kernel is a better design, Tanenbaum could never back down from his premise without losing face.

      --
      09F911029D74E35BD84156C5635688C0
      Jesus loves you, I think you suck
    11. Re:I like the last bit by IamTheRealMike · · Score: 1, Interesting
      I must have missed the part where the MacOS X kernel was fast. I believe when Miguel de Icaza first compiled Mono on an Apple laptop which was faster than his desktop PC, the compile took almost twice as long (don't have a citation, it was a blog entry some time ago).

      Basically, Mach has had severe performance problems especially with things like file I/O, which they are now "fixing" the same way Microsoft did with NT, by moving some servers in kernel.

    12. Re:I like the last bit by Anonymous Coward · · Score: 1, Funny

      Treating the micro v. monolithic debate as a solved problem ("microkernels win!") is as idiotic as suggesting that object orientation is the ideal solution to all programming problems.

      ...because obviously object oriented programming is adds a terrible amount of overhead to any program without adding substantial usability to the code, especially as it's implemented today.

      It's a shame so much work has gone into writing OO languges when all that would could've gone to improving C. </joke>

    13. Re:I like the last bit by Tarantolato · · Score: 4, Interesting

      Treating the micro v. monolithic debate as a solved problem ("microkernels win!") is as idiotic as suggesting that object orientation is the ideal solution to all programming problems.

      Apparently, the really trendy kids have decided that microkernels themselves are obsolete, and moved on to something called exokernels. I can't pretend to understand the distinctions involved.

    14. Re:I like the last bit by Anonymous Coward · · Score: 0

      Remember that Windows uses a microkernel, and Windows is rather fast. Not many platforms are faster when it comes to hardcore gaming ;)

      Even if you do not like Windows or Microsoft or whatever, it still shows that microkernels are good.

      There are many other benefits and security does not have to be bad. Why should it be? Users should not have direct hardware (driver) access in the first place.

    15. Re:I like the last bit by cyb97 · · Score: 4, Insightful

      Performance of the compiler is probably more guilty when it comes to overall performance than the kernel. Further you are comparing apples with oranges comparing a Mac to a PC when it comes to compiling...

    16. Re:I like the last bit by Anonymous Coward · · Score: 0

      You'd figure he'd have a lot of face to lose by latching onto it and refusing to let go.

    17. Re:I like the last bit by holviala · · Score: 2, Interesting
      improved Mach kernels derived from newer incarnations already have shown how powerful and stable the concept can be, Two words:AIX and MacOSX both based on Mach kernels and both excellent and fast operating systems.

      I have no idea about OSX, but calling AIX fast is about the same as calling Windows user-friendly. Most people think it's like that but once you actually try do do something the truth reveals itself.

      I used to run my own server on AIX on a pretty fast RS/6000 and it was rediculous. I finally replaced it with a slow Duron with Linux which ran abour orders of magnitude faster (and cost about 1/20 of the RS). I also benchmarked Linux on the same RS6k and got 2x the performance compared to AIX on compilations.

    18. Re:I like the last bit by kfg · · Score: 4, Insightful

      Bitter much?

      Perhaps, just perhaps mind you, he is simply stating what, in his opinion, is true.

      KFG

    19. Re:I like the last bit by gowen · · Score: 1
      he is simply stating what, in his opinion, is true.
      Of course he is. But the merits of microkernels v. macrokernels are not really germane to the argument, so why does he feel the need to reopen the argument, unless he's bitter than no-one took any notice of him last time?
      IMHO, it spoils what is otherwise a superbly written article.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    20. Re:I like the last bit by Sunda666 · · Score: 5, Informative

      Windoz had a microkernel in the NT 3.51 days. It is way far from a microkernel today. There are some info about this on the NT 4 resource kit documentation.

      cheers.

      --


      ``If a program can't rewrite its own code, what good is it?'' - Mel
    21. Re:I like the last bit by CustomDesigned · · Score: 5, Informative
      Exokernels reinvent IBMs VM system. "An Exokernel securely multiplexes the raw hardware, and application libraries directly implement traditional OS functions." This does not mean that applications must now include their own drivers for every possible hardware they might use. It means that drivers can now be packaged as shared libraries in user space rather than as kernel modules.

      To summarize, let me call the part that securely multiplexes hardware the "kernel".

      • Monolithic makes drivers share address space with the "kernel".
      • With Microkernel, "kernel", drivers, filesystems, applications, etc each get their own address spaces.
      • Exokernel makes drivers share address space with applications. (Hopefully, filesystems get their own process and address space.)
      As you can see, as soon as you start partitioning applications into separate processes for security and robustness, the distinction between Exokernel and Microkernel becomes rather vague. The advantage of the Exokernel or VM approach is that you get the flexibility of keeping things like filesystems in a separate process for security and robustness, and things like video drivers in the same address space for performance. You might even have an X server as a separate process, but still allow full screen mode games that directly call the driver libraries for performance.

      IBM's VM was never that popular in its raw "Exokernel" mode with drivers in application space. However, it is still hugely popular as a way to run multiple Operating Systems as the "applications". Your mainframe can securely run multiple instances of S/390 Linux and traditional mainframe systems together.

    22. Re:I like the last bit by arkanes · · Score: 5, Insightful
      I've re-read that old flameware a few times over the years. It's kinda interesting how one reason he derides the performance hack is that "you don't need them", because normal PCs only have one job running. Certainly nobody envisioned the kind of systems we'd be running today (note the comment about 10 years from now when we're all on 200mips 64MB sparcs. That'd barely qualify as a toaster today....), but Linux rose to the challenge, Minix pretty much didn't. I think the freedom of Linux had alot to do with that (and he misses the point during the flamewar on that, too).

      12 years ago, who would have imagined that it is normal and in fact essential for a desktop OS to be able to smoothly handle many IO intensive processes at the same time?

    23. Re:I like the last bit by Anonymous Coward · · Score: 0
      But the merits of microkernels v. macrokernels are not really germane to the argument

      Actually, they are, as this is the easiest way for Tannenbaum to demonstrate that Linux is not a simple ripoff of Minix and to contradict Brown's claim that it was such a ripoff. And as others have pointed out, Tannenbaum's criticisms of Linux on the technology front make it harder to ignore his arguments on the legal front.

    24. Re:I like the last bit by Thinman · · Score: 0

      I think MacOSX is FreeBSD Derivate not Mach derivate.

    25. Re:I like the last bit by gowen · · Score: 1
      It's kinda interesting how one reason he derides the performance hack is that "you don't need them", because normal PCs only have one job running. Certainly nobody envisioned the kind of systems we'd be running today
      But someone in that thread does say:
      "But what if I want to run X, have a compile running in one terminal and read netnews in the other?"
      (I'm paraphrasing, but thats the jist of it). And thats pretty much *exactly* what I'm doing now, so someone had some foresight, anyway.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    26. Re:I like the last bit by Tony-A · · Score: 1

      Bitter much?

      I didn't read it as such.

      This from a man who describes true multitasking and multi-threaded I/O as "a performance hack."

      It it's anywhere as hard to get everything right as I think it is, Tanenbaum is right. From the standpoint of teaching the stuff, I'd say that Tanenbaum's stand is very defensible and you can't fault Tannenbaum for defending it.

      This doesn't mean that Linus is wrong. A useable system has a different set of priorities than a teachable system.

      The quote I liked best was:
      [Butler Lampson] "Is there anybody here who couldn't write CTSS in a month?" Nobody raised his hand. I concluded that you'd have to be real dumb not to be able to write an operating system in a month.
      Writing an OS is not that big a deal. I've done it and I'm nowhere near those guy's league.

    27. Re:I like the last bit by kfg · · Score: 2, Insightful

      . . .so why does he feel the need to reopen the argument. . .

      The argument was never closed.

      He brought the issue up for exactly the reasons stated, to explain why, despite some people's feelings, that he and Linus are not "enemies."

      In other words, that he has nothing to be bitter about, so his "defending" Linus isn't in any way anomylous. Seemed perfectly natural to me, and he took the same "dig" at Windows.

      KFG

    28. Re:I like the last bit by chez69 · · Score: 2, Interesting

      What a bunch of crap. how old was the RS/6000 and what was the model? how much memory did it have?

      --
      PHP is the solution of choice for relaying mysql errors to web users.
    29. Re:I like the last bit by gowen · · Score: 2, Insightful
      Actually, they are
      No, they're not. It would suffice to say "MINIX's design and Linux's design" are quite different.

      Tanenbaum basically says "MINIX's design and Linux's design are quite different, and MINIX's is unarguably superior." Theres just no need for that second clause.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    30. Re:I like the last bit by gowen · · Score: 1
      From the standpoint of teaching the stuff, I'd say that Tanenbaum's stand is very defensible
      I agree, but to criticise Linux for not being designed as a teaching tool, when that was never one of its design criteria, is a little perverse, to say the least.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    31. Re:I like the last bit by Anonymous Coward · · Score: 0

      Hrm... good post, but in no way is Mac OS X "fast". Tried running it on a 200 MHz processor with 32M RAM? It can't, and even if you coerced it to, it'd be unusable (see the recent PearPC discussions).

      You can still run Linux, BSD, Syllable etc. very nicely on those kinda boxes. OS X may be nice, but it's a big monster and is there to sell more Macs.

    32. Re:I like the last bit by Jeremy+Erwin · · Score: 4, Informative

      One reason that Minix did not "rise to the challenge" is that Tannenbaum wanted to keep his OS simple, for didactic reasons. Linux designed his OS to run on his new 386 computer, which had all sorts of nifty capabilities-- memory protection, a 32 bit address space, etc. Tannenbaum thought it was important to run run on on low end (student) hardware

    33. Re:I like the last bit by Anonymous Coward · · Score: 0

      I love my Mac, but MacOSX is anything but fast. Multimedia run smooth as silk, but the general OS feels sluggish.

      I think a better speed example would be QNX.

    34. Re:I like the last bit by Sajarak · · Score: 3, Informative
      but Linux rose to the challenge, Minix pretty much didn't.

      To be fair though, he primarily wrote Minix for educational purposes, with the idea that a computer science student could read and understand the entire system within the duration of a one-semester course. He refused to add a lot of features which would have made Minix harder to understand, even though they would have made it more useful.

    35. Re:I like the last bit by Anonymous Coward · · Score: 0, Informative

      both.

    36. Re:I like the last bit by arkanes · · Score: 2, Interesting

      I'm aware of that and it's addressed in the flamewar. The freedom of Linux is one thing that allowed this - if Tannenbaum (and PH) and allowed forks, then Minix could have had all this without compromising the educational aspects. Further, today, all that stuff IS on low end student hardware and yet Minix doesn't have it.

    37. Re:I like the last bit by Tony-A · · Score: 1

      but to criticise Linux for not being designed as a teaching tool, when that was never one of its design criteria, is a little perverse, to say the least.

      "I still fervently believe that the only way to make software secure, reliable, and fast is to make it small. Fight Features."
      This requires an unrelenting and possibly unreasonable stance.

      There's two kinds of Microsoft Windows users.
      One kind has screensavers and desktop wallpaper.
      The other kind does not.
      Guess which kind gets all the viruses and worms.

    38. Re:I like the last bit by maitas · · Score: 1

      In fact, back at university I implemented the "nice" command for MINIX 2.0 and it hard part was to pass the message from userland to the scleduler (which previosly I had modified so it sorts the process qeue according to the priority).

    39. Re:I like the last bit by jedidiah · · Score: 1, Insightful

      >> Certainly nobody envisioned the kind of systems
      >> we'd be running today

      Total BULLSHIT. By that time, we already had seen mini-computer systems go from the size of a large refrigerator to a single IC. Any CIS prof that couldn't see "beefier PC's" coming in 1991 should have turned back in his PhD.

      By 1991, PC's were already running a class of cpu that could be described as "VAX on an IC". Only slightly beefier CISC machines were running as Sun Workstations.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    40. Re:I like the last bit by jedidiah · · Score: 2, Insightful

      Bullocks!

      The cheaper machines (not clones) were MORE likely to have 32bit addressing and memory protection. Kludge Klones were more expensive and behind the curve (as usual).

      --
      A Pirate and a Puritan look the same on a balance sheet.
    41. Re:I like the last bit by k98sven · · Score: 1

      This from a man who describes true multitasking and multi-threaded I/O as "a performance hack."

      Now that is just unfair, and taken completely out of context.

      The context he was talking of is of the old 16-bit PC systems, which had no hardware support for multitasking. And in that context, he is correct, and he's not making a secret of the fact that Minix was designed to run on low-end machines.

      Linux, on the other hand, was 386-only.

      So what the heck is the point in holding that quote up against him?

    42. Re:I like the last bit by gowen · · Score: 1

      Actually, the real context is damning. His real reason for damning multitasking for MINIX is "no-one on a home PC will ever want to run more than one job at a time."

      People who reason like that have no grounds for criticising other people's design decisions.

      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    43. Re:I like the last bit by Anonymous Coward · · Score: 0

      There's two kinds of Microsoft Windows users.
      One kind has screensavers and desktop wallpaper.
      The other kind does not.
      Guess which kind gets all the viruses and worms.


      Um... I'm finding it hard to follow you.

      Are you saying that the ones who don't have screensavers get all the viruses because they're too clueless to set up a screensaver? That can't be right, because so many viruses have proliferated by claiming to be screensavers.

      So are you saying that the ones who do have screensavers get all the viruses? But I can prove that wrong too. I have a screensaver, a rather nice one in fact, I wrote it myself. My Windwos computer has also never had a virus.

      So what are you trying to say? Please explain.

    44. Re:I like the last bit by Profane+MuthaFucka · · Score: 5, Insightful

      Thirteen years ago, I didn't give a flying FUCK about how outdatated Linus' monolithic kernel was. Remember, we were all running DOS, and desperate to break out of real mode hell.

      Arguing about monolithic versus microkernel was like arguing about whether a starving man's meal should be vegetarian or not.

      --
      Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
    45. Re:I like the last bit by Anonymous Coward · · Score: 1, Insightful

      I love how Linux zealots like to rant about "freedom" and then get their panties in a twist when someone uses their freedom of speech to criticize Linux.

    46. Re:I like the last bit by wolf31o2 · · Score: 1

      No, no... my favorite is the last 2 words.

      Fight Features.

      If that doesn't say a lot about how he would see computing today, I don't know what does.

    47. Re:I like the last bit by Minna+Kirai · · Score: 3, Insightful

      Theres just no need for that second clause.

      Sure there is. It adds detail, and makes the speaker more credible, because it proves that the topic is actually something he cares heavily about. Demonstrating passion is a way to quickly prove that although your beliefs might not be perfectly correct, you've at least spent a lot of time and effort researching them, and are thus an informed source.

      And from another perspective: show that he is still antagonistic to Linus's system gives him even more credibility. If a friend vouches for you, that might be discounted as a buddy covering for you- but if an enemy says you're innocent, then he's got no motivation to lie on your behalf.

      (This reminds me in a roundabout way of Iraq today: the US Army "raiding" Chalabadi's headquarters, and he's publically "upset" about it. But they could've really been trying to help him gain power in Iraq, because the common people won't trust a leader who's too friendly to the USA. An OT example of how people can be easier to categorize by counting their enemies rather than their supporters)

    48. Re:I like the last bit by Anonymous Coward · · Score: 0

      That AIX is a microkernel architecture is news to me. There was, in the mid-nineties, a project at IBM to make AIX run on the IBM Microkernel (an OSF Mach derivative). That project was abandoned, AFAIK. AIX is a monolithic kernel.

    49. Re:I like the last bit by cosmo7 · · Score: 5, Funny

      Further you are comparing apples with oranges comparing a Mac to a PC

      I object to your comparison between apples and oranges and Macs and PCs. Equating apples compared to oranges with Macs compared to PCs is like comparing comparisons between euphemisms with comparisons between idioms.

    50. Re:I like the last bit by Anonymous Coward · · Score: 1, Informative

      He is telling that Linux was 2x faster on *that very hardware*.

      Who's the bunch of crap now?

    51. Re:I like the last bit by 0racle · · Score: 1

      ...easier to program

      Tell that to the Hurd people who are now 14 years over-due for a kernel.

      --
      "I use a Mac because I'm just better than you are."
    52. Re:I like the last bit by mrchaotica · · Score: 1

      MacOSX has a Mach microkernel, but everything is running as one big monolithic service, so it doesn't matter anyway

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    53. Re:I like the last bit by Anonymous Coward · · Score: 2, Informative

      NT 4.0 moved away from microkernel by putting window management and graphics subsystem into the kernel. It was because of performance measurements done at the time on the hardware that existed at the time. Unfortunately these measurements were a snapshot in time - hardware became much more powerful and over time proved moving the gui subsystem into the kernel was shortsighted and unnecessary.

    54. Re:I like the last bit by Jeremy+Erwin · · Score: 2, Informative

      Minix ran on 8086 computers. 20 bit memory. No memory protection.

      I still remember reading in Byte about the first 486 machine-- a rather expensive, bulky system, too exotic for personal use. After a few months, more economical systems were gradually introduced. It was a far cry from today's market, where the usual response to a new x86 incarnation is to benchmark it against "Serious Sam" and "Quake 3".

    55. Re:I like the last bit by cshark · · Score: 1

      I remember when I first started creating web pages, there were people that insisted that there can never be any layout of any kind other than flat paragraphs and line breaks in a hyper text document in order for it to remain true hypertext.

      Well...
      I'm not going to say they were wrong either. But those guys that started in the begining of things had a different take on things.

      Kind of the same way the next generation will consider your ideas about the way things work to be wrong, misinformed, or... quaint.

      --

      This signature has Super Cow Powers

    56. Re:I like the last bit by buzzdecafe · · Score: 3, Interesting

      Treating the micro v. monolithic debate as a solved problem ("microkernels win!") is as idiotic as suggesting that object orientation is the ideal solution to all programming problems.

      Tell that to Tanenbaum:

      From: ast@cs.vu.nl (Andy Tanenbaum)
      Newsgroups: comp.os.minix
      Subject: LINUX is obsolete
      Date: 29 Jan 92 12:12:50 GMT

      ". . . While I could go into a long story here about the relative merits of the two designs, suffice it to say that among the people who actually design operating systems, the debate is essentially over. Microkernels have won . . ."

      Cited from here

    57. Re:I like the last bit by Anonymous Coward · · Score: 0
      Yeah, and RISC kicks CISC's ass. Right?

      (clues for clueless; modern processors are all hybrids, as are most real-world OSes).

    58. Re:I like the last bit by Bull999999 · · Score: 1

      I agree with this statement. Back then, GNU people still didn't have a kernel and BSD people were caught in a lawsuit. That left Minix as a contander for a free UNIX clone. He didn't allow it to be a free replacement for UNIX and Linus stepped in. And the rest is history.

      --
      1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
    59. Re:I like the last bit by 13Echo · · Score: 4, Funny

      I personally prefer nanokernels. A nanokernel is a (kernel * 10^-9). It works out as being much smaller and faster, since a microkernel is only (kernel * 10^-6). Yeah, yeah? Let's see if Andy Tanenbaum can explain that one! Soon, Linux hackers will be jumping ship because they will be 1337 enough to write a PICOKERNEL!

    60. Re:I like the last bit by Jeremy+Erwin · · Score: 1

      Maybe he was trying to teach to clueless students. Perhaps he didn't have a clue.

      Perhaps the european market was flooded with old 8086 clones.

    61. Re:I like the last bit by chez69 · · Score: 1

      he also said
      I used to run my own server on AIX on a pretty fast RS/6000 and it was rediculous. I finally replaced it with a slow Duron with Linux which ran abour orders of magnitude faster (and cost about 1/20 of the RS)


      that is what I was calling BS on. As far as linux being faster on the same hardware, I can believe that. Twice as fast, well that is less believeable.

      --
      PHP is the solution of choice for relaying mysql errors to web users.
    62. Re:I like the last bit by cduffy · · Score: 1

      Microkernels are not necessarily slower than dirt -- just poorly implemented ones (the HURD being a prime example).

      See VSTa for a counterexample.

    63. Re:I like the last bit by cduffy · · Score: 1

      That's just the HURD people being idiotic.

      Folks with better design sense have implemented their own microkernels with vastly better performance and in far, far less time.

    64. Re:I like the last bit by CountBrass · · Score: 1

      20/20 hindsight is easy.

      What contribution have you made, ever, to advancing computer science? Is it significantly more than Tenabaum's? Is it on par? Have you made *any* contribution at all?

      --
      Bad analogies are like waxing a monkey with a rainbow.
    65. Re:I like the last bit by shaitand · · Score: 1

      I believe he's talking about that class of user on windows who has just enough of a clue to break things.

      There are users who know what their doing, there are users who have no clue and don't claim to, there are users who have half a clue and believe they have a full clue and those who do have a full clue are special geniuses and wizards.

      It's the last class that is most dangers, they download and run all kinds of junk, things like incredimail, weatherbug, kazaa. They are the ones who pass around joke mails that feed mail viruses lots and lots of addresses, most non-CS/engineering college students fall into this category.

      These users generally waste time setting up a screen saver and pretty background, usually one they downloaded from the net. Where most advanced users (who haven't written a screensaver for themselves) turn off every piece of desktop prettiness they can because it improves system performance. And because as a rule, the less that's running the more secure the system is.

    66. Re:I like the last bit by arodland · · Score: 1

      Honest question: Does OSX actually use the microkernel architecture, or does it use the sort of monolithic-on-top-of-microkernel setup I've seen before, which makes the microkernel just a convenience layer, but doesn't bring any of the most commonly touted advantages?

    67. Re:I like the last bit by LO0G · · Score: 3, Informative

      Um. NT4's still got the same kernel architecture that NT3 had.

      The only difference is that in NT 4, the GDI and USER components were moved from user mode (in CSRSS.EXE) to kernel mode (as the Win32K.Sys device driver).

      Having the GUI running at ring 0 is not the same thing as having a monolithic kernel.

    68. Re:I like the last bit by k98sven · · Score: 3, Insightful

      Actually, the real context is damning. His real reason for damning multitasking for MINIX is "no-one on a home PC will ever want to run more than one job at a time."

      If by "home PC" you mean an Intel x86 machine, and put that into the context of way things were looking around 1990, that is an entirely reasonable standpoint. Not very many people ever did do much multitasking on 386es.

      Most people around then (myself included) did not think the x86 architecture was going to hang around much longer. It is quite clear that Tanenbaum shared the majority view at the time, that RISC was the way to go.

      Also, the design goals of MINIX, clearly stated by Tanenbaum, (see his book, I've read it.) was for MINIX to be an educational tool, and run on low-end (e.g. 286) PC:s. He was not planning MINIX to be a production-quality system. He did not want to add 386-specific features.

      You should not dismiss Tanenbaum so lightly, he most likely is far more knowledgeable on these subjects than you or I. It's like saying Einstein was a moron because he didn't grok quantum theory.

      I don't know, perhaps you're a Linux zealot who wants to believe that Linus is always right. But the reason this entire debate is so well-known is that both sides raise valid points. The difference is in their intentions and design goals, not in the facts.

    69. Re:I like the last bit by Sunda666 · · Score: 2, Informative

      but it a'int a microkernel either, eh? (think QNX).

      cheers.

      --


      ``If a program can't rewrite its own code, what good is it?'' - Mel
    70. Re:I like the last bit by Anonymous Coward · · Score: 0

      And that's "insightful"? No, people are criticizing him for ruining otherwise good article by doing unnecessary and self-serving soap-boxing at the end. No one said he shouldn't be allowed to do, many have commented it sounds like sour grapes.

    71. Re:I like the last bit by Anonymous Coward · · Score: 0

      Why must people post stuff without checking the facts first?

      The information on the web would be of a much higher quality if people actually bothered to search first. How about reading an article on NT design next time before posting about it?
      http://www.winntmag.com/Articles/ArticleID/29 84/pg /2/2.html

      A few corrections from someone who has used and follow NT design from since the word go:

      NT was *always* a microkernel. The first release was NT 3.1, so therefore the statement ".. in NT 3.51 days" is kind of silly.

      Secondly even though they have moved some drivers into ring 0, this does not make it "far from a microkernel".
      It is in fact *still* a microkernel design.

    72. Re:I like the last bit by Zebidiah · · Score: 0
      That's so true!

      My partner's daughters tend to install everything not nailed down. Not necessarily a bad thing if you want to learn how to use a computer and you don't mind re-installing the OS, but for the most part they just want frills and eye candy.

      One of them thinks it is cool if there PC gets a virus. I've set-up their systems as best I can (firewall, virus killers, user/admin accounts) and threatened to disconnect them from the Internet, but they still manage to get infected! I feel sick just thinking about the shit they put on their PCs.

    73. Re:I like the last bit by LO0G · · Score: 1

      Did I say it was? I just said that the architecture of the kernel didn't change when they moved the gui stuff into kernel mode.

    74. Re:I like the last bit by Nurf · · Score: 5, Interesting

      Treating the micro v. monolithic debate as a solved problem ("microkernels win!") is as idiotic as suggesting that object orientation is the ideal solution to all programming problems.

      I'll agree with that. However, I can say that for the stuff I do, microkernels win. I've written a microkernel RTOS for an embedded system, and it had the following advantages for me:

      1) It was easy to write. (Very modular)
      2) It is easy to maintain. (Very modular, and because all interaction is done with messaging, you dont worry about the code you are doing now interacting in some unknown way with something else. ie. You can ignore the rest of the system except for the messages you send to it)
      3) It is easy to give it strong deterministic real-time response. This is a big thing for me in the applications I use it for. Data ends up flowing from one task to another, and I just have to make sure my scheduler doesn't mess that up.
      4) The overhead introduced by message passing was negligible (The RTOS was implemented to replace an existing system, and did so comfortably)
      5) Its really easy to make stable and reliable systems, because everything is chopped up into small well understood sections with well defined interaction between sections.

      Microkernels might have slightly lower throughput than monolithic macrokernels, but I am not running a batch transaction processor.

      For desktop use, I want controlled latency and reliability. I don't feel that Linux gives me all that it should in those departments, though I use it because it is better than most (with some patching). Kernel modules feel like the worst of both worlds to me.

      So, given the priorities I stated above, I think I would prefer a microkernel OS, all other things being equal. I'd jump ship from Linux to one, if most other things are equal.

      Other people will have other priorities and I encourage them to use whatever works for them.

      --
      ---
    75. Re:I like the last bit by Sunda666 · · Score: 3, Interesting

      To be 100% fair, it never was a microkernel anyway. But in the 3.x days the NT kernel was small enough to pass as a microkernel (falsely, eh, based on the sheer size/complexity alone). But GUI performance sucked, and had some issues (regular users being unable to change the desktop resolution due to the lack of priviledges comes to mind), and since windows is all about the GUI, they decided to put the GUI (and a lot of other drivers too) in kernelspace. So, now it is not a microkernel, and the kernel is not small anymore.

      Peace.

      --


      ``If a program can't rewrite its own code, what good is it?'' - Mel
    76. Re:I like the last bit by IamTheRealMike · · Score: 0, Redundant

      Well, they are both gcc, so only the backend and assembler is different - the overhead of compiling C is mostly parsing and the tree manipulations, iirc. Oh, and creating lots of processes/files.

    77. Re:I like the last bit by RAMMS+EIN · · Score: 1

      Which is mind boggling. What ARE they doing?

      Seriously, I can write a kernel in a day, in x86 assembly. Give me a week and I can make it do proper multitasking and write a shell and a few proof of concept apps. What's keeping them?

      --
      Please correct me if I got my facts wrong.
    78. Re:I like the last bit by Sunda666 · · Score: 2, Interesting

      No it is not. It may be a "microkernel in design" as you say, but it is not "microkernel in implementation". If it was a real microkernel, some random shitty soundcard driver would not be able to crash the entire OS, like it usually happens. And of course it would not have the video/audio/3d performance it has today. True microkernel == too much context switching, which is a show-stopper (at least in x86)

      peace.

      --


      ``If a program can't rewrite its own code, what good is it?'' - Mel
    79. Re:I like the last bit by Tokerat · · Score: 1


      Well, then perhaps you can point me to a good site detailing how to get Linux running on an RS since I have two in my basement that are just itching to be hooked up.

      --
      CAn'T CompreHend SARcaSm?
    80. Re:I like the last bit by doug_wyatt · · Score: 3, Interesting

      Actually, with most of the exokernels that actually existed in the wild, even things like the filesystem and the network stack existed within the process of the application using it. For apps that shared the same implementation, they'd use a shared library - a purely performance hack so that the text segments didn't use up lots of memory. But each app could chose to implement their own version. You could think of an Exokernel as a monolithic kernel except that the abstractions that the kernel present to the process are much lower level (e.g. disk blocks and packet filters) than with traditional monolithic kernels (e.g. files and sockets). The main premise of Exokernels was that OS's have traditionally, secured hardware resources, multiplexed hardware resources and abstracted hardware resources - the first two are good ideas, but the last one is better left up to the application since it knows what it's doing with them.

    81. Re:I like the last bit by holviala · · Score: 2, Interesting
      What a bunch of crap. how old was the RS/6000 and what was the model? how much memory did it have?

      It was a 43P-140 with a 332MHz 604e, half a gig of memory. Of course it's slow now, but back then 604e's were standard RS6k CPU's and the 332 was the fastest of them (I know, I worked with SP clusters @ IBM at the time and ALL had 604e CPUs). The Duron was... umm... a 600MHz one with 128 megs of memory (and yes, a few years younger than the RS6k). With the RS/AIX my load was around 40 every day and the machine was unusable - with the Duron the loads were under 1.

      I don't know what you do to your AIX machines for them to be fast (neither do the guys @ IBM), but even the POWER4's that I administer now are slow. The floating point performance is excellent, but that's about it. They're no use for any real work - even the Sparcs we have are faster (and they're pathetic too).

      Me - I switched to x86 hardware with Linux and haven't looked back.

    82. Re:I like the last bit by holviala · · Score: 1
      Well, then perhaps you can point me to a good site detailing how to get Linux running on an RS since I have two in my basement that are just itching to be hooked up.

      Try Google. You'll need a special kernel, but the userspace stuff from Debian works wonders.

    83. Re:I like the last bit by Anonymous Coward · · Score: 1, Informative

      Um, but it is compiling for different instruction sets, which is a different task.

      Perhaps if you were cross-compiling for intel on the mac the number comparison would mean something.

    84. Re:I like the last bit by strobert · · Score: 3, Insightful

      very true. also, Tanenbaum I think ignores the kernel module and abstration layers in the kernel. one of the points of a message passage system is to have proper interfaces defined so that subsystems can be replaced and interchanged. For people that have watched kernel development over the years, those design benefits are basically in the Linux kernel. yeah it may be "monolithic" in the OS kernel theory deisgn aspect, but it incorporates the design abstrations of a "microkernel" without the performance hits (for the most part on both counts).

    85. Re:I like the last bit by jayminer · · Score: 1

      While yes, it is easier to program (except the core), it's hard to keep it secure for running mission critical jobs running on user space instead of kernel space (which are by nature, far more relatively secure), but it is not impossible.

      Keeping things simple is the fashionable new way of 90s and 2000s. Look at qmail, or other simple but secure/robust/fast/insert_favorite_software_engine ering_objective_here programs by DJB (even though they are structural).

      Look at Object Oriented Programming (yes, it was available before, but not that widely used). Makes it great for a group of programmers safely (without killing each other) develop a complex system, consisted of numerous very simple parts.

      Andrew Tanenbaum is surely a smart guy. He has thought of things many could still not think of.

      It's very hard to make things change in academic minds (I have a slight academic background), but this guy had revolutionary ideas back then.

    86. Re:I like the last bit by cyb97 · · Score: 2, Informative

      but who says gcc is equally efficient on both PPC and x86?
      It might be for all I know, but it's certainly more likely that it's gcc being a troll rather that the actual mach kernel being slow...

    87. Re:I like the last bit by jonadab · · Score: 1

      The real win would be getting the kernel into hardware (i.e., making it part
      of the CPU's microcode). Then you could claim that your operating system
      software doesn't even *need* a kernel!

      --
      Cut that out, or I will ship you to Norilsk in a box.
    88. Re:I like the last bit by jimfrost · · Score: 1
      Two words:AIX and MacOSX both based on Mach kernels and both excellent and fast operating systems.

      MacOS X, clearly, but AIX? I believe you are mistaken about AIX being a Mach derivative. It sure as hell doesn't look anything like Mach to me. My guess would be "SysIII derivative". That seems most likely since AIX predated OSF/1 and SysV. This opinion appears to be supported by information exposed in the SCO/IBM lawsuit.

      I think the only other commercial Mach derivative currently in production is Tru64, aka Digital Unix, aka OSF/1.

      --
      jim frost
      jimf@frostbytes.com
    89. Re:I like the last bit by JudgeDredd · · Score: 3, Funny

      I think you may have misinterpreted his sentence structure. Let me put some brackets to clarify the logical structure:

      Further you are comparing apples with (oranges comparing a Mac to a PC)

      So, what we have is a comparison between (the fruit called an apple) and (the act of an orange comparing two other things). Clearly these things are, in fact, different! One is a fruit doing nothing and the other is an action by a fruit.

    90. Re:I like the last bit by jedidiah · · Score: 1

      Guess again.

      If anything, Europe had a lower concentration of overpriced lame ass x86 clones. They simply had less disposable income to throw away on such shenanigans.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    91. Re:I like the last bit by Marxist+Hacker+42 · · Score: 1

      I agree with the point of view that microkernals would be more stable; but it seems the public doesn't like stability compared with the "Load Everything Once Use Some Many" macrokernal model, in that Linux, OSX, and Windows basically have the desktop market sewn up; and MINIX is still just a educational example. What is good programing does NOT equal what people will pay you to program.

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
    92. Re:I like the last bit by maximilln · · Score: 1

      The clued users who know what they're doing are okay.
      The clueless users will have a vanilla system which may get infected but are, generally, okay.
      The half-clue users who think they have a full clue are certainly obnoxios and dangerous.

      There's another class of users that I've come across lately: former Mac users. In the sense of their general ability to use a computer they can be like the clued users (pretty savvy) or the clueless users (don't know, don't care, can do enough to get the job done). In the sense of their ability to _maintain_ a computer and choose proper software, however, these people are as bad as the half-clue users.

      Take my new manager. He's a former Mac user. He's accustomed to having the Mac world spoonfeed him with everything that he needs. He's accustomed to the operating system taking care of all management tasks for him. He doesn't know the different between good software and bad software with an important sounding name. Whenever we need a piece of software for a task he'll go back to some old pedant and get a suggestion for a piece of software written by a virtuoso on some estate in the middle of a Californian vinyard. Ihe Mac world this was okay. The Mac world was full of snobby virtuoso's living in vinyards and they generally did have the best handle on which software to use with their Mac. I feel like knocking his head in and saying,"Hello, Dr. Self-Important Ex-Mac user... WE'RE NOT IN THE MAC WORLD ANYMORE!" Generally, following the Mac trend for choosing Windows software ends up with several hundred installed pieces of crippleware, a mangled registry, and lots of broken apps that aren't maintained with the regularity that's necessary to keep up-to-date on the Windows platform.

      Essentially, having an ex-Mac user as a manager is forcing me, a clued user, to function like a half-clue user. I end up being told to install every nifty little app because "that's what we need to do the job." If I ever suggest a different app, perhaps one that's better maintained or better focused, he immediately runs back to his private group of ex-Mac using Ph.D.s to use their collective opinion to override anything that I may have to say about functionality.

      Me: "We really don't want to use that software. The functions are clumsy, it has a poor layout, and it won't integrate well with the other systems that we're trying to put into place."
      Dr. Mgr: "Well, I talked with Dr. So-and-so, and so-and-so, who's an expert with 15 years of experience, and so-and-so that teaches at such-and-such University, and Dr. So-and-so who works at Such-and-such, Inc. and has been doing this kind of work for 30 years, and they all agreed that _MY_ choice is a good tool."

      I could strangle his ex-Mac using neck.

      --
      +++ATHZ 99:5:80
    93. Re:I like the last bit by tietokone-olmi · · Score: 1

      Filesystems, the TCP/IP stack, memory management, overdesign. I suppose in roughly that order.

      But hey, I've installed a Debian GNU/Hurd computer once. It wasn't very fun (clearly very much in a development stage), but it worked far enough for me to read a few comments from bash.org in w3m from the console.

    94. Re:I like the last bit by EddWo · · Score: 1

      With Longhorn its moving back the other way. GDI is coming out of kernel space. Graphics device drivers will no longer have to implement GDI drawing accelerations and will concentrate entirely on Direct3D. All GDI operations will be performed in software within the applications process, and then passed through to the Desktop Compositer as a bitmap used as a Texture by Direct3D.
      This will reduce the performance of GDI operations, but they are only being kept on for legacy applications. New Longhorn applications will use the new Avalon model which will be renered entirely using the 3D graphics pipeline.

      See "Windows Longhorn Display Driver Model" session presentation from WinHEC.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    95. Re:I like the last bit by hunterx11 · · Score: 1

      Actually OS X is based on a Mach microkernel, just like NeXTSTEP was.

      --
      English is easier said than done.
    96. Re:I like the last bit by Alsee · · Score: 0, Redundant

      Using some clever optimizations I was able to squeeze my femtokernal into a single bit.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    97. Re:I like the last bit by smittyoneeach · · Score: 4, Insightful

      I contend with the characterization of the last para as 'ragging'.

      The tone I got was of an affectionate tip o' the hat to what is surely one of the all-time classic flame wars.

      Besides, when you >make menuconfig, and you go through there and choose whether you want various bits compiled into the kernel or loaded as modules,

      isn't that an admission that the 'truth' on the modular/monolithic argument falls somewhere in the mote in the eye of the Tannenbaum/Torvalds Tempest?

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    98. Re:I like the last bit by EddWo · · Score: 2, Informative

      See Here for the white paper explaining the move to place GDI and USER in kernel space.

      The example they give is that the 3D pinball game runs great on Windows95 but terrible on NT 3.5 on the same hardware. Putting GDI in kernel mode was important to bring NT up to equivelent performance. Personally I think they found they couldn't get Win95s more complicated shell to run fast enough on NT, and they wanted to have the same environment on both Consumer and Business OS after all the Marketing that Windows 95 got.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    99. Re:I like the last bit by metamatic · · Score: 2, Interesting

      "We" weren't all running DOS, though.

      I was running Atari TOS. AST's microkernel design ran on my Atari ST and gave me a working Unix-like system. Linus's hack only ran on the 386, and was useless to me. Arguing that it was superior when it only ran on a machine I didn't have was pointless.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    100. Re:I like the last bit by Anonymous Coward · · Score: 0

      "No, people are criticizing him for ruining otherwise good article by doing unnecessary and self-serving soap-boxing at the end."

      So the "good" part of the article supports Linus and the part that "ruins" it is critical of Linux. It sounds like the only appropriate content from your perspective is pro-Linus, pro-Linux.

      In my view, Tanenbaum did Linus a big favor by setting the record straight. Don't look a gift horse in the teeth.

    101. Re:I like the last bit by twd20 · · Score: 1

      soon the linux kernel will be so big, it will become possible to have a picokernel...

    102. Re:I like the last bit by Marxist+Hacker+42 · · Score: 1

      Thanks for the correction- if I had actually read the comments closer, I would have noticed that one sooner. So, given the incredible speeds of hard drives and microprocessors today, what's the boot time for the Macintosh crowd? 1s, with most of that the time it takes to wake up the hard drive?

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
    103. Re:I like the last bit by Anonymous Coward · · Score: 0

      I've already written a picokernel. Here's the source:

      0000 JMP 0000

      I haven't quite got the multitasking code working properly, but it boots... and in only three bytes!

    104. Re:I like the last bit by bored · · Score: 1

      I worked at IBM a few years back, and there are definitly some things you don't want your AIX box doing. One of those things is paging. The pagining performace on a RS6k box (4.3.3) that should have been about 3x (faster processor, faster disks etc) was about 1/10 what an old Ppro with a crappy IDE disk was getting running linux (2.2) at the time. Recently though, the newer versions of linux have gotten a lot slower, and the 64-bit version of AIX faster, so that may not be true anymore.

    105. Re:I like the last bit by Ost99 · · Score: 1

      Disk I/O tends to be a bit slower on laptops.

      Most laptops have *slow* 2.5" disks (4200rpm), while most desktops have fast(er) 3.5" disks (7200 - 10000 rpm).

      Seek times for 2.5" disks are only a bit higher than for 3.5" (12-15ms vs 8-10ms), but transfere rate is much slower (10-20MB/s (30MB/s burst) vs 30-60 MB/s (80-100MB/s burst)).

      --
      ---- Sig. gone.
    106. Re:I like the last bit by pb · · Score: 1

      um. In that case, I suggest you switch from ethernet to token ring, and get a very large SRAM device to replace your HD. That is to say...

      Just using a microkernel will not give you any sort of controlled latency on the desktop, and I suspect you know this as well. :)

      --
      pb Reply or e-mail; don't vaguely moderate.
    107. Re:I like the last bit by Anonymous Coward · · Score: 0

      screw all y'all. i got the goods on an attokernel architecture... i can't say much but it involves superstring theory.

    108. Re:I like the last bit by Nurf · · Score: 1

      Just using a microkernel will not give you any sort of controlled latency on the desktop, and I suspect you know this as well. :)

      Well, it is my experience that it is fairly simply to control latency in such systems. In linux it is being done using horrible hacks that complicate the code and make modifications to affected areas error prone. Also, I feel comfortable blaming linux and not my IO devices for my latency issues - my mouse shouldn't stutter just because there is disk IO.

      I am not talking about waiting for IO, so much as if it doesnt tie directly to the process I am using, it shouldn't affect me.

      I'm not saying that a microkernel will give me low latency for free, but it would give developers the opportunity to implement it without quite so many headaches. :-)

      --
      ---
    109. Re:I like the last bit by drinkypoo · · Score: 1

      So if you have an SMP system which has more processors, thus more contexts (or even a hyperthreading intel chip) and thus less switching, does the cost of using a microkernel go down? And further, does that mean that the age of the microkernel is fast approaching, since it's starting to look like parallel computing is finally coming? Never before have multiple-core processors been available as commodity items.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    110. Re:I like the last bit by Jeremy+Erwin · · Score: 1

      Ah, but if you had a Amiga or Atari ST, you couldn't install Linux on it, but you probably could install Minux.

      The debate is obsolete, though. LInux has modules, so it's not quite as unwieldy on low end machines. Linux has been ported to many architectures, though the x86 arhitecture has sort of taken over, so portability isn't as desirable as it once was. And the technologies that Tannenbaum regarded as exotic are now commonplace.

    111. Re:I like the last bit by Anonymous Coward · · Score: 0

      Actully it's a BSD Fork.

    112. Re:I like the last bit by Pseudonym · · Score: 2, Interesting
      But there are also drawbacks (message passing is terribly hard to make secure in a multi-tasking context, and is frequently slower than dirt.

      While I take your point on security, to be fair, in a decent modern microkernel, message passing is a highly optimised operation. In fact, the kernel is usually optimised for precisely two tasks: scheduling and message passing. When that's pretty much all your kernel does, there are a few implementation tricks that you can use which avoids a lot of machinery that you'd otherwise find in your kernel.

      Moreover, a point which is not always appreciated is that monolithic kernels often have similar costs. You still have to copy data from user space to kernel space and back again. Compare this with a modern microkernel which copies directly from address space to address space. The microkernel still needs to swap tasks, but a) it's trivial to schedule, and b) only on the x86 is swapping tasks expensive, and sometimes not even then (e.g. using L4's small address space optimisation).

      IMO, microkernels and monolithic kernels are so different as to be almost incomparable.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    113. Re:I like the last bit by Anonymous Coward · · Score: 1, Funny

      Holy shit! *brain explodes*

    114. Re:I like the last bit by Pseudonym · · Score: 1
      Microkernels might have slightly lower throughput than monolithic macrokernels [...]

      "Throughput", defined as the amount of work that the system can do just prior to being overloaded, is not the quantity that everyone wants to optimise for. Performance when you are overloaded, or latency when you're not, can be more important in some systems (such as yours).

      Just thought I'd mention this, because not a lot of people understand what "throughput" is, and even fewer can tell when it's important and when it's not.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    115. Re:I like the last bit by Anonymous Coward · · Score: 0

      Well said, this is one of the best FP's ever.

    116. Re:I like the last bit by pyrrhonist · · Score: 1
      Seriously, I can write a kernel in a day, in x86 assembly. Give me a week and I can make it do proper multitasking and write a shell and a few proof of concept apps.

      It's not on Freshmeat yet. What's keeping you?

      --
      Show me on the doll where his noodly appendage touched you.
    117. Re:I like the last bit by EvilTwinSkippy · · Score: 1

      Well, the Mach kernel is available for x86, the Linux kernel is available for PPC. Run the same app under BSD and Linux on both architectures. QED.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    118. Re:I like the last bit by Anonymous Coward · · Score: 0

      AIX is *not* Mach based. However, there was an internal IBM project for a Unix-like personality running on Mach. This was based on the OSF/1 code-base and was called WPX.

      The reason it didn't get anywhere was the same age-old debate of monolithic vs. microkernel. Monolithic AIX was much more efficient than WPX, so eventually WPX was killed.

    119. Re:I like the last bit by EvilTwinSkippy · · Score: 1
      Which is mind boggling. What ARE they doing?

      Seriously, I can write a kernel in a day, in x86 assembly. Give me a week and I can make it do proper multitasking and write a shell and a few proof of concept apps. What's keeping them?

      Probably the fact they thought they could write the kernel in a day and it was only going to take a week to write...

      I program for a living. Writing something in a week doesn't impress me. Writing something that is useful for more than a week, that is what seperates the mental fappers from the real programmers.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    120. Re:I like the last bit by EvilTwinSkippy · · Score: 1
      When my mom does dumb stuff like that I threaten to reformat her machine into Linux.

      She is addicted to CivIII, and there is no Linux port. She behaves after that for a few months...

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    121. Re:I like the last bit by Anonymous Coward · · Score: 0

      I still have an RS/6000 N40 notebook (PPC601/50 MHz/32 MB) running AIX 3.2.5, and performance of X/Motif/Netscape2 is perfectly acceptable. This configuration tends to be about as fast as RedHat 6.2 running on a P100 (i.e. an x86 with twice the clock speed).

      If you're content with pretty old and obsolete hardware, try a 601-based PowerPC like a Model 230 or 250. These can run AIX 3.2.5, which beats the pants off any other Unix on raw performance, including Linux, with very limited memory footprints (16M to 32M is fine). AFAIK, the 601 topped out at about 100 MHZ, so that's where it ended.

    122. Re:I like the last bit by Anonymous Coward · · Score: 0

      now I am hungry- thank you very much.

    123. Re:I like the last bit by cammoblammo · · Score: 1

      I hope you checked the definitions of the micro- nano- and pico- prefixes. I'm really not in the mood for a micki- nani- and picbi- debate right now.

      --

      Cogito, ergo sig.

    124. Re:I like the last bit by Crazy+Eight · · Score: 1

      Well, presumably Miguel was using gcc on both platforms. I would blame a laptop hardrive before I blame the compiler.

    125. Re:I like the last bit by Crazy+Eight · · Score: 1
      I don't know about that. Keep in mind that Darwin is a hybrid of Mach and BSD. This page about Mach describes early attempts at such a union and characterizes the performance as "absymal". Understand, I'm not saying gcc isn't the culprit. I'm only saying it isn't unreasonable to wonder if Apple's kernel might have a hand.

      Update! I just found de Icaza's blog entry. Check it out here (that's google's cache) under the title "Mono and MacOS X". It turns out that the faster Mac was a desktop and the slower pc was a laptop.

    126. Re:I like the last bit by slittle · · Score: 1

      Urm.. modular/monolithic has nothing to do with macro/micro. Kernel modules run in kernel space, just as if they were compiled in. If it were a microkernel OS, they'd run in userspace.

      --
      Opportunity knocks. Karma hunts you down.
    127. Re:I like the last bit by Anonymous Coward · · Score: 0
      , some random shitty soundcard driver would not be able to crash the entire OS, like it usually happens

      Even if a driver were implemented in 100% user space, it might be possible for it to crash the system by writing garbage to the sound card registers (which is needs access to produce sound). Lots of cards do not properly "check inputs" like they should and take down the machine with them when they "die".
    128. Re:I like the last bit by LWATCDR · · Score: 1

      I do not think that when those flame wars where going on that anyone was thinking that Linux or Minix would ever be "production" OS's. Most people where waiting for GNU to produce theie Unix like OS. Rember GNU is not Unix. Well that one sure as hack turned out to be true. Hurd is still not ready for production and really is getting very little interest. I am tempted to install it just to look at it. One has to wonder what if Minix had been given to the GNU project back in the late 80s? It was free of all leagle problems with AT&T code and could have been a good base for GNUs OS.
      I have to admit that I am more than a little disapointed with HURD. I like the idea of trying new Ideas in an OS but it really is not getting the development that it should. I guess that the big problems is that BSD and Linux are good enough.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    129. Re:I like the last bit by phoenix_rizzen · · Score: 1

      You've got your terms all confused. Monolithic kernels can be modular (like the Linux or BSD kernels). Once a module is loaded, it is actually part of the kernel, running in kernel space. There is no difference between a Linux kernel with all the drivers compiled into it, and a Linux kernel that loads all the drivers via modules.

      A microkernel has a teeny tiny kernel, then all the drivers are loaded as separate processes, all the programs are loaded as separate processes, and the kernel just passes messages around between those processes. Very different from a monolithic kernel. Nothing runs in kernel space except for the tiny little kernel itself.

    130. Re:I like the last bit by jedidiah · · Score: 1

      The Atari/Amiga port of Linux is actually how I first came to hear of it.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    131. Re:I like the last bit by rthille · · Score: 1

      Shit, 13 years ago I was running NeXTStep and it _still_ kicks the shit out of windows and pretty much any other OS that wasn't derived from it :-)

      --
      Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
    132. Re:I like the last bit by Jeremy+Erwin · · Score: 1

      1991: linux created
      1992: linus and ast have the debate.
      1994: m68k port of linux
      1996: Linux 2.0 released

      So, apparently tennebaum's dire predictions were disproved fairly quickly...

    133. Re:I like the last bit by RAMMS+EIN · · Score: 1

      ``It's not on Freshmeat yet. What's keeping you?''

      You really think the world is waiting for another OS in early development stage? It really wouldn't be very useful.

      That said, I like OS development a lot. If I get enthusiastic enough about some idea (not just writing another UNIX clone), I will happily hack away.

      --
      Please correct me if I got my facts wrong.
    134. Re:I like the last bit by RAMMS+EIN · · Score: 1

      I completely agree with you. I never said anyone would actually want to use my one week project. That's why I haven't done it (well, I did once, but it sucked so bad I never really picked up on it. but who knows, maybe those diskettes still work...)

      --
      Please correct me if I got my facts wrong.
    135. Re:I like the last bit by pyrrhonist · · Score: 1
      You really think the world is waiting for another OS in early development stage? It really wouldn't be very useful.

      Well, that was a joke, but you're right.

      The market is already overloaded:

      That said, I like OS development a lot. If I get enthusiastic enough about some idea (not just writing another UNIX clone), I will happily hack away.

      Did anybody write a nice free exokernel yet? That's something I'd be interested in messing with. Different personalities could be plugged into it depending on the application.

      --
      Show me on the doll where his noodly appendage touched you.
    136. Re:I like the last bit by foobsr · · Score: 1

      Yes.

      DESKTOP DREADNOUGHT. In just a few months, Intel plans to throw a coming-out party for its next-generation design, a superchip dubbed the 80486 and familiarly known as the 486. It will be a veritable mainframe-on-a-chip. Packing more than 1 million transistors, this thumbtack-size sliver of silicon will deliver the number-crunching wallop of a low-end IBM 3090 mainframe (chart).

      from http://www.businessweek.com/1989-94/pre88/b30711.h tm

      CC.

      --
      TaijiQuan (Huang, 5 loosenings)
    137. Re:I like the last bit by Tore+S+B · · Score: 1

      Do you know what date the Byte article was? The local library keeps a complete record of Byte mags, and it would be sort of cool to read. TIA.

      --
      toresbe
    138. Re:I like the last bit by Jeremy+Erwin · · Score: 1

      Probably April 1989-- when the 80486 was first introduced.

  2. An excellent article by madprof · · Score: 5, Funny

    Poor old Ken Brown must be wondering how wise it was to have made that particular trip now!
    Curious that someone would spend all that cash and yet have done so little research. Smells of hidden agendas, or no-so-hidden agendas perhaps?
    The best part has to be: "But the code was his. The proof of this is that he messed the design up." :-)

    1. Re:An excellent article by Anonymous Coward · · Score: 0

      Is Ken Brown a right wing conservative? It sounds like it...

    2. Re:An excellent article by not_a_product_id · · Score: 3, Insightful

      I thought one particularly interesting part in the Tanenbaum article was that it seemed pretty clear that Brown hadn't done any reading about Unix before hand. For something like this you surely spend a few weeks reading up at home and making notes before you fly to Holland and interview someone. Smells very fishy to me.

      --

      ---
      We spoke for about a half an hour. I don't recall a thing we said. - Colorblind James Experience

    3. Re:An excellent article by Anonymous Coward · · Score: 0

      He's filthy stinking communist and no mistake!
      Commie scum infecting our chldren and draining our precious bodily fluids.

    4. Re:An excellent article by Matt_UK · · Score: 1

      Ken Brown had done some research
      "Who has had a argument with Linus and would therfor dish up some dirt?"
      (lightbulb)
      "Hello KLM 1 return ticket to amstadam please"

      --
      Oooh 'eck DM!
    5. Re:An excellent article by AndroidonPPC · · Score: 0, Redundant

      Wait, I thought linux was just lifted from unix. That's what SCO says, and SCO seems like a bunch of upright people, right?

    6. Re:An excellent article by Anonymous Coward · · Score: 1, Funny

      "Hidden agenda" being amsterdam's coffeeshops and whorehouses, no doubt.

      Not that theres anything WRONG with that. Im just saying that any excuse to go to amsterdam is a good one.

      What a great city.

    7. Re:An excellent article by Anonymous Coward · · Score: 0

      You spelled uptight wrong

    8. Re:An excellent article by silicon+not+in+the+v · · Score: 1

      You don't have to read up on the topic or do any research to just catch a suspicious quote that you can proclaim out of context to "prove" the agenda you already have in mind. So Brown doesn't really need to do any research for his purposes, but at the same time, it does reveal to his interviewees what he's really about.

      --
      We may experience some slight turbulence and then...explode. -Capt. Mal Reynolds
    9. Re:An excellent article by oconnorcjo · · Score: 1
      I thought one particularly interesting part in the Tanenbaum article was that it seemed pretty clear that Brown hadn't done any reading about Unix before hand. For something like this you surely spend a few weeks reading up at home and making notes before you fly to Holland and interview someone. Smells very fishy to me.

      (for the humor impaired, please skip this post)
      Pretty simple to me- Free trip to Holland or Homework. If I could get away with billing a free trip to Holland instead of doing REAL work, I know which one I would do!

      "But boss, I need to know the syntax to this API, so I have a plain ticket to Brazil to talk to the guys who wrote the API"

      "What do you mean the library is down the street"

      "You mean you expect me to do research instead?"

      "I have to refund the plane ticket..."

      "But I have already arranged the interview!"

      --
      I miss the Karma Whores.
    10. Re:An excellent article by Anonymous Coward · · Score: 0
      Mod parent up! I would not be surprised if this Brown guy thought along these lines. He's not the brightest person around, that's for sure.

      Incidentally, do you happen to be Matt Loney from ZD UK?

  3. history... by azatht · · Score: 2, Insightful

    Whi is writing the history? the winner or the who loose?

    It seems that as of now no written history is correct, who can we trust? Buy a book for ×$ and learn history that is incorrect is not good.

    --
    ------- In the end there are no begining
    1. Re:history... by BerntB · · Score: 2, Interesting
      Whi is writing the history? the winner or the who loose?
      In almost all searches for truth, you will not reach it. But you can get more or less close.

      Yes, you can't reach perfect models of reality in multitudes of area (history, physics, etc), but to claim that they are all bunk is a bit overblown.

      It's like saying that since we can't freeze anything to 0 degrees Kelvin, that all termometers are worthless. Physicists can get very, very close to absolute zero -- and measure how far we are.

      (On topic, I loved Tanenbaum's books when I studied comp sci and would have lots of them, if people returned all things I've lent them the last 20 years... :-) )

      --
      Karma: Excellent (My Karma? I wish...:-( )
  4. Re:Grain of salt please by 91degrees · · Score: 3, Interesting

    Why are microkernels a bad idea?

  5. I still love the classic conversations from 1992.. by byolinux · · Score: 4, Informative

    Torvalds Vs Tanenbaum. I've never used MINIX, but I believe the source code is out there somewhere, although AFAIK, it's not free software.

    I've often wondered what things will be like when Hurd is ready, and we'll have GNU and GNU/Linux, and all those BSDs, and OS X all in usage.

    And then we'll probably still have to worry about making stuff look right in IE 6, because Microsoft takes forever to update it.

  6. Tanenbaum was wrong about microkernels by troon · · Score: 1

    ...slashdotted after only a few comments!

    --
    Ydco co ,df C erb-y go. a Ekrpat t.fxrapev
    1. Re:Tanenbaum was wrong about microkernels by Anonymous Coward · · Score: 5, Informative

      Some Notes on the "Who wrote Linux" Kerfuffle, Release 1.1

      Background
      The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

      Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

      Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

      AST: "What's the Alexis de Tocqueville Institution?"
      KB: We do public policy work
      AST: A think tank, like the Rand Corporation?
      KB: Sort of
      AST: What does it do?
      KB: Issue reports and books
      AST: Who funds it?
      KB: We have multiple funding sources
      AST: Is SCO one of them? Is this about the SCO lawsuit?
      KB: We have multiple funding sources
      AST: Is Microsoft one of them?
      KB: We have multiple funding sources
      He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.

      UNIX and Me
      I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

      Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there discussing compilers with Steve Johnson, networking with Greg Chesson, writing tools with Lorinda Cherry, and book authoring with Brian Kernighan, among many others. I also became friends with the other "foreigner," there, Bjarne Stroustrup, who would later go on to design and implement C++.

      In short, although I had nothing to do with the development of the original UNIX, I knew all the people involved and much of the history quite well. Furthermore, my contact with the UNIX group at Bell Labs was not a secret; I even thanked them all for having me as a summer visitor in the preface to the first editio

    2. Re:Tanenbaum was wrong about microkernels by Short+Circuit · · Score: 1

      Don't intercontinental data carriers charge by the amount of data transferred? I'm not sure how much data normally goes through those lines, but I suspect this article is going to hurt someone's pocketbook.

    3. Re:Tanenbaum was wrong about microkernels by Wizard+of+OS · · Score: 3, Funny

      And the fun thing is that that server is in the Netherlands, where today (thursday) is a nation-wide holiday.

      I think I can hear the faint cursing of a VU system administrator somewhere ...

      --

      --
      If code was hard to write, it should be hard to read
    4. Re:Tanenbaum was wrong about microkernels by deuce868 · · Score: 1

      ouch didn't even last 10 minutes. Anyone have it to share?

    5. Re:Tanenbaum was wrong about microkernels by ZenBased · · Score: 1

      Ok, here is a link to the article: without pictures

      --
      http://www.virtualconcepts.nl/
    6. Re:Tanenbaum was wrong about microkernels by The+Flying+Guy · · Score: 1

      Ahwell, it is hosted at the university AT works at, so they are prolly getting free or nearly free bandwidth.

    7. Re:Tanenbaum was wrong about microkernels by byolinux · · Score: 3, Funny

      Dutch people get every Thursday as holiday?

      No wonder they're so happy!

    8. Re:Tanenbaum was wrong about microkernels by owlstead · · Score: 1

      It probably still runs on Sun hardware and Solaris. I got it fine (though I am not in the first wave as you can see).

      Ex student.

    9. Re:Tanenbaum was wrong about microkernels by ReinoutS · · Score: 2, Informative

      It's a Christian holiday, "Hemelvaart". It's 40 days after Easter, the day Jesus supposedly ascended to Heaven on a cloud.

      BTW I'm a student at cs.vu.nl and I can tell you the bandwidth is definately not the problem (we're almost directly connected to the Amsterdam-US backbone).

    10. Re:Tanenbaum was wrong about microkernels by Eccles · · Score: 1

      ouch didn't even last 10 minutes.

      Was the server running a microkernel OS?

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    11. Re:Tanenbaum was wrong about microkernels by Anonymous Coward · · Score: 0

      Well, prolly is used on IRC alot, so I am hoping someone could not be such a nitpicker and just accept it as being online language.

    12. Re:Tanenbaum was wrong about microkernels by jedidiah · · Score: 0

      >> Linux has been the victim of fewer attacks than
      >> Windows because (1) it actually is more secure,
      >> but also (2) most attackers think hitting Windows
      >> offers a bigger bang for the buck so Windows
      >> simply gets attacked more

      This just demonstrates that smart people can still
      say remarkably stupid things. The attentions of
      virus writers have never had anything to do with
      popularity. Neither has the prevalence of virii
      themselves. If a system is a ripe breeding ground
      for malware, it will propagate regardless of size.

      This is as true for Linux as it was for the Atari ST.

      Anyone that claims that Linux doesn't get hit harder becuase it's "less popular" is just blathering.

      Automated malware propagates itself through any size user population. That's why we give such programs the moniker of "virus".

      --
      A Pirate and a Puritan look the same on a balance sheet.
    13. Re:Tanenbaum was wrong about microkernels by Anonymous Coward · · Score: 0

      Consider this:

      An inexperienced programmer wants to try his hand at writing a virus to see what sort of impact he can make on other people's lives. He has choices.
      How can he impact the maximum number of people? He will need to spend a fairly considerable amount of time studying an operating system to determine what vulnerabilities he can exploit. He can choose between MacOS, Linux, and Windows to get the most bang.
      MacOS constitutes a very small percentage of computer users, so it's out. Linux is apparently difficult to hack, and so would require serious time. Windows may require just as much time to hack for him, but probably less. The difference is that with the same or less time expenditure, he can either affect Linux's relatively small legion of users, or he can go after Microsoft's empire of clueless users. The choice is obvious.

    14. Re:Tanenbaum was wrong about microkernels by Leto2 · · Score: 1

      Ascension Day in English. And Monday 31 May is Pentacoste, aka "Pinksteren" in Dutch. Also christian, and unrelated to Memorial Day in the US.

      --
      <grub> Reading /. at -1 is like driving through Cracktown in a convertible that is stuck in 1st
    15. Re:Tanenbaum was wrong about microkernels by jedidiah · · Score: 1

      The choice is irrelevant.

      It doesn't take a large number of malware authors to create havoc on a platform. That's rather the point of malware. Morris demonstrated that quite nicely.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    16. Re:Tanenbaum was wrong about microkernels by ziphnab · · Score: 1

      You think he's cursing, you should have heard this place. You bastards slashdotted my uni's sites the week before finals

      --
      --- Sometimes even music cannot substitute for tears. --Paul Simon, Cool Cool River
  7. This just in. by xyote · · Score: 5, Funny

    Andrew Tanenbaum discovers slashdot effect. Adti disputes it, citing that others discovered it first and that Tannenbaum just copied it.

    1. Re:This just in. by Anonymous Coward · · Score: 0

      A pretty neat trick to let Slashdot link to a site that is hosted in a country that has a national holiday today. No system adminstrators around to fix the problems. They are probably lying somewhere on the beach ;-)

    2. Re:This just in. by FeebleX · · Score: 1

      They might have discovered it, but *I* have already patented it! MUWAHAHA!

  8. ignore and move on by whowho · · Score: 1

    This just all looks like a classic case of shouting out some blatantly false statement and running... Leaves behind a trail of people bouncing up and down trying to drown out the initial totally false message. We should just point out the idiocy of the book and move on. (ps /. already?) -- visiting italy? http://alltuscany.com

  9. Article text by Anonymous Coward · · Score: 5, Informative
    Slashdotted...
    Some Notes on the "Who wrote Linux" Kerfuffle, Release 1.1
    Background

    The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

    Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

    Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

    AST: "What's the Alexis de Tocqueville Institution?"
    KB: We do public policy work
    AST: A think tank, like the Rand Corporation?
    KB: Sort of
    AST: What does it do?
    KB: Issue reports and books
    AST: Who funds it?
    KB: We have multiple funding sources
    AST: Is SCO one of them? Is this about the SCO lawsuit?
    KB: We have multiple funding sources
    AST: Is Microsoft one of them?
    KB: We have multiple funding sources

    He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.

    UNIX and Me

    I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

    Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there disc

    1. Re:Article text by Spoing · · Score: 1
      I think what is really interesting is the length Brown went to dance around specific points.

      I've been interviewed in trade magazines, and this is exactly the tactic that is used to force a point (pre-determined by the interviewer) and get a quote in any context -- or enough bits to gerrymander something. The facts be dammed. Really *isses me off.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    2. Re:Article text by Anonymous Coward · · Score: 0
      gerrymander
      You keep using that word; I don't think it means what you think it does.
    3. Re:Article text by n0ano · · Score: 1, Informative
      With all the security problems Windows has now, it is increasingly obvious to everyone that tiny microkernels, like that of MINIX, are a better base for operating systems than huge monolithic systems.


      Interesting comment from AST given that, to my knowledge, Windows IS a micro-kernel based OS and it is still the most insecure system out there. If micro-kernel architectures were so inherently secure then Windows would have one of the best records in the business.


      I'm sorry Andy but, in a University teaching environment, I agree with you, a micro-kernel is the way to go. It makes it much easier to have students try different algorithms and see how they affect the system if the memory management system is done as a user process.


      Having said that, for a production system a micro-kernel is just wrong. The stability and security of a monolithic kernel is much more important than the flexibility of a micro-kernel.

      --
      Don Dugger
      "Censeo Toto nos in Kansa esse decisse." - D. Gale
    4. Re:Article text by RAMMS+EIN · · Score: 3, Interesting

      ``Windows IS a micro-kernel based OS''

      That may be true if you look only at the kernel proper, but I'm willing to bet that there are "userspace" processes that have kernel access to an extent that makes the system actully megakernel.

      Arguing your comments about microkernels:

      I don't believe microkernels are any more secure or insecure, than macrokernels. As for stability, I would rather expect microkernels to be better there. The added flexibility is immense, and has real world uses.

      Personally, I favor a system where nearly everything resides in userspace. It might even be feasible to make the system so flexible that different users or even processes can use different memory managers, schedulers, etc. There are a number of OS projects that explore in this direction, but I don't think we're quite there yet.

      --
      Please correct me if I got my facts wrong.
    5. Re:Article text by Unknown+Lamer · · Score: 1

      QNX

      So micro it hurts.

      Also fast, small, secure, and hard realtime.

      --

      HAL 7000, fewer features than the HAL 9000, but just as homicidal!
    6. Re:Article text by kisielk · · Score: 1

      QNX already lets you specify which scheduling algorithm to use for a thread. It allows you to choose FIFO, Round-Robin, or Sporadic scheduling. I believe you can add your own as well, but I don't have my reference book here to check for sure.

    7. Re:Article text by CrayzyJ · · Score: 5, Interesting

      `Windows IS a micro-kernel based OS''

      No no no. Windows is a monolithic kernel. Using Andy's defintions, the drivers run in kernel space; thereby, making it monolithic.

      "but I'm willing to bet that there are "userspace" processes that have kernel access to an extent that makes the system actully megakernel."

      Nope, this is false. In this sense, Windows NT (not counting 9x/Me because they suck) is identical to Linux. User space processes require system calls and a kernel crossing to have access to any kernel services.

      "I don't believe microkernels are any more secure or insecure, than macrokernels."

      I strenously disagree. In both Linux and Windows NT, 80+% of crashes are due to problems in drivers. There is a ton of research to back this up (Engler et al, I think). If the drivers existed in user space, a la microkernels, then 80+% of crashes would just disappear. Most people who complain about Windows' crashes do not realize the driver writers are to blame. Yes, Linux will have the same problem as drivers are ported. This also, has been pointed out in much research. THIS is the very reason why Andy dislikes monolithic kernels.

      --
      Holy s-, it's Jesus!
    8. Re:Article text by Anonymous Coward · · Score: 0

      It used to be in the Windows NT 3.5 days, but since NT4 they have moved so much crap, including windowing system, into ring0, (or kernel space) to make it essentially a monolithic kernel with loadable modules..

    9. Re:Article text by drinkypoo · · Score: 1
      "I don't believe microkernels are any more secure or insecure, than macrokernels."
      I strenously disagree. In both Linux and Windows NT, 80+% of crashes are due to problems in drivers

      Secure != Stable. You're talking about stability, he's talking about security. You're right about microkernels being potentially more stable because less of the OS need explode at once, and the one part that will take the whole system down is much simpler. It's kind of like how if you're running Windows and the GUI gets hosed up it usually takes the rest of the system with it, but if you're using a Unix[like] system X dies, and then respawns, and all your running applications (except stdio stuff, if you're using "screen") are lost but the system comes right back to usefulness. But that has little to do with security, because the application/process will still need the same kind of rights that it has on a megalithic kernel system and a microkernel system, it only uses different methods to get them. It's true that you can implement fine-grained rights control, but you can do that with either type of kernel.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:Article text by strider_starslayer · · Score: 1

      I'm going to call bullox here.

      As many if not more devices are supported (and that means with drivers) on linux, and even worse, they are supported by random individuals who are looking at the output from a 'black box' device (like a printer, or a scanner) and writing a driver based on that (since unline the driver writers they do not have access to the proprietary internals of the device), and they are not being paid, which often means that 'good enough' means it works and can crash on ocassion. Despite this, linux systems (And BSD systems, and to a lesser extend mac systems (while most hardware in macs are tightly controlled anyone can build a printer for a mac, and trust me some printer manufacturers *cough* HP *cough* do a pisspour job on the mac drivers) are downright rock solid compared to windows systems (This is of course entirely personal experience, and the most often reason I reset either machine is a result of slow memory leaks degrading performance over time); so one of the following is therefore true:

      1-80% of crashes are not due to drivers
      2-I exist almost entirely in the 20% due to a satistical anomoly
      3-Somehow people just trying to make things work have mannaged to build greatly superior drivers without knowing the internals of the systems there building those drivers for
      4-There is a fundamental flaw in the windows arcetecture that allows drivers to more easily crash it compared to linux
      5-Building drivers for windows requires more skill then building them for Linux, and the end result of this is that windows drivers are more crashy

      --
      -Millions of Monkeys, Millions of typewriters, 6 hours of sorting through faeces encrusted pages to find: This post
    11. Re:Article text by bored · · Score: 1
      4-There is a fundamental flaw in the windows arcetecture that allows drivers to more easily crash it compared to linux
      5-Building drivers for windows requires more skill then building them for Linux, and the end result of this is that windows drivers are more crashy


      Accually, its a little bit of both and a lot of a couple of things you didn't mention. Firstly windows like AIX (for example) is a paged kernel. Linux isn't, this adds some complexity because the driver writter has to have tighter control over their memory allocations and interrupt levels. Most of the time's i've seen windows crash its been because of "Page fault at IRQL>=DISPATCH_LEVEL" which is caused by a driver writter accessing paged memory in a path which isn't allowed to access paged memory. AIX has a 'backtrack' function which will attempt to resolve these page faults but it's _REALLY_ hairy, and its slows the system down a _LOT_. Plus if the page fault can't accually be resolved (ie the disk driver takes a page fault while holding a lock, and the pagin path needs to reenter the disk section) bad shit happens.

      Windows does a much better job of checking irq levels, handles etc. In windows if a driver in kernel space does something that is "against the rules" like hitting paged memory at dispatch level then the box blue screens. In linux driver failures don't always take the box down. This is accually bad, because the system behavior isn't deterministic. Its possible in linux to accually have driver crashes and continue to executution. Of course anything from that point forward is suspect. If your running a web server who cares... This accually brings me to the freezing point, because of this loose and dirty method of dealing with kernel mode failures, i've seen a lot of freezes (especially when running X and the OOPS ends up on a TTY you can't see) in linux. Probably 2 to 3x as many freezes as accual crashes. Although the end result is basically the same (given a hw watchdog in linux since a crash can be handled as a reboot by the system). Freezes are something I can't remember ever seeing in windows.

      In windows there are a number of kernel tunable parameters that can be screwed with to increase the stability of the machine. Especially on NT4 boxes turning off kernel paging is a good one. Since 2k M$ has shipped a _VERY_ nice toolkit for driver writers to test their drivers in ugly situations. For example, there are things which force all non pinned kernel pages out to disk, this helps find paged kernel problems, there is also a tool to make sure that callback paths are called at the max IRQL that the documentation lists, there are low memory tests where the driver tries to allocate memory and fails (something that is almost guaranteed to crash/freeze a >=2.4 linux box)



      Anyway, the driver signing program from M$ is little more than running those tests, in M$'s labs on a number of diffrent hardware configurations. The result is noticable in anything newer than W2k. Running signed drivers crashes are _VERY_VERY_VERY_ rare. Now if linux were to have something similar (a proper testing program) I probably wouldn't be experiencing 5 to 10 crashes/freezes a week on the half dozen linux boxes i use.


    12. Re:Article text by CrayzyJ · · Score: 1

      "Secure != Stable. You're talking about stability, he's talking about security. "

      When drivers run in kernel context, it becomes the same thing. Drivers can now run in priviledged mode.

      --
      Holy s-, it's Jesus!
    13. Re:Article text by CrayzyJ · · Score: 1

      You sir have not the slightest bit of knowledge in this area; therefore, you should not contradict me.

      "1-80% of crashes are not due to drivers"

      WRONG. You HAVE NO idea what you are talking about. There has been much work in this area that state 80% of crashes are due to drivers. See work by Engler et al.

      "3-Somehow people just trying to make things work have mannaged to build greatly superior drivers without knowing the internals of the systems there building those drivers for"

      The APIs are well documented. It's not like writing Windows drivers is a voodoo science. One again, get a clue before you spout off FUD.

      "4-There is a fundamental flaw in the windows arcetecture that allows drivers to more easily crash it compared to linux"

      Nope. Both allow drivers to run in priviledged mode. Period. They BOTH have the same fundamental flaw.

      "5-Building drivers for windows requires more skill then building them for Linux, and the end result of this is that windows drivers are more crashy"

      I write drivers for both. This is also a flawed statement. Depending on the driver, either can be easier or harder. For example, file system drivers, in my opinion are easier on Linux. Transport drivers are easier on Windows due to the TDI. Writing drivers on ANY OS requires skill, and this is the problem. Companies allow any old smack to write drivers.

      --
      Holy s-, it's Jesus!
    14. Re:Article text by Anonymous Coward · · Score: 0

      I think you need to reread my post and try responding again, you seem to believe that I listed 5 things that were happeneing, rather then 5 options, of which only one needed to be taking place.

      Also
      WRONG. You HAVE NO idea what you are talking about. There has been much work in this area that state 80% of crashes are due to drivers. See work by Engler et al.
      While I have encountered many works that put more then 85% of crashes on drivers, those works are often pointed strictly at windows XP or 2000, and rarely even mention linux. So even if all the research is correct, and not heavily influenced by those who paid to have those satistics taken, or the research done (See the recently done 'research' by an unnamed company that claims essentially that all the ills of society are the fault of free software and that Linus did not make Linux).

    15. Re:Article text by Anonymous Coward · · Score: 0

      This just in, adti says that post was copied from somewhere else.

  10. Re:Grain of salt please by tribulation2004 · · Score: 3, Informative

    You'd be wary of Tannenbaum's assertion that Linus wrote Linux? Did you read his statements at all, or did you simply comment in a rush to be one of the first posters?

  11. Re:Grain of salt please by Anonymous Coward · · Score: 0
    Why are microkernels a bad idea?
    Because they get stuck between your teeth and hurt!
  12. Re:I still love the classic conversations from 199 by madprof · · Score: 4, Informative

    MINIX is licensed under the BSD licence, as mentioned in the article.

  13. slashdotted by mikeee · · Score: 1

    I think his webserver could use a performance hack right about now.

    1. Re:slashdotted by Zork+the+Almighty · · Score: 1

      It must be running on a microkernel system :)

      --

      In Soviet America the banks rob you!
  14. Re:Grain of salt please by AKAImBatman · · Score: 1, Troll

    annenbaum is also the guy who thought that micro-kernels were a good idea.

    I'm sorry, who was it that had that much coveted OS that "just works", and is so cool that everyone wants it but doesn't have the first clue as to how to copy it?

    Oh, right. Microkernels seem to work pretty well for Apple.

    Linus wrote Linux, and that's all there is to it. Anything to the contrary is Microsoft FUD.

    Can't argue with that. I can't read the article, but I don't think that Tannenbaum argues with that either. He probably said something like Linus copied the basic Minix design (true) and the reporter blew it out of proportion.

  15. Sounds like my mother-in-law by TaxSlave · · Score: 5, Funny

    Start with a premise, do little or no research, and declare conclusions. When the truth is pointed out, get indignant.

    Granted, I haven't read the book in question, but this was a very enlightening article. I especially loved the comment that insinuates that Linus could have done a better job if he HAD stolen the code, than he did.

    1. Re:Sounds like my mother-in-law by Anonymous Coward · · Score: 0

      Start with a premise, do little or no research, and declare conclusions. When the truth is pointed out, get indignant.

      Sounds like a good description of posts on a Microsoft article. Sigh.

    2. Re:Sounds like my mother-in-law by adamofgreyskull · · Score: 3, Informative
      I especially loved the comment that insinuates that Linus could have done a better job if he HAD stolen the code, than he did.
      AST is talking about the design, but Linus has made similar comments regarding certain parts of the implementation to refute SCO's claims:
      Basically, the above is _exactly_ the kinds of mistakes a young programmer would make. It's classic.
    3. Re:Sounds like my mother-in-law by Anonymous Coward · · Score: 0

      Sounds like my mother. My mother-in-law is very rational.

      posted anonymously in hopes that God won't know who wrote this and shorten my life-span (Exodus 20:12)

  16. It's an old copyright strategy by argoff · · Score: 4, Insightful

    In old world media, who creates something of value is more important than what gets created. Hence there is often alot of slander, lies, and outright fraud (and a lot of crapy media). In Hollywood, it's so bad it's pratically institutionalized.

    I think the enemies of Linux are trying a similar strategy based on the addage "if you kill the shepard - the sheep will scatter", "If you lie about something long enough or hard enough, people will believe it". They can't discredit Linux for technological or commercial reasons anymore, so their only option is to discredit Linus. With billions at stake, it could get nasty.

  17. The Real Father of DOS &Windows by CrypticSpawn · · Score: 3, Interesting

    Okay the real father of dos and windows is here

    1. Re:The Real Father of DOS &Windows by Hey_Bliss · · Score: 1

      And by the way if you search well and wide (Google for gods sake goooooglee!!!) you'll find out that P/CM was latter open sourced so you can find the source around the net, I still have a copy in my HD somewhere around... pretty nifty OS it was, ran lovely on my epson qx-10

    2. Re:The Real Father of DOS &Windows by njcoder · · Score: 1
      My favorite part of that....
      After Ray Noorda had to step down from the helm of Novell he set up a new company, Caldera, which bought the rights to Novell's legacy operating systems from its DRI acquisition. Caldera then filed a lawsuit against Microsoft over its anti-competitive practices against DRI. Caldera's lawyers and their witness documented ample evidence of the anti-competitive practices and dirty tricks that Microsoft had used to drive its competitor out of the market. At the beginning of 2000 the lawsuit was settled out of court in return for Microsoft paying a reported US$150-200 million to Caldera. Thus DR DOS, the product that I had helped develop, cost Microsoft dearly, both while DR DOS was a healthy challenge to Microsoft's virtual operating system monopoly and after Bill Gates had considered it dead and buried.
      Funny how Novell Cheif starts Caldera... sues Microsoft based on technology he bought from Novell..... now Microsoft (it seems) helps Caldera (SCO) start a lawsuit based on technology it bought from Novell. Makes sense that Baystar would think SCO's value is in it's IP. It's worked for them in the past.
    3. Re:The Real Father of DOS &Windows by Anonymous Coward · · Score: 1, Insightful

      There were systems long before CP/M that similar characteristics. Better, though, in that at least some of them didn't have the "C drive, D drive" crapola that lingers in Windows and VMS. Well, CP/M had A drive and allowed it to be swapable on the fly because who could afford more than one tiny drive anyways. Doesn't anybody remember RT-11 and its predecessors? Or OS/8, or PS/8, written originally over a weekend by Richie Lary to mimic TOPS-10. Pfaugh. Can one person write an operating system, sure. One person can write more than one operating system. That Linus should have followed the "two weeks in the lab can save an hour in the library every time" philosophy on Linux is no surprise. We would have been better off had he spent his energies to flesh out Net-2, but he's better off having done what he did.

  18. Devil's advocate by A+nonymous+Coward · · Score: 2, Interesting

    Well, not quite advocate ... I can't get to the interview, it's acting ...slow ... for some reason.

    But I had the distinct impression from other quotes about the AdTI book that IFFFF you go with the idea that everything which looks like UNIX was inspired by UNIX, THEN it is not that big a stretch to say that Linux was not invented but is just a copycat derivative, therefore Linus did not invent Linux, he merely wrote it. Like I said, I have not seen the actual book (of course) or interviews, but maybe that is the quibble they are going with, a sock puppet for SCO, who is in turn Microsoft's own sock puppet.

    And for all you bozoes who think this means I believe it, well, ha ha, yolk's on you for having no imagination in your narrow little cross-eyed brain.

  19. Re:Grain of salt please by samhalliday · · Score: 0, Troll

    +1 interesting? come on moderators... this is a blatent troll!

  20. Re:Grain of salt please by Shadowlion · · Score: 3, Insightful

    Why are microkernels a bad idea?

    They aren't, any more than monolithic kernels are a bad idea. The general whine against microkernels goes something along the lines of, "Any performance increases that result from a microkernel can be matched by simply tweaking a monolithic kernel, therefore why bother with the complexity of a microkernel?"

  21. How can Linux be a copy of Minix by solidhen · · Score: 3, Interesting

    if one is a macrokernel and the other a micokernel?

    I don't think Tanenbaum is bitter. He just wants to point this out.

    --
    Some things are more important than an animated rat
    1. Re:How can Linux be a copy of Minix by Tarantolato · · Score: 5, Insightful

      I don't think Tanenbaum is bitter. He just wants to point this out.

      Since I don't think anyone here has RTFA'd (/. effect and all) it's not worth judging right now. I think it's pretty classy of Tanenbaum to step up and offer some perspective on the AdTI FUD. If he does that as someone who still doesn't buy into Linux, that makes it all the more credible. Do we really want every response to this to be written by a Linux fanboy?

    2. Re:How can Linux be a copy of Minix by B'Trey · · Score: 5, Informative

      I read the article from the Groklaw link before it showed up on /. Tanenbaum says that at least five different people single handedly wrote a UNIX-like kernel and that Linus clearly wrote Linux. He also says that Brown, the person who interviewed him, was completely clueless and obviously pushing an agenda.

      The bitter part comes in the last couple of paragraphs, where he takes the opportunity to say that Linus was a misguided kid who should have paid more attention in class such that he would have seen the obvious superiority of a microkernel over a macrokernel. But he's quick to point out that he and Linus are not enemies.

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    3. Re:How can Linux be a copy of Minix by Boing · · Score: 2, Funny
      Do we really want every response to this to be written by a Linux fanboy?

      You're new here, aren't you?

    4. Re:How can Linux be a copy of Minix by Tarantolato · · Score: 4, Interesting

      He also says that Brown, the person who interviewed him, was completely clueless and obviously pushing an agenda.

      I was semi-surprised at how retarded Brown came off in the article. I mean, everything that's come out of his "institution" would lead one to expect that, but somehow I thought maybe it was just an act for the punters. Turns out he really is that dumb. Weird.

    5. Re:How can Linux be a copy of Minix by Tony-A · · Score: 1

      Turns out he really is that dumb. Weird.
      What's significant is that this is what Microsoft can find to do their "independent research".

    6. Re:How can Linux be a copy of Minix by killjoe · · Score: 1

      This guy is the president of ADTI. If he is that dumb can you imagine the other 13 people?

      I really have to figure out how to do this scam.
      Get money from big corporations
      write books they want you to write ...
      profit!!

      Bigtime too!

      --
      evil is as evil does
    7. Re:How can Linux be a copy of Minix by crotherm · · Score: 4, Insightful

      The bitter part comes in the last couple of paragraphs, where he takes the opportunity to say that Linus was a misguided kid who should have paid more attention in class such that he would have seen the obvious superiority of a microkernel over a macrokernel. But he's quick to point out that he and Linus are not enemies.

      When I read it, to me it came across as a gentle rub, more good natured than bitter. Alas, when reading text, very often it is hard to determine the mind set of the author at the time of witing...

      --
      "Those who make peaceful revolution impossible, make violent revolution inevitable" - JFK
    8. Re:How can Linux be a copy of Minix by bradkittenbrink · · Score: 1

      You're new here, aren't you? The correct phrasing of that joke is: You must be new here...

    9. Re:How can Linux be a copy of Minix by WinterSolstice · · Score: 1

      I think it is good that he did take those shots. They were honest, they were fair, and they make sense. He's saying (As far as I can tell) that he's no fan of Linux, but that this whole thing (the SCO/MS stuff and the paper released by their agents) is just stupid. Linus wrote Linux, it belongs to Linus, and writing an OS/Kernel is NBD. (Hurd notwithstanding, apparently ;) )
      I disagree slightly, since I think writing a *useable* OS is a big deal. Other than that, I agree with his perspectives. Mostly.

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
    10. Re:How can Linux be a copy of Minix by Tarantolato · · Score: 5, Insightful

      I really have to figure out how to do this scam. Get money from big corporations

      They started off taking money from the Swiss. The process seems to go something like this:

      1. Get some hack-journalist experience (overfunded and obscure policy journals publish damn near anything; ditto for the Washington Times, as long as it purports to be conservative).
      2. Get to know rich people
      --a. get cushy internships in college
      --b. marry a lawyer at a Big Firm
      3. Convince the rich people you know to pay you for hack journalism.
      4. Use hack journalism to push dubious foreign-investment schemes
      5. PROFIT!!!

      The key is that business, academia, law, journalism and government don't really know how to function with one another. They want to, for both good and bad reasons, so a lot of the time they're willing to throw big money conferences, fellowships, publications and "research institutions" that are supposed to grease the wheels.

      Added to this, washed-up bigwigs usually want some place to go, and their former friends often set up make-work jobs for them. Lose an election? Why don't you give a lecture once a month at my public policy school. Get shitcanned from your CEO job? Why don't you sit on my government advisory committee. Newspaper column dried up? How bout you be a fellow at my think-tank. And of course, all of these people need gophers, personal assistants, research aides, etc. - a whole industry of suckups scurrying around washups.

      The pay is peanuts for the honorees, sometimes even nonexistent. But they like the honorary titles. In exchange, the institution that hands out the titles gets more prestige from having Big Names attached to it. Look at the name-dropping on AdTI website: Jack Kemp, Newt Gingrich (Republicans), John Norquist (Democrat). In turn, the aura of Big Names clustered around an institution makes it easier to sucker donors.

      That's basically the scam: laundering prestige for money. All you have to do is Know People(tm).

    11. Re:How can Linux be a copy of Minix by arodland · · Score: 1

      Not sure whether this is a typo in the book or the article that was recently on /. referencing the book, but if the article is correct, then Tanenbaum doesn't need to worry anyway, because it claimed that Linux copied from Minux ;)

    12. Re:How can Linux be a copy of Minix by Anonymous Coward · · Score: 0

      I thought it was pretty obvious that Tanenbaum's criticisms of Linux as having a flawed design were tongue-in-cheek. I could see him smiling as I read it.

    13. Re:How can Linux be a copy of Minix by LWATCDR · · Score: 2, Interesting

      Tanenbaum is a great teacher. And if it was not for Minix there might not have been a Linux.
      The problem is that Tanenbaum does not seem to understand that the world outside of universities has a different view of superiority.
      The x86 ISA sucks. The Alpha, 68k, spark, Arm, and powerPC where and in some cases are much better ISAs. But the Intel ISA won. More people use it and it gives a HUGE bang for the Buck!
      Tanenbaum was to interested in Minx as a teaching tool and in "pure" OS design. Linux at the time wanted more bang for the buck. It might be hard to believe but Linux used to only run on the 386 family of chips. If I remeber correctly Linux was supposed to be PC only OS.
      Tanenbaum may be right. Of course there are also things like Plan 9. Frankly I am a little tired of Unix/Linux being the best OS. I want to see some new ideas in OSs and GUIs. Being a big OOP fan I would like to see an OO OS. Maybe I will start writing my own OS like Linus and Tanenbaum did. Odds are I will develop it on Linux :)
      Thanks Mr Tanenbaum and thanks Linus.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    14. Re:How can Linux be a copy of Minix by StormReaver · · Score: 1

      "I think it's pretty classy of Tanenbaum to step up and offer some perspective on the AdTI FUD."

      I agree completely. I don't have to agree with everything Andrew says to realize that the man demonstrates the utmost integrity by defending a person (Linus) whose opinion on a subject important to them both is drastically different from his own, and by defending him for no other reason than to make sure the truth is known.

      There's a man I can respect.

  22. Re:I still love the classic conversations from 199 by Brent+Nordquist · · Score: 1

    The complete archive for this thread was linked from Groklaw yesterday, you can find it here. You're right, it's well worth reading. The part I found funniest was his comment about "when you can run Hurd in the 21st Century" -- that was 1992 and here it is 2004...

    Linus has said repeatedly in recent years words to the effect of "People think I'm a nice guy, but I'm really a bastard." It's interesting to see elements of that in what he calls (in the thread) "hopefully my last flamefest"; he was big enough to apologize for the tone of his first reply.

    --
    Brent J. Nordquist N0BJN
  23. Monolithic versus microkernel by John_Sauter · · Score: 5, Informative

    In a kernel there is a lot of interaction between the various parts. In a monolithic kernel these interactions are performed by simple subroutine calls and manipulation of shared data. In a microkernel these interactions require a more complex switch between tasks, and message passing. In exchange, you get better protection of one part from the others, which makes tracking down bugs quicker.
    John Sauter (J_Sauter@Empire.Net)

    1. Re:Monolithic versus microkernel by Laxitive · · Score: 4, Insightful

      There's a little bit more to it than that.

      The microkernel idea derives from one basic principle: anything that doesn't need to run in kernelspace, shouldn't be in kernelspace.

      There are several hypothetical benefits to this approach. For one, code that executes in kernel space is trusted. You'll notice that a lot of CS academics advocate microkernel architectures. It's because the less you have in the kernel, the easier it is to verify the kernel. The fewer the set of kernel primitives you have, the easier it is to reason about how the kernel will behave. In modern microkernels (see: L4, or it's free variant Fiasco), pretty much the only thing of importance left in kernel space is the scheduler, process management, and a few basic stubs for memory management. Most of the memory management implementation itself is pulled out into userspace.

      The other benefit of microkernels is that they allow the system to be more flexible, when designed correctly. For example, having drivers in userspace means that you don't have the Linux issue with having to match driver versions with kernel versions. Another good example is that you _still_ cannot reasonably mount filesystems as a non-priviledged user in Linux. It's not unreasonable to expect that if you have access to a filesystem image, and you have access to the mount point, that you be allowed to extend the mount point with a view into the filesystem that you have control of. It should be possible, but it's not - mostly because the FS core is embedded into the kernel. And yes, there are kernel modules that promote the VFS layer to userspace - and they work pretty well. But there's really no need to have an artificial distinction between userspace FS impementations and kernelspace. There's nothing special about parsing directory and file structures that really needs to be in the kernel.

      There are, and always will be, performance hits associated with moving kernel stuff into userspace. You necessarily have to have context switches for message passing - which has to be implemented in the kernel to be trusted in a microkernel design. The question is wether you think the benefits of microkernel design are worth that tradeoff.

      I think they are. A 10% hit in performance is going to get eaten up as hardware gets better and faster. But that 50% increase in manageability and flexibility is going to pay dividends well into the future.

      -Laxitive

    2. Re:Monolithic versus microkernel by prockcore · · Score: 2, Interesting

      I think they are. A 10% hit in performance is going to get eaten up as hardware gets better and faster. But that 50% increase in manageability and flexibility is going to pay dividends well into the future.

      Who's saying anything about a 10% hit in performance?

      Here are some benchmarks between Panther and Yellow Dog Linux on a Dual 1.25 ghz G4.

      Unix Bench Scores (bigger is better)
      for Linux: 316.4
      for Panther: 131.0

      lmBench Fork in microseconds, smaller is better)
      for Linux: 352
      for Panther: 1402

      lmBench TCP Latency (in microseconds, smaller is better)
      for Linux: 46.3
      for Panther: 76.8

      lmBench Pipe performance (in MB/s, bigger is better)
      for Linux: 419.0
      for Panther: 216.0

      We're talking about huge performance issues across the board. Everything from process construction and destruction to context switching to communication latencies. OSX is much much slower. I attribute this entirely to the Mach Microkernel.

    3. Re:Monolithic versus microkernel by groomed · · Score: 1

      I think they are. A 10% hit in performance is going to get eaten up as hardware gets better and faster. But that 50% increase in manageability and flexibility is going to pay dividends well into the future.

      It's important to point out that it's not so clear-cut as a 10% performance hit. The hit might be 1000% here and just 0.5% somewhere else, or it might be that the modularization prevents the use of a particularly efficient algorithm. The overall performance hit on average might be 10%, but on the whole that's a pretty useless figure.

      Secondly, the increased manageability has a large subjective component. There's a huge learning curve to overcome when you modify highly modular systems. It's a lot easier to just add a member to a struct and add a few lines of code here and there. For the increased manageability to actually materialize you really need lots of people with lots of training and experience to be working on a huge codebase. With F/OSS, that's usually not the case.

    4. Re:Monolithic versus microkernel by Laxitive · · Score: 1

      Yes, the numbers look bad. But there are several things to note here.

      First off, I believe the Linux kernel is much better engineered than OSX's mach derivative. The Mach model was one of the first microkernel models to be developed. Apple has done a lot of optimization on Mach to make it usable, but Linux has had much more active development over a much longer period of time. For example, people have tuned the fuck out of Linux's fork and exec functions - mostly because that used to be the main way to handle concurrency in Unix. I don't think similar amounts of development have happened with OSX's kernel.

      Secondly, you quote those numbers. So how bad is it really to use OSX? How is the user experience affected by this? I can't speak for myself, because the only desktop I run is debian, but from what I've heard from Apple users, they really don't seem to think anything is that badly off.

      Thirdly, there are more modern microkernel architectures out there. See: QNX and L4. Now, I'm not going to unequivocally say that these are going to perform as well or nearly as well as Linux - since the kernels themselves havn't really received the kind of testing on a full-blown OS that they need (well, I've read that L4 with a Linux single-server implementation on top suffered a 5% performance hit, but a single-server kernel implementation is likely to give higher performance than a real multiserver implementation that actually _uses_ the message passing infrastructure for more than just basic tasks). These have yet to be tried, tested, and optimized extensively.

      -Laxitive

    5. Re:Monolithic versus microkernel by Laxitive · · Score: 2, Interesting

      Ok, I'm going to do some armchair analysis here. I think it _will_ come down to a X% difference in performance, in general. Consider what happens when a process in Linux makes a syscall. It triggers a user->kernel context switch. The kernel does some work, potentially blocking the user process, and eventually wakes up the process again and does a kernel->user context switch.

      In the message passing model, generally, the syscall ends up sending a message to some system server. Now that involves a user->kernel switch to trigger the message send, and a kernel->user switch for the message to be delivered. When a response is sent from the system server, the same hit is incurred again. So essentially, we have about twice the number of context switches going on.

      But userkernel stuff isn't really the major problem with message passing. It's kernelkernel interaction that used to be a simple function call.. but with microkernels suddenly become two message sends. That seems rather daunting at first, but there are many optimization methods to resolve it.

      For example, if two system servers are going to talk with each other extensively, they can do some initial handshaking to establish a shared memory area, and use that to communicate.. bypassing the kernel entirely. There will still be a latency hit with relation to that _particular_ interaction, but the overall message passing overhead will be reduced.

      Another idea is to used shared memory for uploading of, for example, write-protected code. It might be possible to have two processes share a chunk of memory, and in that memory, include code to access structures stored within that shared memory. If you design a standardized system for doing something like that, you might be able to bring it all down to the level of a function call again.

      There are lots of options. I don't know how feasible those options are - but they havn't really been tried to any great extent. There's nothing equivalent in the microkernel area to the extensively tested and tweaked freely developed Linux.

      About modularization, I disagree with you. The problems you are describing stem from over-engineering. Modular systems don't need to be hard to understand or work with. Their whole purpose is to partition off related code into islands, have them interact with well-defined interfaces, so that it's easier to reason about the whole by reasoning about the pieces. Badly engineered modular systems can be just as horrible as badly engineered monolithic systems. That's not really saying anything about either approach.

      -Laxitive

    6. Re:Monolithic versus microkernel by groomed · · Score: 1

      There are lots of options. I don't know how feasible those options are - but they havn't really been tried to any great extent. There's nothing equivalent in the microkernel area to the extensively tested and tweaked freely developed Linux.

      There has been at least one port of Linux to Mach, MkLinux. This port actually had some support from Apple. You can slice the numbers any way you want; it's slow.

      Is that because of lack of effort? Inherent difficulty? Mach flaws? Who can tell? What we do know is that almost no microkernel based designs survived in the wild. At what point does it stop being an implementation problem and become a design problem?

      About modularization, I disagree with you. The problems you are describing stem from over-engineering. Modular systems don't need to be hard to understand or work with.

      All I'm saying is that it's harder to write modular code than to write non-modular code. You may have a point about the overengineering.

  24. On Minux by Gumshoe · · Score: 4, Informative
    On Minix:
    While [Minix is] not free software in the sense of "free beer" it was free software in the sense of "free speech" since all the source code was available for only slightly more than the manufacturing cost.
    That's not "free as in speech". IIRC, the licence prevented us from distributing changes to the OS in any form other than patch files. This was a major reason why people became interested in Linux -- no such restriction exists and it is therefore, truly "free as in speech".
    1. Re:On Minux by rthille · · Score: 2, Informative

      That's exactly "free as in speech". If I give a speech at a gathering and you write it all down and start distributing it, you're violating my copyright. However, if you distribute a patch set to my speech because you feel it reads better with your modifications, then you're welcome to do so.

      --
      Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
    2. Re:On Minux by Gumshoe · · Score: 1

      In literal terms you may be correct, but his comparison with free beer software leads me to believe he was alluding to the Free Software Foundation's meaning of "free as in speech" software. Regardless of whether he was or not, freedom as he defines isn't particularly useful.

      I've nothing against Minix incidentally, I quite like it in fact, and I understand his wish to keep Minix simple for the purposes of education; but his objection to people deriving works from Minix and distributing them, whether in prepatched source form or as a binary, is/was a mistake IMO.

  25. Cache/mirror? by anonieuweling · · Score: 1

    Does anyone here know about a cache or a mirror of the page that AT wrote about this issue?

  26. Re:I still love the classic conversations from 199 by AKAImBatman · · Score: 5, Funny

    "It was the dawn of the third age of mankind. Ten years after the Earth-Minbari war,

    "the Babylon project was a dream given form

    "Its goal: to prevent another war by creating a place where humans and aliens could work out their differences peacefully.

    "It's a port-of-call, home away from home for diplomats, hustlers, entrepreneurs, and wanderers.

    "Humans and aliens wrapped in two million five hundred thousand tons of spinning metal, all alone in the night.

    "It can be a dangerous place, but it's our last, best hope for peace.

    "This is the story of the last of the Babylon stations. The year is 2258.

    "The name of the place is Babylon5."

    "Oh, and GNU Hurd was just released."

  27. Mirror here by Brent+Nordquist · · Score: 2, Informative

    The whole thread was linked from Groklaw yesterday at this URL.

    --
    Brent J. Nordquist N0BJN
    1. Re:Mirror here by giminy · · Score: 1

      Um, you linked to a 12 year old newsgroup flamewar? How is this a mirror of AST's latest argument (unless this is still his latest argument :)).

      --
      The Right Reverend K. Reid Wightman,
    2. Re:Mirror here by Rick+Zeman · · Score: 1

      Um, you linked to a 12 year old newsgroup flamewar? How is this a mirror of AST's latest argument (unless this is still his latest argument :)).

      If nothing else, Linus "Benedict" Torvalds sure has learned a bit more diplomacy over the years....

    3. Re:Mirror here by Rick+Zeman · · Score: 1

      PS--

      Obviously, Brown in his hatchet-job^Wresearch never read this thread which if he googled he would have. If he had, his thesis would be even more indefensible.

  28. Oh the irony. by mumblestheclown · · Score: 3, Interesting
    Of course Linus wrote linux.

    right?

    But who wrote the version of Basic that started bill gates on his path to riches?

    The answer of course is that every creative engineering endeavour builds upon what came before. the detractors will call the step that the developer in question took as derivative, obvious, insignificant, or larcenous. the supporters will shine light upon the principal's ability to fuse diverse, unfocused, and/or unapplied parts into a cohesive whole.

    to mis-quote grandpa simpson, 'the fax machine isn't anything more than a waffle iron with (something or other that i forgot).'

    so, the question is really this: those of you who accuse (probably correctly) whoever is claiming that linus didn't write linux of spreading FUD, have you ever written a similar post smearing gates on basic? pot kettle?

    1. Re:Oh the irony. by Anonymous Coward · · Score: 2, Informative

      Quote:

      "Oh everything's stolen nowdays. Why the fax machine is nothing but a waffle iron with a phone attached."

    2. Re:Oh the irony. by tbannist · · Score: 1

      This could be amusing if this message gains any traction and someone has the insight to ask "Who wrote MS-DOS" at the right time. It would be very amusing if Microsoft managed to discredit itself... again...

      --
      Fanatically anti-fanatical
    3. Re:Oh the irony. by Anonymous Coward · · Score: 0
      so, the question is really this: those of you who accuse (probably correctly) whoever is claiming that linus didn't write linux of spreading FUD, have you ever written a similar post smearing gates on basic? pot kettle?


      However, I didn't get paid to do it by Linus (or Sun, or Novell...)

    4. Re:Oh the irony. by Anonymous Coward · · Score: 1, Interesting

      Actually, it is my understanding that most of the real work on Altair BASIC was done by Paul Allen, and it was inspired by work that had been done on DEC BASIC during an internship at Digital while he and Gates were students. It is also well known that Gates 'borrowed' computer resources from Harvard for his own commercial interests in starting Micro-Soft (as it was then known). So if you buy Ken Brown's arguments, then Bill Gates and Microsoft are guilty of the same thing that they are accusing Linus of.

    5. Re:Oh the irony. by advocate_one · · Score: 4, Informative
      yes... it's amazing what he managed to write with the help of a wodge of printout from a garbage can... (requires sub or day pass)
      Bricklin sent waves of laughter through the auditorium by reading a passage from Lammers' interview with Bill Gates in which the young Microsoft founder explained that his work on different versions of Microsoft's BASIC compiler was shaped by looking at how other programmers had gone about the same task. Gates went on to say that young programmers don't need computer science degrees: "The best way to prepare is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating systems."[my emphasis]

      Bricklin finished reading Gates' words and announced, with an impish smile, "This is where Gates and [Richard] Stallman agree!"

      The "Programmers at Work" panelists were full of optimism about new opportunities to reinvent software -- in the mobile-phone world (where, Scott Kim noted, the constraints of small screens and tiny memory made it feel "like the early days" again), in the new universe of RF tags, and in the still-unfolding saga of global networking. Bob Carr reminded everyone that technology transformations usually take 20 years to unfold -- "I remember thinking in 1987 that the PC industry was mature, it was over" -- and that the Internet is only halfway through that cycle.

      Still, that picture of Bill Gates dumpster-diving for operating-system code was hard to shake. Finding new ways to think about programming and to make better software demands a willingness for pioneers to open up their work so others can learn from it. "Getting the software industry on a more open, fair and level playing field," as Hertzfeld put it, is a prerequisite for any leap forward in the programming world. Software patents are a looming train wreck; competition in most "end-user" software is largely a distant memory. Simonyi's technical bottleneck is also a social, political and business logjam.
      Linus of course was doing a course at Uni with Tannenbaum's Minix as it's example code... But then again... he didn't deliberately set out to write an OS from scratch... to begin with, he wrote it primarily to have fun with the 386 instruction set and also to read usenet...
      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    6. Re:Oh the irony. by Dave_bsr · · Score: 3, Insightful

      Actually... didn't MS get its start writing BASIC compilers??

      I'm the first to disagree with anyone who says that Bill Gates isn't a very smart guy. He's got programming skills and incredible business smarts. However, he didn't write DOS, it was a clone of CP/M bought from another seattle company and then resold to IBM. story.

      You are right of course, that each engineering marvel builds on something previously. If all the tech in the world were removed, we might know how to build cars and houses and put together computer systems, but we'd never know how to put together a hammer with stones and sticks, or fashion steel and silicone out of iron and sand. It would be interesting, wouldn't it? We'd have to start out with that old tech, to get back to this new stuff.

      Anyways. idiots complain about Microsoft all the time, stupidly. But smart people do too - and there are plenty of good arguments against MS that don't require ignorance. The debate will continue. Hopefully Linux will get better, and the computing experience in general will get better. We'll see.

      --


      Who is this Anonymous Coward character, how does he post so much, and why is he always such a whore?
    7. Re:Oh the irony. by AndroidCat · · Score: 1

      According to the story, they managed to get their papertape of BASIC to run on the second try after a couple of tweaks. Since they didn't have access to an 8080 processor until then, they must have either had an 8080 simulator for testing or used a fairly mechanical translation of a working BASIC from another processor.

      --
      One line blog. I hear that they're called Twitters now.
    8. Re:Oh the irony. by atcurtis · · Score: 1

      But who wrote the version of Basic that started bill gates on his path to riches?

      That is simple to answer.... I remember an old interview on TV where Billy Gates himself admits that he went dumpster diving behind DEC for the discarded printouts which had the source code for DEC BASIC... Which Billy Gate's BASIC was heavily based upon.
      DEC, who became Digital, who got swallowed up by Compaq, who was eaten by HP, were the real authors behind Micro Soft BASIC.

      Ho hum...

      --
      -- The universe began. Life started on a billion worlds...
      -- Except on one where stupidity was there first.
    9. Re:Oh the irony. by SubtleNuance · · Score: 2, Interesting

      Isaac Newton to fellow scientist Robert Hooke on 5th. February 1676; "If I have seen further it is by standing on the shoulders of giants".

      This wise adage is why Intellectual Property, if implemented in the visage of Capitalists, will lead us to another Dark Age, a Totalitarian State or both.....

    10. Re:Oh the irony. by bladesjester · · Score: 1

      Making steel from iron qualifies as "Dangerous Fun" (as george carlin would say) to some of us. i miss it :)

      --
      Everything I need to know I learned by killing smart people and eating their brains.
  29. Re:I still love the classic conversations from 199 by Anonymous Coward · · Score: 0

    I've often wondered what things will be like when Hurd is ready...

    You sir, have more faith than I.

  30. The Text by Anonymous Coward · · Score: 0

    Some Notes on the "Who wrote Linux" Kerfuffle, Release 1.1
    Background

    The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

    Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

    Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

    AST: "What's the Alexis de Tocqueville Institution?"
    KB: We do public policy work
    AST: A think tank, like the Rand Corporation?
    KB: Sort of
    AST: What does it do?
    KB: Issue reports and books
    AST: Who funds it?
    KB: We have multiple funding sources
    AST: Is SCO one of them? Is this about the SCO lawsuit?
    KB: We have multiple funding sources
    AST: Is Microsoft one of them?
    KB: We have multiple funding sources

    He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.
    UNIX and Me

    I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

    Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there discussing compilers with Steve Johnson, networking with Greg Chesson, writing tools with Lorinda Cherry, and book authoring with Brian Kernighan, among many others. I also became friends with the other "foreigner," there, Bjarne Stroustrup, who would later go on to design and implement C++.

    In short, although I had nothing to do with the development of the original UNIX, I knew all the people involved and much of the history quite well. Furthermore, my contact with the UNIX group at Bell Labs was not a secret; I even thanked them all for having me as a summer visitor in the preface to the first e

  31. Re:Grain of salt please by Anonymous Coward · · Score: 2, Informative

    From Micro Kernels

    The basic idea of microkernels is to minimize the kernel, and implement as much of it as possible outside the TCB. The kernel should only export simple, low-level operations which hopefully allow for more efficient application implementations. This idea dates back to [Hansen 70], and a good overview can be found in [Liedtke 96]. Traditionally kernels are 'monolithic' in the sense that they implement all their functionality in a relatively unstructured fashion within the TCB. The advantages of microkernels are obvious from a software engineering standpoint:

    The TCB is made smaller, reducing the chances of errors due to its faulty implementation. The OS is more modular and thus more flexible and extensible.

    Services previously in the TCB can now possibly have more than one different implementation, perhaps even running concurrently.

    Microkernels initially met with great enthusiasm and in the late 80s there was much work on them in both academic and commercial settings. This wave of initial enthusiasm subsided when people started encountering what seemed to be inherent difficulties with the flexibility and efficiency of microkernel implementations:

    For some frequent operations, e.g. networking, the overhead of context-switching was too great for an out-of-kernel implementation. Thus the microkernels were not as efficient as originally thought.

    There are great difficulties with supporting more than one implementation of a basic system service, especially when more than one is to run concurrently. Thus the microkernels were not nearly as flexible as supposed.

    These difficulties were overcome by various compromises to the original microkernel ideals. Several efficiency-critical features were brought back into the kernel and the addition of new features into the kernel was supported through downloadable binary code, or trusted 'kernel-loaded modules'.

    But this integration of most drivers and servers back into the TCB largely eliminates the benefits of the microkernel approach, in the end resulting in an even more complex monolithic-like OS kernel.

  32. Article text by Anonymous Coward · · Score: 0

    Some Notes on the "Who wrote Linux" Kerfuffle, Release 1.1

    Background

    The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

    Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

    Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

    AST: "What's the Alexis de Tocqueville Institution?"
    KB: We do public policy work
    AST: A think tank, like the Rand Corporation?
    KB: Sort of
    AST: What does it do?
    KB: Issue reports and books
    AST: Who funds it?
    KB: We have multiple funding sources
    AST: Is SCO one of them? Is this about the SCO lawsuit?
    KB: We have multiple funding sources
    AST: Is Microsoft one of them?
    KB: We have multiple funding sources

    He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.

    UNIX and Me

    I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

    Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there discussing compilers with Steve Johnson, networking with Greg Chesson, writing tools with Lorinda Cherry, and book authoring with Brian Kernighan, among many others. I also became friends with the other "foreigner," there, Bjarne Stroustrup, who would later go on to design and implement C++.

    In short, although I had nothing to do with the developmen

  33. AdTI by nanojath · · Score: 2, Funny

    I think it says something that the link to "Accomplishments" at the AdTI website is broken... (see here)

    --

    It Is the Nature of Information to Transgress Artificial Boundaries

  34. I created Linux by Anonymous Coward · · Score: 3, Funny

    I was the one who created Linux, and as I was on my way to cash in with ol' IBM I had the code hidden in a Wendies bag so no thief would steal it. But that rascal Linus was a starving pro-communist student at the time and he robbed me of my Cheese Burger, Fries, and my rights to the Linux empire.

    That's the truth, I swear it.

  35. The plot thickens by DreamerFi · · Score: 5, Interesting
    Take a look at this post on alt.os.development:

    Greetings,

    I'm conducting some research on behalf of the Alexis de Tocqueville
    Institution in Washington, DC. I'd like if someone could shed some
    light on the following questions:

    1. Describe the components of an operating system, besides the central
    component, the kernel.
    2. What do programmers usually develop first, the compiler or the
    kernel?
    3. Does this sequence impact the OS at all?
    4. What's more complicated, the kernel or the compiler?
    5. Why does operating system development take as long as it does? What
    are the three key things in operating system development that take the
    longest to perfect?
    6. Do you need operating systems familiarity to write a kernel? Yes /
    no? Elaborate please.
    7. In your opinion, why aren't there more operating systems on the
    market?

    Thanks for your time. Best,
    Justin Orndorff


    1. Re:The plot thickens by stanmann · · Score: 2, Funny

      1. Interface
      2. Yes
      3. Yes
      4. Yes
      5a. Because
      5b. 1. Bugs
      2.Bug fixes
      3. Features
      6. No. Because
      7. Because there are only 6 Billion people on earth and only 1-10% of them write OSs/Software.
      You're welcome.

      --
      Food not Bombs is a nice platitude but it breaks down when you notice that the Bombees are usually well fed
    2. Re:The plot thickens by Dr.+Smeegee · · Score: 4, Funny

      1. Describe the components of an operating system, besides the central component, the kernel.

      The Klaspil, the Frammistat and the Peramulator (sometimes called the "Virtual McGuggehupphe Valve). The Kaspil formats tuples for processing by the Frammistat, tuples are sorted, tagged and valued by the Perambulator.

      2. What do programmers usually develop first, the compiler or the kernel?

      Acne. Lots, usually.

      3. Does this sequence impact the OS at all?

      Probably

      4. What's more complicated, the kernel or the compiler?

      Girls

      5. Why does operating system development take as long as it does?

      Why is a duck?

      What are the three key things in operating system development that take the longest to perfect?

      Obsolecense, threading and nice icons.

      6. Do you need operating systems familiarity to write a kernel? Yes / no? Elaborate please.

      Yes. No.

      7. In your opinion, why aren't there more operating systems on the market?

      Terrorism.

    3. Re:The plot thickens by GeekDork · · Score: 3, Funny

      Great. In principle, this is the "please write an article so that I just have to put my name over it" strategy from the "The Way of the Weasel" Dilbert book.

      --

      Fight hunger. Filet a politician and send him to a 3rd world country of your choice.

    4. Re:The plot thickens by Anonymous Coward · · Score: 0

      A little bit of googling on what appears to be a cineast named J.O.

      Alias? Set-up? Cover. Duck. Sitting duck.

    5. Re:The plot thickens by Cruciform · · Score: 1

      I walked in on the whole thing late, but is Alexis de Tocqueville a legitimate place, or has The Toque engineered a big hoax?

    6. Re:The plot thickens by stanmann · · Score: 1

      Yes, and no Alexis de Tocqueville is legitimate.

      Sponsored by microsoft and the US government, but does do quasi-serious research. Aparently their hiring practices let in all sorts of idiots, but they are real and legit.

      --
      Food not Bombs is a nice platitude but it breaks down when you notice that the Bombees are usually well fed
    7. Re:The plot thickens by Decaff · · Score: 2, Funny

      Response from a certain well-known software company....

      1. Describe the components of an operating system, besides the central
      component, the kernel.

      Media player, browser, Word processor, Spreadsheet, database, demo games, Clippy, special virus/worm susceptibility modules.

      2. What do programmers usually develop first, the compiler or the kernel?
      Neither - you buy them off someone else and re-badge.

      3. Does this sequence impact the OS at all?
      Not if you have enough money.

      4. What's more complicated, the kernel or the compiler?
      The compiler, obviously. It as to cope with all the different versions of our OS.

      5. Why does operating system development take as long as it does? What are the three key things in operating system development that take the longest to perfect?
      The colours and shapes of the buttons and the start-up music takes a lot of time to design.
      (1) Thinking of the name ('XP' took a lot of effort). (2) Researching all the bits of other systems we want to copy. (3) Finding a rock group to perform at the launch.

      6. Do you need operating systems familiarity to write a kernel? Yes / no? Elaborate please.
      Not at all; its irrelevant. We have known for decades about how good operating systems should work, it hasn't stopped us providing BSODs.

      7. In your opinion, why aren't there more operating systems on the market?
      Nothing to do with us.... you didn't see us trying to sabotage DR-DOS. It was someone else who just looked like us.

    8. Re:The plot thickens by Anonymous Coward · · Score: 0

      view the whole whole thread. He doesn't get the answers he wants.

    9. Re:The plot thickens by An+Onerous+Coward · · Score: 4, Funny
      A chance to be funny! Or possibly insightful. Either way, yay me!

      1. Describe the components of an operating system, besides the central
      component, the kernel.
      The components of the operating system are as follows: The file browser, the kernelized window manager, the web browser, the media player, and the gaping remote exploit. As can be seen by this feature list, Microsoft Windows is the only true operating system on the market today.

      2. What do programmers usually develop first, the compiler or the
      kernel?
      Neither can be developed without access to a text editor, so invariably this is always written first. Unfortunately, once it is written, it needs to be compiled, and the compiler itself needs an operating system to run on. This "chicken and egg" problem wasn't solved until 2097, with the invention of time travel.

      [Seriously, this guy is wrong to assume that both have to be written in order to have a complete system. Theoretically, you could develop an x86 operating system entirely on an Apple Powerbook, and just copy the binaries over, so you don't need to develop a compiler to develop an operating system.]

      3. Does this sequence impact the OS at all?
      Yes. Writing the compiler first opens a gaping hole in the fabric of the universe, while writing the kernel first causes a plague of sabre-toothed cows. The trick is to write them both at the same time so that the cows are immediately sucked into the gaping hole.

      4. What's more complicated, the kernel or the compiler?
      "Complicated" means "something I know how to do." "Simple" means "something I don't know how to do, but I know the people who do and they're a bunch of nitwits so how hard can it be?" Given that criteria, I would have to say that both are braindead simple. Ask me again in a couple of years.

      5. Why does operating system development take as long as it does? What
      are the three key things in operating system development that take the
      longest to perfect?
      There are three rules that apply here. The first is Hofstadter's Law: It always takes longer than you think, even if you've accounted for Hofstadter's Law.

      The second rule is the 90% rule: The first 90% of the project will take 90% of the time, and the last 10% will take the other 90% of the time.

      The last rule is called the "There's no way in hell we can add all the features the marketing department has already promised our customers, and they just added twenty more, and by the way three of them violate laws of physics" rule. Unfortunately, only the name of the rule has been passed down over the years, so nobody remembers what it was about.

      6. Do you need operating systems familiarity to write a kernel? Yes /
      no? Elaborate please.
      A basic familiarity with computers is helpful, but not strictly necessary. For example, when Dennis Ritchie wrote the compiler for the BCPL language, he didn't actually use a computer. He scrawled the whole thing on a ream of paper, and had his secretary transcribe it. Similarly, when Linus wrote the 0.1 kernel, he used a photocopier.

      7. In your opinion, why aren't there more operating systems on the
      market?
      Because it is not in the interests of the Freemasons to have more operating systems on the market. I can't say anything more about that in this forum, but it's absolutely true.

      [Geez. There's a difference between an "operating system" (which a decent grad student can whip out in a few months) and an operating system which can be marketed as competition to the OSes already on the market. Linux 1.0 was probably closer to the former than the latter.]
      --

      You want the truthiness? You can't handle the truthiness!

    10. Re:The plot thickens by AndroidCat · · Score: 1

      From their methods of attempting to obtain a confession, I'm surprise that they called it the Alexis de Tocqueville Institute. Obviously they really meant the Tomás de Torquemada Institute.

      --
      One line blog. I hear that they're called Twitters now.
    11. Re:The plot thickens by Anonymous Coward · · Score: 0

      2 What do programmers usually develop first, the compiler or the kernel?

      In mmy caase, it waas neurrosis and thiis damnb eyye twitytch. I'nm jst glaaad thet snprintf alreeeady lokks lke a typo.

    12. Re:The plot thickens by WWWWolf · · Score: 1
      For example, when Dennis Ritchie wrote the compiler for the BCPL language, he didn't actually use a computer. He scrawled the whole thing on a ream of paper, and had his secretary transcribe it.

      Er, wasn't that rather the case with Niklaus Wirth and Pascal?

      (The rumor has it that since initially there was no compiler for Pascal, Wirth wrote one in Pascal, then "interpreted" it in his head and "ran" it on paper. A secretary might indeed have been handy.)

    13. Re:The plot thickens by Brandybuck · · Score: 1

      If AdTI are asking these questions, it's clear that they don't know the first thing about the topic their researching. It's like someone writing a history of Europe and then asking Usenet what species of frog the Franks were...

      But I can't really blame them. There's so much misinformation about operating systems out there, that it's no wonder they're confused. Between the marketing drivel from Microsoft and rantings from GNU, one might actually start to think that word processors and compilers were operating system components.

      --
      Don't blame me, I didn't vote for either of them!
    14. Re:The plot thickens by Brandybuck · · Score: 1

      They used to be a decent think tank. But like most other think tanks, it became a collection of yes men. Instead of providing answers they changed their business model to provide excuses.

      1954 Sponsor: "What impact will this policy have on agriculture"
      1954 AdTI: "That will cost you $50,000"

      2004 Sponsor: "What impact will this policy have on agriculture"
      2004 AdTI: "For $500,000 we will come up with whatever impact you want us to..."

      --
      Don't blame me, I didn't vote for either of them!
    15. Re:The plot thickens by Anonymous Coward · · Score: 0

      7. In your opinion, why aren't there more operating systems on the market?

      This one's simple: application developers will only develop to one platform. If they're doing it for the money (which most are), they will pick the most popular platform. When they've proven the market, you (the OS developer) "innovate" by writing your own version of the application and bundling it with your OS.

    16. Re:The plot thickens by An+Onerous+Coward · · Score: 1

      I wouldn't know. I was just making up something that sounded silly but ever-so-slightly plausible.

      --

      You want the truthiness? You can't handle the truthiness!

    17. Re:The plot thickens by Araneidae · · Score: 1
      when Dennis Ritchie wrote the compiler for the BCPL language
      Uh, I think you'll find that BCPL was written by Martin Richards.
    18. Re:The plot thickens by An+Onerous+Coward · · Score: 1

      A few points:

      1) I did not claim that Dennis Ritchie wrote BCPL. I claimed he wrote "the compiler for" BCPL.

      2) I was overreaching when I made the statement. In his online biography, Ritchie wrote, "I helped with a compiler for the BCPL language on the Multics machine (GE 645) and on the GE 635 under the GECOS system." source

      So essentially I was in error. Which brings me to point 3:

      3) After claiming that the Freemasons were secretly controlling the compiler market, that Linus wrote Linux using a photocopier, and that the "how do you compile the compiler" question can only be solved by time travel, why would you jump on me for THIS error?

      No, really. I want to know.

      --

      You want the truthiness? You can't handle the truthiness!

    19. Re:The plot thickens by Araneidae · · Score: 1
      why would you jump on me for THIS error?

      No, really. I want to know.

      No good reason: I happened to notice your remark, and I remembered learning BCPL and being taught by Martin Richards, so I knew he created it.
  36. (Un)available by NoOneInParticular · · Score: 0, Redundant

    Knowing the Free University network, I highly doubt that it is slashdotted, more likely that someone just pulled the plug after the unwashed masses of /. came along. No fear, I've got a login onto the machine and got the following from ast's www dir. This is the text version, I've also got the html, but given that my homepage is on the same machine as Andy's, I doubt that it will be of much use for me to mirror it.

    Some Notes on the "Who wrote Linux" Kerfuffle, Release 1.1

    Background

    The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

    Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

    Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

    AST: "What's the Alexis de Tocqueville Institution?"
    KB: We do public policy work
    AST: A think tank, like the Rand Corporation?
    KB: Sort of
    AST: What does it do?
    KB: Issue reports and books
    AST: Who funds it?
    KB: We have multiple funding sources
    AST: Is SCO one of them? Is this about the SCO lawsuit?
    KB: We have multiple funding sources
    AST: Is Microsoft one of them?
    KB: We have multiple funding sources

    He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.

    UNIX and Me

    I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

    Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there discussing compilers with Steve Johnson, networking with Greg Chesson, writing tools with Lorinda Cherry, and book authoring with Bri

  37. Fighting features by amightywind · · Score: 4, Insightful

    ..As I did 20 years ago, I still fervently believe that the only way to make software secure, reliable, and fast is to make it small. Fight Features.

    Credit Mr. Tanenbaum sticking to his guns on the micro kernel design. But the brilliance of Linus is that he realises you must first have features to fight!

    --
    an ill wind that blows no good
    1. Re:Fighting features by Tin+Foil+Hat · · Score: 3, Insightful

      FWIW, I think he's probably right from a technical standpoint. In practice, however, the macrokernel has been far easier to work with. Witness the huge success that macrokernel designs have had over microkernel designs. Even Apple, whose original macs were microkernels, eventually switched over to a macrokernel because of the difficulties of updating the original one.

      --
      No matter how many of my rights are taken away, somehow I still don't feel safe. -Frigid Monkey
    2. Re:Fighting features by Anonymous Coward · · Score: 0

      Huh???

    3. Re:Fighting features by chrism238 · · Score: 0
      But the brilliance of Linus is that he realises you must first have features to fight!

      One argument against "features" is that once they're there, they are very hard to remove. Features are too easy to add. The addition of features is not automatically brilliant. Fortunately, the world is beginning to realise this, and not automatically updating their operating systems and MS-Office just because they have new, infinitesimal, features.

      The alternate approach, is to be forced to justify why new features *must* be added, and why they can't be developed using existing facilities. Read about creeping featurism

    4. Re:Fighting features by Midnight+Thunder · · Score: 1

      Even Apple, whose original macs were microkernels, eventually switched over to a macrokernel because of the difficulties of updating the original one.

      They took something that worked and had a provem track record. In fact, from what I understand the orginal OS that makes up MacOS X actually had drivers running in protected memory, but this was done away with for performance reasons - maybe we will see this come back when computers are fast enough?

      Having hung around some of the development lists I get the general feeling that it is far less headache to develop things for user space unless you really have a good reason to write in kernal space. For example, anything that is can only be used by one program at a time is best found in user space. One of the problems with writing kernel space drivers is having to put up with constant reboots until you have the bugs out of the code. Developing in user space you only have to put up with crashing applications. For example, almost all USB drivers only need to be user space.

      --
      Jumpstart the tartan drive.
    5. Re:Fighting features by Trepalium · · Score: 2, Interesting

      I think you have apple's OS design completely backwards. Old Macs were completely monolithic (not unlike their hardware), and virtually everything ran in the same address space. Mac OS X changes things by running the microkernel Mach with the monolithic BSD-derrived Darwin kernel under that. The real reason Apple switched over was the simple fact there were too many design limitations in the original MacOS, and it was too difficult to tack on the features people expect these days, like separated (protected) address spaces, fully preemptive multitasking, and multi-user capabilities. All those features could've been grafted into the original MacOS kernel, but the engineers must've decided that it would be easier to graft MacOS onto a modern kernel rather than the other way around.

      --
      I used up all my sick days, so I'm calling in dead.
    6. Re:Fighting features by eraserewind · · Score: 1
      In practice, however, the macrokernel has been far easier to work with.


      Tell me about it. However, I think that proper debugger support for message passing would go a long way to reducing the problems. Debuggers that recognised the OS's messaging passing system, and treaded it like a function call would be great. Beats putting a breakpoint in a some kern_pass_message function anyway.
  38. There's no room for debate. by Phekko · · Score: 5, Funny

    SCO wrote it. From scratch. Now cough up that $699!

    --

    Sigs for Nerds. Sigs that Matter.
  39. Mac OS X != microkernel by ultrabot · · Score: 1

    Microkernels seem to work pretty well for Apple.

    ISTR that Mac OS X isn't really all that much of a microkernel - it's a monolithic BSD based system that mostly uses Mach (which *is* a microkernel) mostly for device abstraction.

    --
    Save your wrists today - switch to Dvorak
    1. Re:Mac OS X != microkernel by AKAImBatman · · Score: 2, Funny

      The BSD kernel used on top is not really a kernel in the truest sense. Instead, it's another microkernel server that provides an interface from the programs to the other servers. This design turned out to be quite sensible. It allowed the OS to "skin" its interface with programs on the fly, without inheriting a lot of the faults of the previously monolithic kernels. Thus Apple was able to run OS 9 programs in an OS 9 kernel "server", and then run ultramodern Unix/Cocoa apps in the BSD kernel "server". All without locking up the machine via OS 9's memory problems and poor system drivers.

    2. Re:Mac OS X != microkernel by ultrabot · · Score: 1

      The BSD kernel used on top is not really a kernel in the truest sense. Instead, it's another microkernel server that provides an interface from the programs to the other servers.

      So effectively Mac OS X is running BSD on a virtual machine? If we assume for a moment that compatibility w/ OS9 was not a concern, wouldn't it have been leaner and more elegant to run the monolithic BSD kernel directly in the first place? The "microkernel" approach here brings no benefits to the monolithic BSD kernel, which is the main thing modern applications actually run on...

      --
      Save your wrists today - switch to Dvorak
    3. Re:Mac OS X != microkernel by Anonymous Coward · · Score: 0

      OS X is more or less a "single server" design. It doesn't take full advantage of the message passing kernel potential. For contrast compare it with GNU Hurd which uses multiple "servers" to tap the underlying kernel. The Hurd design is closer to the ideal but its implementation is still raw and unpolished. Hurd needs more work, however it would be very interesting to hear Tannebaum's take on the GNU Hurd design.

    4. Re:Mac OS X != microkernel by AKAImBatman · · Score: 2, Informative

      You appear to misunderstand what a virtual machine is. The BSD kernel in OS X is 100% native code, running 100% in concert with the rest of the system. "Virtual Machine" implies that you are attempting to fool software into believing that it is running on hardware (real or imagined) that it isn't.

      Instead, the BSD layer of Mac OS X simply provides a POSIX interface to programs. "Kernel calls" are captured in the BSD kernel server, but are routed to the proper Mach server instead of being routed to the driver or I/O area of a full BSD kernel. Depending on how this is implemented, it could have a very minimal impact on performance. Even if it does slow things down in the processor, programs spend 90% of their time blocking on hardware anyway.

    5. Re:Mac OS X != microkernel by TheSunborn · · Score: 1

      No it is running (part of)the bsd kernel as a task similary to all the other tasks that it is running. To understand the mix of bsd and next have a look at What is Mac OS X http://www.kernelthread.com/mac/osx/

  40. Re:I still love the classic conversations from 199 by byolinux · · Score: 1, Funny

    Well, we've still got 96 years of the 21st Century left, so it's likely that the Hurd will be finished long before then.

    I am seriously looking forward to the Hurd, just as much as most people are looking forward to Duke Nukem forever. Difference is, Hurd is not vapourware, it's just an awfully large project and it'll be awfully welcome when it's complete.

  41. Obscure Reference by Anonymous Coward · · Score: 1, Informative

    You could include Mexicans and most of the countries in the caribean. I don't think baseball is popular anywhere else in the world.

    1. Re:Obscure Reference by Anonymous Coward · · Score: 0

      Um, ever heard of Japan?

    2. Re:Obscure Reference by Anonymous Coward · · Score: 0

      Yes, baseball is rather obscure outside of North America and Japan. If only it were interesting or at least exciting, imagine the possibilities.

  42. Re:Grain of salt please by Anonymous Coward · · Score: 0


    The general whine against microkernels goes something along the lines of, "Any performance increases that result from a microkernel can be matched by simply tweaking a monolithic kernel, therefore why bother with the complexity of a microkernel?"


    Ummm, no.

    The general whine against microkernals is that in order to get one to do useful work (outside of an educational institute) you have historically had to mangle it so badly that it is a microkernal in name only.

  43. Right, thanks for pointing out the origin of a ref by Anonymous Coward · · Score: 1, Insightful

    > I think Brown is batting .500, which is not bad for an amateur (for
    > people other than Americans, Japanese, and Cubans, this is an obscure
    > reference to baseball)

    Right. I could have guessed what sport it came from, but what does it mean, exactly?

  44. Obligatory mirror by TaxSlave · · Score: 4, Informative

    Here's a mirror of the article while it lasts.

  45. /.:ed source by azatht · · Score: 0, Redundant
    copy from http://www.cs.vu.nl/~ast/brown:

    Some Notes on the "Who wrote Linux" Kerfuffle, Release 1.1 Background

    The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

    Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

    Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

    AST: "What's the Alexis de Tocqueville Institution?"
    KB: We do public policy work
    AST: A think tank, like the Rand Corporation?
    KB: Sort of
    AST: What does it do?
    KB: Issue reports and books
    AST: Who funds it?
    KB: We have multiple funding sources
    AST: Is SCO one of them? Is this about the SCO lawsuit?
    KB: We have multiple funding sources
    AST: Is Microsoft one of them?
    KB: We have multiple funding sources

    He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.

    UNIX and Me

    I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

    Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there discussing compile

    --
    ------- In the end there are no begining
  46. Mirror please by harikiri · · Score: 0, Redundant

    mirror if anyone has one

    --
    Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
  47. Re:Grain of salt please by mr_z_beeblebrox · · Score: 3, Interesting

    Can't argue with that. I can't read the article, but I don't think that Tannenbaum argues with that either. He probably said something like Linus copied the basic Minix design (true) and the reporter blew it out of proportion.

    Worse, he said "Linus wrote Linux as far as I know" Then when the moron said that One person couldn't possibly write a kernel, Andrew listed six other examples (including himself) showing that one person could do that. Remember reading (the post) is fundamental.
    How is that for a grain of salt?

  48. Re:Grain of salt please by 3fingers · · Score: 0

    I'd be wary of anything that Tannenbaum says especially after prentending he was dying just so his wife would take him back, you just cant trust some people...

    --
    There are 10 different kinds of people, those who understand binary and those who do not
  49. In conclusion .. by Macka · · Score: 5, Insightful
    My conclusion is the Ken Brown doesn't have a clue what he is talking about. I also have grave questions about his methodology. After he talked to me, he prowled the university halls buttonholing random students and asking them questions. Not exactly primary sources


    What more needs to be said !

  50. email between Tanembaum and Linus by rahard · · Score: 1
    Does anybody still have archive of email exchange(s) between Tanembaun dan Linus in the early development of Linus. I read it long-long time ago (reminds me of kernel 0.12. anybody?), but didn't keep it. It would be interesting to re-read it again.

    -- br

    1. Re:email between Tanembaum and Linus by r1ch · · Score: 1

      They're available on Google's USENet archive.

      Here is Linus first announcing Linux, and here is the (in)famous debate between Linus and Tanembaun.

    2. Re:email between Tanembaum and Linus by rahard · · Score: 1
      Thank you very much. Yes, that's what I was looking for.

      -- br

  51. Re:Grain of salt please by wildjim · · Score: 3, Insightful

    I personally think Microkernels are *still* a good idea. A well-designed one is extremely modular, often extremely small (yeah, I know: "duh") and very portable, and the small-chunk approach can make them a lot easier to understand. On top of this, you can seperate the different parts of the kernel from each other, so there's far less likelihood of different pieces stepping on others, drivers can (theoretically) be run in user-space (if such a thing applies)...

    However, like anything, they are *not* going to be a perfect panacea. If the design is not just right, they can end up being far worse than the mono-kernels they are often competing with.
    The Mach MK is one where kernel-developers complain frequently about trying to get drivers to work with it, its message-passing architecture being unable/difficult to use in certain important ways, etc, etc, whereas I've heard a lot of praise for the L4 design.
    In fact, isn't TRON/iTRON (etc) a MK-style design? If it weren't for the US Trade Dept, it'd probably be running on your Desktop, PDA, Washing-machine, Wrist-watch, TV.....

    Anyway, it feels a bit like the difference between OO and Procedural coding, where OO projects tend to suffer without a reasonable amount of design effort *before* starting to code, but make maintenance simpler over the life of the project, and Functional-style tends to allow you to get stuck in, but can make maintenance and/or functionality upgrades more difficult. In fact, even down to the usual blaming of OO-style for creating slower code.

    Horses for courses; but I'd love there to be a full-fledged Linux-style OS (FOSS, good driver support, etc) running on a MK. Just because ;-)

  52. QNX by RAMMS+EIN · · Score: 5, Interesting

    Add QNX to that. It doesn't get much more microkernel than that, and I think noone would argue that QNX is slow.

    As for Darwin; it was certainly slow on my x86 laptop, but it's not lacking any speed on my iBook. I guess that says something about the quality of the x86 port (hint: there is no such thing).

    Poor Andy seems a bit too stuck in his I am right and everyone who disagrees is wrong. I have a book here (Distributed Systems: Principles and Paradigms) in which he claims that a 20% performance loss is not so bad, in exchange for all the benefits a microkernel brings. I most sincerely think that is a ridiculous statement, but fortunately, it doesn't have to be that way. I believe microkernels need not incurr any significant performance penalty at all.

    --
    Please correct me if I got my facts wrong.
    1. Re:QNX by MemoryDragon · · Score: 1

      Well 20% performance loss is bad, but newer microkernels are much better in this regard, I just had a look at the L4linux page, they use a linux personality on a mikrokernel and claim only a performance loss of 4% to the plain 2.4 kernel, which is not too shabby given the advantages you get from the design in the long term.

    2. Re:QNX by RAMMS+EIN · · Score: 4, Informative

      However, L4Linux is Linux running atop an L4 kernel. This means that the Linux kernel is still as monolithic as it always was. The same goes for MkLinux (Linux on Mach) and Darwin (a monolithic BSD server on Mach).

      --
      Please correct me if I got my facts wrong.
    3. Re:QNX by Paladine97 · · Score: 1

      QNX's filesystem is HORRENDOUSLY slow. I had two partitions, of roughly 20 gigabytes in size on the same disc. I performed a dd to copy the one partition into the other. I returned 10 hours later, to find it still running.

      I wise up, pop in a Linux rescue CD, and perform the dd in about 20 minutes.

      The networking is slow. Try doing a find / over a telnet session. Ouch.

      It's pretty quick if you stay in your own process ;-)

    4. Re:QNX by JesseL · · Score: 3, Interesting

      If you'r using dd to copy a partition and you find it slow, how cold you possibly attribute it to the filesystem? Doesn't dd just do a raw copy and ignore the filesystem in a case like that?

      --
      "Prefiero morir de pie que vivir siempre arrodillado!"
    5. Re:QNX by photon317 · · Score: 3, Insightful

      A 20% performance hit really doesn't matter. Look at the rate of speed increases in hardware. When new systems come out doubling performance at such a regular pace, a one-time 20% slowdown to switch to an otherwise superior architecture with other benefits is an easy pill to swallow.

      Of course, I don't think microkernels are a superior archeticture to begin with, and I think that a bland "20%" isn't a reasonable estimate of the real-world application or database's performance loss, so I still disagree with Andy.

      I'm of the view that the differences between micro and monolithic kernels are really a question of where you place things in a semantic sense. Just as one can write OO code in C, one can write well-isolated modular code in a monolithic kernel. I'd rather have the burden of that modularization taken care of on the developer's end than at runtime.

      --
      11*43+456^2
    6. Re:QNX by Wesley+Felter · · Score: 1

      I would argue that QNX is slow. It doesn't even have a unified page cache. But you could prove me wrong with some QNX vs. Linux LMBench results on the same hardware.

    7. Re:QNX by Tony-A · · Score: 5, Insightful

      A 20% performance hit really doesn't matter. Look at the rate of speed increases in hardware. When new systems come out doubling performance at such a regular pace, a one-time 20% slowdown to switch to an otherwise superior architecture with other benefits is an easy pill to swallow.

      Good theory. Practice seems to work out differently.

      Speed comparisons between products. Seems like 5% difference is enough to declare a clear winner. Unless you look behind the curtain.

      Speed increases in hardware? At work I have two computers. I am typing this on NT4 on a 400MHz Gateway. My "other" computer is XP on a 2.4GHz Dell. Other than some legacy dBase for DOS applications the "faster" computer isn't any faster. It does boot faster which means that the XP machine is booted a lot more often than the NT. A 20% performance hit would be the same 20% on both machines.

      The quoted improved performance doesn't quite translate into reality. A legitimate 10-times performance (IBM 1410 to IBM 370/135) transated into a 2-times difference in actual throughput. By the way, going the other direction won't work. As a rule of thumb, you will feel 90% of all slowdowns and only 10% of all speedups. This works both directions, like the "uphill both ways" quip.

    8. Re:QNX by Anonymous Coward · · Score: 0


      Add QNX to that. It doesn't get much more microkernel than that, and I think noone would argue that QNX is slow.


      Well you thought wrong.

      QNX is NOT and has never been a high throughput kernel.

      QNX is in many ways the Python of OSes. It is very beautiful, isn't very fast, but is still quite useful and appropriate for a wide variety of applications.

    9. Re:QNX by TheRaven64 · · Score: 4, Informative
      As for Darwin; it was certainly slow on my x86 laptop, but it's not lacking any speed on my iBook. I guess that says something about the quality of the x86 port (hint: there is no such thing).

      The performance hit of doing a context switch on PowerPC is about the same as doing a function call, which make multithreading and things like microkernels very easy to do fast. On x86, the overhead is often an order of magnitude larger, making microkernels crawl.

      --
      I am TheRaven on Soylent News
    10. Re:QNX by lscoughlin · · Score: 1

      Clue time.

      Thats not the filesystem, it's some attribute of your computer or the way in which you invoked dd.

      dd does a bit level copy of everything from raw source to raw destination. A partition to partition copy using dd if=/dev/hda1 of=/dev/hda2 utterly ignores the filesystem. Incidently, if you tried too use that command, on ANY os, it would be horrendously slow because the default block size is like 512bytes.

      Foo off.

      --
      Old truckers never die, they just get a new peterbilt
    11. Re:QNX by dan_sdot · · Score: 1
      I most sincerely think that is a ridiculous statement, but fortunately, it doesn't have to be that way. I believe microkernels need not incurr any significant performance penalty at all.
      What are you talking about? On what basis do you "believe" this? Have you ever found an OS that competes in terms of speed with the speed of a monolithic kernel of the same size? And if you are about to respond "yes," think again. The difference between a micro and monolithic kernel is that for any given action that the kernel must perform, the code path in a micro-kernel is longer. This is how abstraction and modularity is provided. In a monolithic kernel, things are done "down and dirty," where you ignore important concepts in computer science (the before mentioned), but the benefit is that you eliminate a good amount of code to be executed. This ends up bringing a large benefit when the code is executed as much as a kernel's code is.
      The simple fact of the matter is, context switching into another kernel process, say, the mm, takes much longer then a simple function call into some code address that is considered the "mm" because it was compiled from a directory called "mm". But maybe you just "believe" that context switching is as fast as a couple pushes and a jump.
    12. Re:QNX by RAMMS+EIN · · Score: 3, Informative

      Exactly. The parent probably meant disk device driver. I wonder what blocksize he used? Picking the right blocksize makes all the difference in the world; larger blocksizes reduce head movements (which are orders of magnitude slower than actual data transfers), but will eventually exhaust core memory.

      --
      Please correct me if I got my facts wrong.
    13. Re:QNX by newandyh-r · · Score: 1

      "A 20% performance hit really doesn't matter. Look at the rate of speed increases in hardware" The problem if you take that attitude is that all the places you "don't worry about the performance" tend to add up and performance is at lot worse than down 20%

    14. Re:QNX by Rysc · · Score: 1

      "A 20% performance hit really doesn't matter. Look at the rate of speed increases in hardware. When new systems come out doubling performance at such a regular pace, a one-time 20% slowdown to switch to an otherwise superior architecture with other benefits is an easy pill to swallow." ...tell taht to Java.

      What was it everyone said "Sure, Java is a bit slow NOW. But just wait! With the next rev of CPUs it'll be just as fast as the apps you use now."

      Only the CPUs revved and all the apps sped up, so Java was still proportionally slower. Whoops.

      Java is *still* slow. Sometimes you don't notice so much, but you do notice.

      --
      I want my Cowboyneal
    15. Re:QNX by Anonymous Coward · · Score: 0

      Ummm.. It's a port of the Linux kernel that runs in user mode on top of L4, side by side with the other microkernel applications.

      Your point being?

      L4 is actually very fast. Read some papers on it.

    16. Re:QNX by pyrrhonist · · Score: 1
      Thats not the filesystem, it's some attribute of your computer or the way in which you invoked dd.

      Hmmm, lets break this down a little bit. The poster said:

      I performed a dd to copy the one partition into the other. I returned 10 hours later, to find it still running.

      I wise up, pop in a Linux rescue CD, and perform the dd in about 20 minutes.

      In other words, he used dd on both operating systems.

      That being said, I don't think that it's reasonable to assume that he invoked dd with drastically different options on each operating system. Maybe he did, but I doubt it. It just doesn't make sense to suddenly remember the blocksize option when switching operating systems. In other words, if he forgot the blocksize option on one OS, he would most likely forget it on the other.

      Thus, it doesn't matter how he invoked dd. Linux would still end up being faster for him, because he would have used the same options on each OS.

      Now, assuming that there isn't some important message in the manual, like, "you must always use a blocksize of 8192 when using dd on QNX", I don't think the difference in speed is due to the way in which he invoked dd. I don't think the speed difference is necessarily due to filesystem implementation, either.

      What I'd be curious to know is how each OS recognized the capabilities of his drive and IDE controller.

      --
      Show me on the doll where his noodly appendage touched you.
    17. Re:QNX by Tony-A · · Score: 1

      What I'd be curious to know is how each OS recognized the capabilities of his drive and IDE controller.

      I'm guessing, but this sounds like:
      QNX is doing: Read a sector. Write a sector. Repeat.
      Linux is doing: Read a mess of disk. Write a mess of disk. Repeat.
      Linux disk drivers do seem to at least attempt to get maximum performance out of the disk system.

      To test, manufacture a bogus partition table where p2 is one sector after p1.
      If my guess is right, QNX will behave repeatedly and Linux will give random garbage. In neither case will p2-after be the same as p1-before.

    18. Re:QNX by Elladan · · Score: 1
      Add QNX to that. It doesn't get much more microkernel than that, and I think noone would argue that QNX is slow.


      QNX is slow.

      We had to deal with it a bit at my last job, and while it's nicely suited for realtime programming, it was horribly inefficient at things where throughput matters. The filesystem, for instance, was amazingly slow.

      This isn't to say that's necessarily a problem - for some applications, only latency matters. But most people would like their work to get done fast, too.

      That said, most of the reason QNX is slow probably has to do with it being realtime, not with it being a microkernel. These things are always tradeoffs - realtime performance implies you've sacrificed efficiency for determinism.

      A microkernel is an attempt to sacrifice efficiency for stability and/or maintainability - but to a very large degree that's an illusion, since the hardware doesn't allow you to truly isolate device drivers, and that's where most instability comes from.
    19. Re:QNX by Anonymous Coward · · Score: 0

      I believe his point is that in this mode of operation, L4 is actually only "scheduling" one application (the monolithic Linux kernel), and not lots of small applications (Linux scheduler, individual driver 'apps', ...). There is a difference.

    20. Re:QNX by TheSunborn · · Score: 1

      Most likely problem. No dma support for your chipst in qnx. Just think about it. Your harddisk can't read more then 40MB/second, and any kind of computer sold widthin the last 7 years should able to copy 40MB in far less then a second.

    21. Re:QNX by ACPosterChild · · Score: 1

      He's only right if you accept his assertions. He feels that security is more important than a GUI. Obviously, if you don't rate features at the same importance level as him, you're probably going to come to a different conclusion. The question you have to start with is, better at what?

      However, the last sentence and a half of your post is what really intreagues me. I find it interesting that you'd disagree with somebody who's been studying and teaching microkernel architecture for 20 years. If a well-known and respected champion of a cause is willing to admit to a significant performance hit, you really need to post more evidence than "I believe". (the way things get moderated here at /. never cease to amaze me) Checking your web site, I see that you have thought about and posted a couple articles about programming (although I found them incomplete and disagreed with some things), but I get the feeling that you don't have the expertise to argue such things with a well-respected expert (Tanenbaum, not me!).

      As far as QNX being slow, do you have a monolithic QNX kernel to compare it to? If not, then how do you know that it's not running 20% slower than a comprable monolithic kernel? That's Tanenbaums's point of the 20% performance loss being moot; if you're running at a speed that you're happy with (2.4GHz), then why worry about any performance cost (i.e., vs. 3GHz)?

      Damn, electricity is blinking. forgive any errors, can't proofread!

    22. Re:QNX by g-san · · Score: 1

      ...will eventually exhaust core memory.

      I use DIMMs you insensitive clod.

    23. Re:QNX by RAMMS+EIN · · Score: 1

      ``But maybe you just "believe" that context switching is as fast as a couple pushes and a jump.''

      Which is actually pretty much the case on architectures other than x86 (which wasn't originally designed to do multitasking), or so I am told. I am going to test it once I have enough experience with low level programming on PowerPCs.

      On the other hand, it's also a question of debate whether you actually need full context switches. Many people think that microkernel means that every driver runs in a separate address space, and this may be required by some definitions, but what if we get rid of this idea?

      Drivers can be implemented like shared libraries, sharing address space with other drivers and applications, in which no context switches are required anymore, and thus no performance hit is incurred. In fact, such a system might even perform better than a monolithic kernel.

      The last paragraph is just a sketch to give you a rough idea of how microkernels can be fast. I'm sure you can identify deficiencies; it's not a fully worked out proposal. I just mean to illustrate that there are other ways to achieve independently loadable modules, besides having them run in different contexts. And, as I said in the beginning, context switches needn't be expensive.

      --
      Please correct me if I got my facts wrong.
    24. Re:QNX by lscoughlin · · Score: 1

      You're right, i jumped the gun. All i read was this.

      QNX's filesystem is HORRENDOUSLY slow. I had two partitions, of roughly 20 gigabytes in size on the same disc. I performed a dd to copy the one partition into the other. I returned 10 hours later, to find it still running.

      and went off on that first rediculous statement.

      I did then read this.

      I wise up, pop in a Linux rescue CD, and perform the dd in about 20 minutes.

      after reading your return post, but then fournd this.

      The networking is slow. Try doing a find / over a telnet session. Ouch.

      At the end, got annoyed again, and then read this

      It's pretty quick if you stay in your own process ;-)

      and became simply baffeled.

      Why did we feed this troll...!?
      -T

      --
      Old truckers never die, they just get a new peterbilt
  53. Not bitter... by Anonymous Coward · · Score: 1, Insightful

    I believe he's just annoyed. After all his teaching and even writing an example of how an operating system should be, he feels Linus didn't pay attention, and that if he had, Linux would be much better. Nothing seems to annoy teachers more than those darn kids who don't pay attention and run off and try something on their own.

    He wrote Minix as an educational tool in the hope that someone would take the example and do great things. Someone did... but went off in a slightly different direction than was hoped.

  54. Re:Right, thanks for pointing out the origin of a by Tuirn · · Score: 1

    Not that I know squat about baseball, but I think it's a batters hit percentage.

    --
    Klein bottle for rent - inquire within.
  55. Re:Let's reignite the fight! by Smallpond · · Score: 1

    Quote #1 So at the time I started work on Linux in 1991, people assumed portability would come from a microkernel approach. You see, this was sort of the research darling at the time for computer scientists. However, I am a pragmatic person, and at the time I felt that microkernels (a) were experimental, (b) were obviously more complex than monolithic Kernels, and (c) executed notably slower than monolithic kernels.

    Quote #2 Only stupid people think they should throw away old proven concepts. ... This is how we get crap like microkernels.

    -- Linus

    Monolithic: UNIX, Linux

    Micro: Minix, BeOS, Hurd, (supposedly AIX)

  56. Baseball by Gocho · · Score: 1

    Maybe all Dominicans, Puerto Ricans, Venezuelans, Mexicans and Panamanians will disagree that only those thre countries know about baseball... but hey... I'm used to americans thinking that everyone south the border is a tequila-drinking, sombrero-wearing mexican...

    1. Re:Baseball by Anonymous Coward · · Score: 0

      Who is the compete jerk modding this down to troll level?

      idiots

    2. Re:Baseball by Anonymous Coward · · Score: 0

      Yeah, kind of the way you think of those Peruvians, Chileans, and Brazilians, huh.

    3. Re:Baseball by overunderunderdone · · Score: 1

      used to americans thinking that everyone south the border is a tequila-drinking, sombrero-wearing mexican.

      They aren't?

  57. I'm not so sure by bigchris · · Score: 1

    How long have they been developing HURD for? Seems like ages. I'm really not sure that it'll ever be finally released to be honest with you.

  58. Web Text, please? by Anonymous Coward · · Score: 0

    Can someone please post the article? I can't get to the web site. The Interweb may be down. Thank you.

  59. Baseball by Gocho · · Score: 1, Insightful

    How about Mexicans, Puerto Ricans, Panamanians, Dominicans, Venezuelans, Koreans, Colombians and others who also play baseball? :)

  60. Re:Right, thanks for pointing out the origin of a by bbh · · Score: 2, Informative

    It means of his two claims, half (%50) of them are correct. The two claims are that Brown interviewed Tanenbaum (true) and that Linus Torvalds didn't write Linux (false).

    bbh

  61. Two independently developed *nices by jmitchel!jmitchel.co · · Score: 5, Informative

    AST lists several independently developed systems of equivalent complexity to Mixix 1.0 / System 7. Here are a couple more I found:

    OMU (6809 processor, ported to 68000) roughly system 7 but only single user, integrated shell.
    http://tallyho.bc.nu/~steve/omu.html

    UZI (Z80 processor, ported to 180, 280) roughly system 7: multitasking
    http://www.dougbraun.com/uzi.html

    1. Re:Two independently developed *nices by zulux · · Score: 2, Informative



      Microware OS-9 should be in there - it's UNIX like, in that it can do everything UNIX can do....

      Came out atoun '84 if I remember correctly - Multitasking, Multi user - with an add on multiple windowed graphical shell.

      OS-9 is still used in a lot of set-top-boxes and was used be Phillips's CD-i

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    2. Re:Two independently developed *nices by Steve+Hosgood · · Score: 2, Informative

      As the original author of OMU, I can add a slight clarification. OMU09 (the 6809 version) was indeed single-tasking, but merely because the target system only had 64k of RAM, and it seemed pointless trying to multitask in such a small environment. It implemented an 'exec' call in much the style that MSDOS did, though I didn't know of MSDOS at the time.

      OMU68K was a port of OMU09 to the 68000 done mostly by Terry Barnaby. He ripped out the exec call and implemented fork() instead, so OMU68K did do multitasking.

      Of course, with no MMU on the 68000, it relied on well-behaved processes.

  62. You can also still hear... by Anonymous Coward · · Score: 0

    ...the big *SLAP* sound on the FUD.

  63. Backhanded and Grudging by Outland+Traveller · · Score: 2, Insightful

    While it was humorous to hear the account of the "interview", the article was spoiled by Tanenbaum's regrets, continuingly sour grapes, and display of hubris.

    1. Re:Backhanded and Grudging by jjohnson · · Score: 4, Insightful

      I thought it added credibility to Tanenbaum's recounting of the interview, insofar as he was acknowledging the simple fact that Linus wrote Linux without expressing any solidarity with him. It wasn't a case of academics and hackers closing ranks against a hostile interviewer, it was a competitor acknowledging that no wrongdoing had occurred.

      It's on the order of Michael Cowpland's acknowledging that Microsoft's undocumented APIs were no threat and no hindrance in the development of WordPerfect because they were just for internal plumbing and of no benefit to someone writing an app on top of them.

      --
      Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
    2. Re:Backhanded and Grudging by JohnFluxx · · Score: 1

      I disagree. It shows his angle and his feelings.

  64. On second thought by argoff · · Score: 2, Interesting

    After I saying that, I was thinking, perhaps Linus should be discredtied - not in reguards to being the father of Linux, but for being so neutral about freedom.

    When I think of Linus, I think of Charles Lindburg - he was prestigious hero, and a brilliant person. But when he went on a visit to Germany, all he could see was the armada of beautiful planes, and the amazing technology. He came back to the USA, and proclaimed that we shouldn't fight Hitler. The point being, Lindburg was a brilliant hero who was right about technology, but dead wrong about the importance of freedom - his stance didn't help him or us. This is how I feel about Linus, I'm thankfull he put Linux under the GPL, and that he's responsible for bringing us this cool technology - but I think his casual/neutral attitudes about freedom really suck, and in the long term will cause alot of uneeded harm. The goal shouldn't be to win a popularity contest, or to fit in, but to secure our freedoms in the technology space. Heck, that's the force that made Linux grow so much compaired to other alternatives to begin with.

    What amazes me is how so many people feel that there is nothing wrong with having a technology bias, but then these same people turn arround and think you're a fruit for having a freedom bias. But political freedom isn't voodoo, it's provven itself more than enough - it's not just an opinion or wishfull thinking. I just can't understand why so many people who should know better seem simply ashamed of it.

    1. Re:On second thought by Cytlid · · Score: 5, Interesting
      This is how I feel about Linus, I'm thankfull he put Linux under the GPL, and that he's responsible for bringing us this cool technology - but I think his casual/neutral attitudes about freedom really suck, and in the long term will cause alot of uneeded harm. The goal shouldn't be to win a popularity contest, or to fit in, but to secure our freedoms in the technology space.


      In one of the "Revolution OS" interviews, he states he's merely the engineer, and RMS is more like the philosopher. I think he wants to remove himself from the political aspect and just enjoy the work. Think Einstein and the atomic bomb.
      --
      FLR
    2. Re:On second thought by meadowsp · · Score: 1, Troll

      Way to equate the harm caused by WWII and the apparent harm (to who?) caused by Linus having a neutral attitude to freedom.

    3. Re:On second thought by argoff · · Score: 1, Insightful


      In the information age, there is no neutral technology that can distinguish between free speech content and copyright content - in the end, to impose them, you half to have someone watching and approving. So if we loose the battle to secure freedom in the technology space, then we will loose the battle in the free speech space too - and the conesequences that go with that are well known.

    4. Re:On second thought by argoff · · Score: 1

      Think Einstein and the atomic bomb.



      If anything, that shows you can't seperate technology and politics. Besides, if it wasn't about political freedom - then Einstein would have remained in germany, and worked for Hitler.

    5. Re:On second thought by gowen · · Score: 1
      Think Einstein and the atomic bomb.
      Well, as Einstein aged he became more and more worried about uses of the bomb, and became quite a vociferous peace campaigner. I'm reminded more of this Tom Lehrer couplet:
      'Once the rockets are up, who cares where they come down?
      That's not my department,' says Werner von Braun.".
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    6. Re:On second thought by Valdrax · · Score: 3, Funny

      Oh yeah, bring up the atomic bomb when you want to make apolitical engineers not look like dangerous schmucks.

      --
      If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    7. Re:On second thought by Minna+Kirai · · Score: 1

      remove himself from the political aspect and just enjoy the work. Think Einstein and the atomic bomb.

      That's completely backwards. Regarding the atom bomb, Einstein wasn't "an engineer" at all. He had no technical input to the Manhattan Project- he wasn't even on the site.

      The only way Einstein helped make the bomb was by suggesting to President Roosevelt that the project should be started at all. His role was much closer to a philosopher or politician, and not an engineer (that was Oppenheimer)

    8. Re:On second thought by glitch! · · Score: 1

      Once the rockets are up, who cares where they come down?
      That's not my department,' says Werner von Braun.".


      "But I think our attitude
      should be one of gratitude,
      Like the widows and cripples in Old London Town
      who owe their large pensions to Werner Von Braun."

      I guess you can make any point you wish by quoting Tom Lehrer songs :-)

      --
      A dingo ate my sig...
    9. Re:On second thought by Bob_Robertson · · Score: 1

      The American Constitution is an excellent example of what you're talking about.

      The "power" to limit power was given to government to limit what government could do. As is to be expected, no such luck.

      I, too, shuddered when I read Linus talk about how DRM could be built in without much trouble.

      I'm just glad that everything is still GPL'd, and I can go into the DRM module, patch it to uselessness, and re-release it. Unless, of course, that power is taken away from me by someone with a bigger gun.

      Bob-

      --
      The Ludwig von Mises Institute. The reasoning individuals economics
    10. Re:On second thought by Anonymous Coward · · Score: 0
      and the conesequences that go with that are well known.
      Yes, of course, large-scale genocide will occur.

      Maybe next time you can work in the slave trade as well.

    11. Re:On second thought by ca1v1n · · Score: 4, Insightful

      From everything I've read, I'd say Linus is anything but casual about freedom. What he is *not* is an idealist. That's what we have RMS for. He's a pragmatist, exactly the kind of person you want in charge of an engineering project. Perhaps not the person you want at the head of a movement, but that's not what he is. He's first and foremost an engineer.

      If you want to "secure our freedoms in the technology space" with F/OSS, you need to actually have F/OSS that works well to convince the 99.99% of the world to whom the need and benefit is not intuitively obvious. If all we had were a bunch of RMS clones, we'd be a lot worse off, because he scares the hell out of business types, who are much more concerned with the economic benefits of F/OSS that Linus Torvalds provides.

      We need leaders with a variety of different strengths to spread the message to people with a variety of different interests. Linus Torvalds does an excellent job selling the benefits of F/OSS to engineers. The fact that he lets people like Eben Moglen handle the freedom side doesn't mean that he's causing any harm. If Eben Moglen spent his precious time hacking kernel code, we'd all be worse off.

    12. Re:On second thought by 0racle · · Score: 4, Informative

      Actually its RMS who calls Linus 'just an engineer' and its not a compliment. Its said in the vein of 'just a child,' as in he might be able to do something but he doesn't understand the ramifications. In this case, Linus isn't fighting his (RMS) holy war so he doesn't think highly of Linus and derides him as just an engineer who doesn't understand the whys of the GPL.

      A closer quote from Revolution OS is "he calls me just an engineer."

      --
      "I use a Mac because I'm just better than you are."
    13. Re:On second thought by golgafrincham · · Score: 2, Funny

      at last... hitler, linux and gpl in one sentence (post). congrats.

      --
      beer as in "free beer"
    14. Re:On second thought by TheRevenant · · Score: 1

      You seem to be taking the position that the software has to work well to convince people of the benefits of freedom.

      IMO, this is fallacious logic. Once you do that you're _not_ promoting freedom, you're promoting software that works well. Which is great, but beside the original point...

  65. Btw. I forgot by MemoryDragon · · Score: 2, Informative

    http://os.inf.tu-dresden.de/L4/LinuxOnL4/index.sht ml Is an example of a Linux personality running on a mikrokernel architecture. I havent had a look at it, but the developers claim only a performance penalty of 4% to the monolithic makro kernel standard Linux has.

  66. OS X by ink · · Score: 5, Interesting

    To call OS X a Mach system is a bit disengenious. All I/O operations are handled by the "BSD Subsystem" for performance reasons. This means that all file and network I/O (along with the file security descriptions) are in a "monolithic subsystem" of the uK. Needles to say, this is the most performance-intense section of a UNIX (any?) system. A lot of the message-passing is therefore avoided; and the performance costs that those message passes would incur. Take a look at this url: OS X System Overview See that dotted-line that stretches from the kernel to userland? Tannenbaum would not approve.

    --
    The wheel is turning, but the hamster is dead.
    1. Re:OS X by rizzy · · Score: 2, Informative
      A lot of the message-passing is therefore avoided; and the performance costs that those message passes would incur.

      Crap, if Apple has taken measures to improve the Darwin kernel performance, then I would submit that they have failed miserably.


      Since we're talking kernels here, I don't feel bad bringing out lmbench numbers. here and hereare lmbench runs on the same hardware comparing linux to Darwin. The Linux kernel kicks the crap out of the Darwin kernel, in most cases by an order of magnitude.

    2. Re:OS X by Anonymous Coward · · Score: 2, Funny

      Ah, but clearly the benchmarking procedure is wrong, because it shows something from Apple in a bad light.

    3. Re:OS X by Wesley+Felter · · Score: 3, Interesting

      Yes, Apple made a big mistake with the Darwin kernel. They get none of the advantages of a monolothic kernel (speed) and none of the advantages of a microkernel (isolation). They probably would have been better off just throwing away the NeXT kernel and porting the FreeBSD kernel to PPC.

    4. Re:OS X by PCM2 · · Score: 2, Interesting
      All I/O operations are handled by the "BSD Subsystem"
      If that's true, then why do you see so many Readme notices explaining that to install certain software, you need to be running Mac OS X 10.x with the BSD subsystem installed? In fact, I never understood that qualification -- I thought it was installed by default?

      (I guess the easy answer is that you need to install BSD ... to run all your zombie processes, har har har!)

      --
      Breakfast served all day!
    5. Re:OS X by tverbeek · · Score: 3, Informative

      The software that Apple is referring to with the term "BSD subsystem", and the BSD core I/O routines to which the grandparent is referring, are not the same thing. I don't know for sure, but I believe Apple's talking about some additional libraries and such that folks developing for BSD are used to having installed, but which aren't needed by OS X and typical Apple-centric apps.

      --
      http://alternatives.rzero.com/
    6. Re:OS X by bdaehlie · · Score: 1

      I love when people make it sound like Apple has idiots writing their OS. First off, the Mac OS X works, and quite well at that. Secondly, I'm entirely sure they were advised by many, many people far more knowledgable than you. They probably have really good reasons for doing what they did, and it won't surprise anyone if you don't know what they are. If you're going to challenge Apple's kernel team that far with obviously uninformed conclusions, your audience can be found at a dive bar.

    7. Re:OS X by vadim_t · · Score: 1

      That Apple is a big company with enough money to pay lots of consultants doesn't mean it can't make mistakes. Perhaps you have a point, but since you haven't provided any arguments I can't agree with you at the moment.

    8. Re:OS X by drinkypoo · · Score: 1

      Or how about never buying NeXT, and buying Be instead? If we're going to talk about what Apple probably should have done, let's not be shy.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:OS X by Wesley+Felter · · Score: 1

      I'm pretty ambivalent about that one. BeOS was better than NeXTSTEP in some areas and worse in others. And buying Be wouldn't have brought Steve back.

    10. Re:OS X by Anonymous Coward · · Score: 0

      Yes, Apple made a big mistake with the Darwin kernel. They get none of the advantages of a monolothic kernel (speed) and none of the advantages of a microkernel (isolation).

      While this may be true today, in 2004, when most Mac apps are written to support Mac OS X, this was not true back in 2001, when most applications were written for System 7 and MacOS 8/9. Back then, I'm sure it was helpful to have a microkernel architecture to, I dunno, maybe isolate the classic environment so if it decided to eat shit, it didn't take down the rest of the system. Back then, most people still ran MacOS 8/9 applications, and there were very few native X apps.

    11. Re:OS X by Anonymous Coward · · Score: 0

      XNU, Apple's kernel for Mac OS X, performs pretty damn well I believe. Its not "slow" even if Quartz is heavy and large. I don't see the problem, in various benchmarks it compares well to Linux, though Linux is oftne faster the margin is hardly huge.

    12. Re:OS X by torpor · · Score: 1

      Not to mention the fact that their compilers were, for a fairly long time, not even using the PPC register set appropriately, in order to maintain their NeXT kernel heritage from the 68k days ... it was truly a dream to boot linuxPPC on my tiBook for the first time, consequentially...

      Nevertheless, their system design is pretty nice, and if you do any kind of geneology of the RAD side of comp-sci life, you'll find NextStep in a pretty solid branch, for good reason. The -overall- approach to computer systems design and integration which Apple brought to the Unix table should not be overlooked, either... regardless of a few costly decisions, here and there ...

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    13. Re:OS X by drinkypoo · · Score: 1

      A plan with no drawbacks!

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  67. What about Canada? by Anonymous Coward · · Score: 0

    They have baseball there too. Blue Jays and the Expos.

  68. Really A Secret ? by polyp2000 · · Score: 4, Insightful

    I dont think Linus or anyone else has tried to conceal or hide the origins of linux. Anyone who has taken more than a passing interest in the history of linux knows that Linus got interested in kernel development while hacking Minix which was supplied in source code form in an educational book called "Operating Systems: Their design and Implementation". Rebel Code (Glynn Moody) is an excellent history of linux and open source and a great read. If people are interested in getting a good background its a great place to start.

    I think its fair to say that "shock horror!" Andy Tanenbaum probably "learned" how to write Minix from somewhere else. In any case in the initial phases of Linux I think its fair to say that Linus did 99% of the work. And after the seed was planted.. well lots of people are now involoved with writing linux.

    Its the nature of the beast almost all human acheivements are adaptations of something that came before . Its called development and its incredibly difficult to come up with an idea that doesnt have its basis in something else.

    I challenge anyone to try and come up with an idea that doesnt have its origins in something else.

    nick

    --
    Electronic Music Made Using Linux http://soundcloud.com/polyp
    1. Re:Really A Secret ? by reidbold · · Score: 1

      space elevator

      --
      -Reid
    2. Re:Really A Secret ? by reidbold · · Score: 1

      wait, nevermind, that's stupid.
      it has origins in the elevator.
      *slap forehead*

      --
      -Reid
    3. Re:Really A Secret ? by moexu · · Score: 1

      It reminds me of something in a foreward to one of the Shakespearing plays I was reading for a class. In mentioning the supposition that someone other than Shakespeare wrote the plays the author discussed how some people have difficulty accepting the idea that somone outside of the establishment could create the greatest works ever written in the English language.

      I think the quote he used was, "genuis tends to crop up in the most unlikely of places."

      --
      "Seek first to understand." - Socrates
    4. Re:Really A Secret ? by MyHair · · Score: 1

      I challenge anyone to try and come up with an idea that doesnt have its origins in something else.

      Um, I'll poke a badger with a spoon. No wait, I've heard that one before. (Eddie Izzard)

      Okay, I'll cut off my balls and shove this red hot poker up my ass. Oh crap, that was George Carlin.

      Um, um...I'll bang my noze and sneeze until my toenails fall off. There, that's original!

    5. Re:Really A Secret ? by bestguruever · · Score: 1

      I've got one. Unfortunately I can't describe it since there is nothing to compare it to. You'll just have to trust me. What's the prize?

      --
      if you think this is bad, you should have seen my last sig
    6. Re:Really A Secret ? by rkef · · Score: 0
      I agree completely with what you've stated, and I'd like to also point out another book which, according to the Linux Reading List HOWTO and Linus himself[1], influenced Linus's work on Linux: Design of the Unix Operating System by Maurice J. Bach.

      It is, imho, still a fascinating read.

      [1] The two books I originally used were "The Design of the Unix Operating System" by Bach, and "OS Design and Implementation" by Tanenbaum. [...] The Bach book has a few nice algorithms in it, and I'd suggest reading them too: many of the actual ideas on how something could be implemented came from that.
      - Linus Torvalds, 1992
  69. Re:Let's reignite the fight! by johneee · · Score: 1

    So what's Windows? Micro? Monolithic? Neither?

    I seem to remember reading somewhere that it was Micro, but I don't remember if the source was authoritative, or even if I remember it correctly.

    --
    - ------- There are ten kinds of people in the world. Those who understand binary, and those who... Huh?
  70. Oh no, not again! by the+cleaner · · Score: 1
    But the code was his. The proof of this is that he messed the design up. MINIX is a nice, modular microkernel system...

    Here we go again!

    I can still remember that from the thread (Linux is obsolete) in comp.os.minix and reading it again today as a proof for Linus being the author of Linux mad me laugh so hard I am actually still cherry red and short of breath.

    You rule, Andrew!

    --
    Could be worse. Could be raining.
  71. But what about the rest of the interview? by lawpoop · · Score: 1
    I read the interview, R.I.P. At the beginning, Tanenbaum mentions Brown's reluctance to divulge information about his project, and his general lack of preparedness.

    What about the rest of the interview?

    --
    Computers are useless. They can only give you answers.
    -- Pablo Picasso
  72. Re:Right, thanks for pointing out the origin of a by Anonymous Coward · · Score: 0

    You're kidding right? It's the percentage of times a batter makes it to first base based on the total number of "at bats" or turns at the plate. It's usually based on a single season but is, in rare occasions, in reference to a lifetime statistic. Anyhow, baseball on TV blows, almost as exciting as watching golf.

  73. Whoa... by Anonymous Coward · · Score: 1, Funny

    This is the first time I've seen an article where more of the comments are copies of the /.'d article or mirror links than actual comments...

  74. Who is Justin Orndorf by Anonymous Coward · · Score: 0

    Is this some link with the author of the book?

  75. But the security... by Anonymous Coward · · Score: 0

    He goes on about how secure microkernels are, and that all the security problems of Windows show that he is right, but it seems nobody has pointed out to him that since NT Windows does use a microkernel design. Weird.

    1. Re:But the security... by Anonymous Coward · · Score: 0

      NT claims to use a microkernel, however, that really hasn't been true since NT 3.1, even then, I'm not sure it would count as a 'pure' microkernel by AST's standards.

    2. Re:But the security... by Anonymous Coward · · Score: 0

      "that really hasn't been true since NT 3.1"

      NT 4.0 indeed. Windows NT 3.51 was still quite reasonable about its "microkernelness". Was by NT 4.0 when the graphics environment went into Ring 0.

      By the way, NT 3.51 GUI was a bit sluggish and it tended to block out quite habitually. But then, it was only the GUI, the server was just going on as ever and I was able to schedule a reboot when less lesive (I'm talking about the 3.51 Server version, but since it was just the same as 3.51 Wks with different boot params, I'll assume it is the same for both).

      When I was forced to move to NT 4.0, I have to recognize that the GUI was both more stable and fast, *but* when it crashed (and it did for sure), the whole box crashed. All in all not quite an advance to me.

      I really can't make any good advice about Win2000 and newer since I really didn't give too much time to anyone of them. I'm quite satisfied with almost any Linux flavour I manage (not a surprise, I was administering HP-Ux 9.x back in the days of NT, and it was clearly BETTER by far; it partially wasn't Microsoft fault, after all, Microsoft was running on cheaper hardware -but not unbranded hardware: all NT servers were IBM and HP based- and a lot of different vendors apps which stands for its part of the unstability. But HP-Ux was clearly superior from the sysadmin standpoint too; much easy and clear to administer and so quite more productive. That's because it was a Unix, and that Linux has enterily inherited. And, oh! it really haven't changed neither with Win 2000 or 2003 nor XP so no, no need to give Microsucks the chance *again*).

  76. Re:I still love the classic conversations from 199 by Short+Circuit · · Score: 2, Interesting
  77. Re:Right, thanks for pointing out the origin of a by Quill_28 · · Score: 3, Informative

    In baseball anything over .300(30%) is considered excellent when it comes to hitting.

    So to say you are batting(hitting) five hundred means you were successful half the time.

  78. Roblimo busted Ken Brown back in 2002! by mojoNYC · · Score: 5, Informative

    my first reaction to this attack was, 'who the f### is Ken Brown? as they taught me back in school, 'always consider the source' --if this guy's attacking Linux, he'd better have some solid credentials in the computer industry, right? well, all it took was a Google search, and the first link I hit told me all i need to know: Anti-Open Source lobbyists need love, too Friday October 25, 2002 - [ 03:00 PM GMT ] Topics: Migration - By Robin "Roblimo" Miller - I felt bad for Ken Brown of the Alexis De Toqueville Institution (AdTI) last week... http://www.newsforge.com/business/02/10/25/056218. shtml?tid=19 thanks to Roblimo, we have a first-hand account of Ken Brown's shameless FUD-ing, back in 2002--read this link for a cuttingly funny look at Mr. Browns earlier efforts;> you gotta love the 'thousands of eyeballs' that are working on our side--it more than offsets what M$ gets from spreading it's dirty money around... -DWitt ps. methinks Brown's IP has just gone down the tubes--thank you very much Andy Tanenbaum!

    1. Re:Roblimo busted Ken Brown back in 2002! by Anonymous Coward · · Score: 0

      In the future, could you try to format your posts? It'd make it all so much easier to read.

      And don't post links as text, link them. It's more practical, doesn't clutter up your text, and besides, Slashdot inserts spaces which are a pest for whoever wants to follow your links.

      Just some tips.

    2. Re:Roblimo busted Ken Brown back in 2002! by Anonymous Coward · · Score: 0
      babble babble babble babble ...

      Paragraph much?

    3. Re:Roblimo busted Ken Brown back in 2002! by mojoNYC · · Score: 1
      mea culpa...

      i had originally posted this on Groklaw, which accepts posts in plaintext format, and i hit submit without previewing...

      you're welcome, you insensitive clods!;>

    4. Re:Roblimo busted Ken Brown back in 2002! by Anonymous Coward · · Score: 1, Informative
    5. Re:Roblimo busted Ken Brown back in 2002! by HenrikOxUK · · Score: 1

      methinks Brown's IP has just gone down the tubes

      Could be, but some other goon will just step up in his place to keep the FUD flowing. The vast majority of people including the press and decision-makers do not read Slashdot, but the do read the mainstream press where books like this will get less critical coverage (as do the 'independent', MS-funded research reports).

      The evil empire is still way ahead in the PR game. Just look at the recent decission by the EU Council :(

    6. Re:Roblimo busted Ken Brown back in 2002! by praksys · · Score: 1

      Roblimo's article is an example of one of the worst ways to defend open source, and the GPL.

      Yes it is useful to know that AdTI is funded by MS, and his first hand account of Brown spouting ridiculous claims about "problems" with open source was informative. But attacking AdTI for being "right-wing", and for criticising evironmental research, second hand smoke research, and teachers unions, is a huge mistake. He should have stuck to the matter at hand.

      Open source is not left wing, or right wing, and it will not be made to look more attractive by asociating it with a bunch of other highly dubious causes.

    7. Re:Roblimo busted Ken Brown back in 2002! by Breakfast+Cereal · · Score: 1

      I don't think the point was the political leaning of the group, but rather that there are certain "think tanks" who will whore for anyone who gives them money (tobacco industry, polluters, Microsoft) by producing seemingly neutral, academic papers to support their contributors' agendas. I suspect that if Greenpeace gave them enough money they would reverse their position.

    8. Re:Roblimo busted Ken Brown back in 2002! by zenyu · · Score: 1

      Open source is not left wing, or right wing, and it will not be made to look more attractive by asociating it with a bunch of other highly dubious causes.

      I'm not sure about this. The patent debate seems to have been framed in this way for us, with the Greens taking the side of freedom and the others taking the side or the tyranny of the dinosaurs. Might it make sense to side with the Greens because of this, even outside the election booth? Too at least speak no evil of their other more dubious issues for a while? Flawed allies may be better than fewer allies.

      I am personally libertarian on most issues. My exceptions are that I believe some form of limited copyright, where a more ideological liberterian might believe in no copyright. I think it can be beneficial enough to put up with the restrictions on my freedom, but probably not with the exclusivity and definitely not with such long terms. I also believe in special tax treatment for libraries, but not charities, churches, etc. And, I believe natural monopolies (city streets, last mile, military, etc.) should be only be co-operatively owned, though by as small a constituancy as is reasonable. So you can see I might see issue with the Greens in many respects, but if they are fighting for a basic freedom and no other significant voter block is, where should I stand?

    9. Re:Roblimo busted Ken Brown back in 2002! by Brandybuck · · Score: 1

      The patent debates, along with DMCA, UCITA, etc, are pretty much evenly divided between the left and the right. Since F/OSS advocates tend to be liberal or libertarian, it's naturally assumed that "enemy" conservatives hold anti-F/OSS views. This is grossly incorrect. But every time some big name conservative says something in agreement with F/OSS advocacy, such as Phyllis Schlafly panning the DMCA, the free software community is stunned and amazed.

      Conservatives are pro-business. But they're not necessarily pro-corporation. For every beltway conservative that wants to give Microsoft a "medal of freedom", there's two mainstream conservatives disgusted with the neo-fascism that the Clinton/Bush administrations have brought about.

      --
      Don't blame me, I didn't vote for either of them!
    10. Re:Roblimo busted Ken Brown back in 2002! by zenyu · · Score: 1

      But every time some big name conservative says something in agreement with F/OSS advocacy, such as Phyllis Schlafly panning the DMCA, the free software community is stunned and amazed.

      I was thinking more of the Greens in Europe. The Republicans are not really a conservative party, it's a coalition of economic conservatives, free-marketiers, and social conservatives. The economic conservaties damage the reputation of the party because their first instinct is to preserve existing business models, often overlooking the damage to the market as a whole; but I think F/OSS could convert them to our side with a good economic arguement. The free-marketiers are pretty much already ours except when the bad guys are clever enough to convince them that pure thought should be a private property, just keeping them well informed will keep them on our side. Social conservatives couldn't care less about the issue and will side with whomever delivers the most gifts.

      The Democrats are pretty much just social liberals and everyone too disgusted with some aspect of the Republican party yet too pragmatic to boycott the vote or vote third party. If you look outside the cultural issues there is no cogency to the party, it contains a number economic conservatives and free-marketiers who didn't like the marriage with the each other or to the social conservatives. This is why they flailed so badly on non-social issues when they had congress.

      But ideology is beside the point in the US because this is one of those marginal issues here that politicians can plead confusion on when confronted and vote on purely based on the money appearing in their bank accounts. Here we can only hope to keep a few congress members informed so that when there is an opportunity to reverse the damage we can get a well thought out bill. Nationalism is also against us currently because Microsoft is here, ignore Novell and IBM because might makes right isn't the only consideration for nationalism, you also need a sexy story. Microsoft has it with the story of Bill Gates as scrappy dropout dumpster diving for code and becoming incredibly rich.

      As much as I care about F/OSS as my livelyhood and as an concept, I won't be voting on this issue in the fall. I'll be holding my nose and voting against Ashcroft and co. I never thought I'd feel so stupid for voting against Gore.

      The only real hope in the USA is to convince the presidential candidate in 2008 or 2012 that this esoteric freedom is important, and we start doing that by teaching people all across the political spectrum about this freedom, F/OSS is a part of the toolkit for doing that. In Europe it may be time to take sides, here it's way too early to decide which side that might be or even if we need to take sides.

  79. Addendum by Anonymous Coward · · Score: 0

    "Now cough up that $699!, you cocksmoking teabaggers".

    Please get it right next time.

  80. Hard to refute by segfault_0 · · Score: 2, Interesting

    Its hard to refute Andy Tanenbaums claims for a number of reasons; his background, his education - basically his history. But to another end, you cant even view Browns document to contrast - they have it password protected.

    Putting a story at the top of the front page of your website but making it password protected while no other storys on your frontpage are similarly protected smacks of gun for hire/skewed view/anything for money. Appears to me they want you to read the headline but not read the text, sound familiar?

    These adti individuals dont appear to be concerned with their own credibility and i hope whatever they are being paid is worth it.

    --

    I was crazy back when being crazy really meant something. (Charles Manson)
    1. Re:Hard to refute by stanmann · · Score: 1

      Well how about the fact that he goes to great lengths to point out that he thinks that the kernal design of linux is screwed up(IHNSHO) as the primary evidence that while it is similar to minix it certainly isn't stolen.

      --
      Food not Bombs is a nice platitude but it breaks down when you notice that the Bombees are usually well fed
    2. Re:Hard to refute by segfault_0 · · Score: 1

      The refuting part was more about the back and forth between the two of them and how the interview was conducted, not whether or not Linus wrote an OS. Was Brown really fishing the way he was made out to be in this article? I was just interested to see his version of this particular exchange if he mentions it at all.

      --

      I was crazy back when being crazy really meant something. (Charles Manson)
  81. My view... by Anonymous Coward · · Score: 1, Funny

    Linus: Be serious, saying that the Linux inventors are Tooth Fairy and Santa Claus shows me and the world how inmature you're and obviously puts more fuel to the doubt many of us are having now. An answer like that says to me that there is a more obscure history than we know and is a tipical defensive reaction when you done something wrong.

    I'm convinced that Linux sucks and is now dead, more when his *creator* answer to such allegations on this child way.

    1. Re:My view... by mhyden · · Score: 1

      There is absolutely no way to respond to such a ridiclulous assertaion without giving it some importance. If Linus were to have wasted any more than a breath on a response, it would have shown that he thought the issue was a serious one, when it is absolutely not. It's just a guy trying to sell a book, and the more we can do to avoid drawing attention to the issue, the better.

      --
      I support Mac For the Masses
    2. Re:My view... by CarrionBird · · Score: 1

      He's giving just as much respect as they deserve. Probably more. They're lucky he doesn't sue them for libel/slander.

      --
      Free Mac Mini Yeah, it's
  82. The Important Point by Dark+Paladin · · Score: 5, Insightful

    Whatever anyone does - do not read Brown's book when it comes out.

    Thanks to Mr. Tanenbaum, we have the proof here:

    People can create operating systems on their own. Even UNIX-like operating systems. Linus learned from Mr. Tanenbaum. Linus wrote the first kernel, published it and asked for input, which the rest of the world provided.

    Linus then acted as a proper project manager, and the rest is history.

    So again, whatever people do - do not buy the book.

    Now, here's the problem: if we talk about this upcoming book, people will want to buy it. It's the Gibson Effect - the more its denounced, the more people will want to read it, and next thing you know there will be lines of people at the bookstores claiming they can see Jesus's face on this book.

    So instead, I recommend to all intelligent folks in the programming community: ignore it. From here on out, don't even refer to the book by name, or its foundation, or the author. The more we pretend it doesn't exist and it's not important, the less interest people will have in it. If someone asks (such as a Pointy Haired Boss guy), shrug and lie as you say "No idea. I heard it was some book, but that it wasn't that good." And then shut up and leave it at that.

    Don't give these guys free advertising. Don't even give them an ounce of respect, they don't deserve it.

    1. Re:The Important Point by Fnkmaster · · Score: 4, Informative
      From what I've observed there are lots of programming projects that are "hard" for companies and large organizations because they aren't so amenable to "early partition" as people would like, and yet are substantially easier for one developer (or two in some cases) who partition the problem using internal divide-and-conquer, thus completely understanding the partitioning scheme right off the bat rather than spending months hashing it out at meetings and miscued early development efforts.


      I had an experience where an entire development team of twenty people spent about a year and a half writing a large, grandiose enterprise software system that was supposed to be general-purpose and flexible, but in the end was a real performance turd at the job it was supposed to do. Using what I knew about the actual problem from looking at the previous solution's mistakes and the original problem statement, I rewrote the system from scratch over about 8 weeks at a client's site, averaging about 300 SLOCs a day (coding in Java where I can fly), with one developer helping me on a few specific tasks, and we ended up with a system that was functionally equivalent and about 50 times faster than the previous version because it stripped out all the unnecessary modularity (modularity is good, but if you split something that should be one component into ten, you just get lots of extra overhead) and message-passing that gunked up the original design.


      I can't help but think of the analogy between this project and the Linux/MINIX effort. My knowledge of the problem was informed by analyzing the earlier design, but not a line of code was actually derived from it. And the twenty-some-odd man year effort was replaced neatly by a 3-man-month effort that was superior.


      The moral of the story is that any of us who've been around in the software world long enough will tell you that most any system, assuming you lift all the crazy featurization constraints, can be written fairly rapidly by one person. And that usually you'll get a better result with an early working product and iterative functionality development than you will with a monolithic development effort, assuming you know the architectural parameters going into the effort by having been able to analyze previous efforts at solving a similar problem.


      So the point is... keep the assumptions in mind before you start estimating a project's size and scope, man-hour requirements and so on. Development of UNIX-like OSes was a well-defined, well-understood problem at the time Linus did his work. And don't go claiming that somebody accomplished an impossible task unless you have a REALLY good understanding of the software engineering process in general, and the particulars of the problem they solved - in this case Ken Brown has neither. We didn't really need Mr. Tanenbaum to tell us that, but it shows what a stand-up guy he is that he has made a clear effort to defend Linus despite any past arguments they may have had.

    2. Re:The Important Point by Sajarak · · Score: 1
      I can't help but think of the analogy between this project and the Linux/MINIX effort.

      Or the MULTICS/Unix effort! Admittedly, Unix wasn't nearly as ambitious a design as MULTICS, but look at which one people ended up using.

    3. Re:The Important Point by Anonymous Coward · · Score: 0
      Obviously Ken Brown has NOT read the dozens of reports about development productivity as the number of programmers on a project increase. If only he googled for a half hour, he would find several large well known universities have studied this and found that productivity and quality is higher when 1-2 experts write the program. The real trick, you need the right programmer. Someone who understands the problem domain and has the technical chops to do the job. Those individuals exist, it's just managers don't like it because they don't look important.

      I mean really, if 2-3 top notch programmers can do the job of 30 average programmers, you don't need a high priced manager to get productivity. In most cases, those programmers are self motivated and do the job well on their own.

      What am I talking about. Ken Brown isn't interested in facts, only BS.

    4. Re:The Important Point by Anonymous Coward · · Score: 0

      Hey, in addition to not reading the book, why don't we print out several hundred copies of Mr. Tanenbaum's response (complete with URL reference), and surreptitiously insert the copies into the books? You know, just fold 'em in half, and slip them into the books. After all, people who are going to read this book should at least have the opportunity to learn the whole story behind the book, right?

    5. Re:The Important Point by jpetts · · Score: 1

      Anybody else notice that one of the senior fellows are the Alexis de Tokinville Institute is called Fossedahl?

      Slightly OT, but I think that the FUD we are seeing now is really the beginning of the open, dirty and vicious phase of the war that MS and its shills will be waging on FOSS in general and Linux in particular. This is going to get *very* nasty and dirty before it settles, and all three branches of the US gummint are going to be called into play wherever possible. I really don't believe we have seen anything yet which will compare with the attacks that have been planned and are now moving into execution.

      I'm genuinely scared...

      --
      Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
    6. Re:The Important Point by Dark+Paladin · · Score: 1

      You are the first Anonymous Coward I've ever seen with a good idea.

      (Sniff.)

      That's brilliant - print out the interviews and responses to Mr. Brown's book, wander into bookstores, insert the pages, and leave. Now if anybody picks up the book, they'll have the true story and counterarguments right there for their reading pleasure - heck, they won't even have to buy the book at that point ;).

    7. Re:The Important Point by Fnkmaster · · Score: 1
      You are absolutely right, Mr. AC. Unfortunately, venture capitalists and mid-level managers seem to be alike in this - they really hate the idea that their businesses only asset is one or two top software developers. The first thing they want to do is make the software development process "repeatable and manageable". They will openly admit they'd rather have 30 average programmers doing the work than 2-3 people who need frequent breaks, time-off, and so-on (and where one person quitting can have a devastating effect on the entire company).


      I call this desire the commodification of software developers - I've seen this several times. It's not the best or fastest way to get good software developed, but it feels less risky to some. Unfortunately, from what I've observed in practice, the 1-2 people will generally get a better product out the door than the 30 people. My conclusion is that in practice, it's better to have several crack "teams" that can work on smaller projects highly independently each of which consists of one or two lead programmers and one or two assistants (less experienced people building expertise by doing support programming), with an architect/adviser to help partition problems up. Or if you can keep the products or projects small enough, one team could be managing the development of the entire product/project itself. The project "managers" job should really be bilateral negotiation of featurization and scheduling, the middle man between sales/marketing/etc. and the development teams.


      In practice, though, this is hard to implement this kind of organization because it's hard to hire enough people with existing experience in any given problem domain who are also excellent programmers. This is roughly akin to what Steve McConnell calls the "Chief Programmer team" or "surgical team" structure in Rapid Development, an excellent book even if it is from Microsoft Press, that talks about some of these kinds of issues without getting mired in the latest software engineering fads.


      From what I've seen, one of the biggest risks any early stage company faces is hiring a Director/VP of Software Development who is a mid-level management type who wants nothing more than to maximize headcount so his role is maximally important. Definitely this is not the best way to get good software written rapidly.

    8. Re:The Important Point by Anonymous+Bullard · · Score: 1
      Actually, your own parent post, with some modifications, could work as a "review" on Amazon and other internet book sites. People who might be inclined buy Brown's book are generally of the tech-savvy type who might also value the benefits of peer review.

      Of course the publishers and bookstore chains could also be informed that this particular book is simply ill-informed and ill-intended propaganda with nothing to do with bona fide Information Technology.

      --

      Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?

  83. Of course developers argue... by Banner · · Score: 2, Insightful

    It's what drives them to make stuff, and attempt to make better stuff than the next guy. If they all got along we'd all still be using SLS!

    As it is the arguments and many different flavors of Linux have helped all of us, and brought a great many things to the Linux world. When all the developers stop arguing and dissing each other, that's when -I'll- get worried.

    1. Re:Of course developers argue... by wjeff · · Score: 1

      Somebody please mod parent up, this is one of the most astute observations I have seen on slashdot.

      --
      my old sig is obsolete, and I haven't come up with a stupid enough new one yet
  84. Re:Right, thanks for pointing out the origin of a by Anonymous Coward · · Score: 0

    I don't think that there has ever been a live baseball match on TV in the UK, so no, I am not kidding! Even highlights would be limited to a late night show on a specialist channel.

    What is the plate? The thing that the batter starts on?

  85. Re:Let's reignite the fight! by kjoonlee · · Score: 1

    I always had the idea that Windows NT was micro, based on Mach.

  86. Not quite by Anonymous Coward · · Score: 0

    Batting average is based on hits, not reaching first base.

    A hit can mean reaching first base, but it can also mean a double, a triple or a home run.

    However, if a batter reaches a base via an error, for the sake of his average it is considered an "OUT" and counts negatively towards his average.

    If a batter walks it does not affect his average (although it affects on-base percentage, which is generally a more esoteric measure of batter's prowness). It doesn't even count as an "at bat".

    Finally, if a batter "sacrifices" himself to advance a leading runner, his average is not penalized, and this is the same as a "walk". It is not considered an "at bat".

    Baseball is a wonderful sport. Too bad "Shoeless Joe" Selig is trying to screw it up.

  87. Re:Right, thanks for pointing out the origin of a by Anonymous Coward · · Score: 0

    > In baseball anything over .300(30%) is considered excellent when it
    > comes to hitting.

    So this Ken Brown fellow with the 0.500 rating is doing rather splendidly then?

    I somehow think that the wrong expression was used in submitting the story!

  88. How many programmers does it take to write an OS? by Brackney · · Score: 3, Interesting

    This simply confounded me...

    "Finally, Brown began to focus sharply. He kept asking, in different forms, how one person could write an operating system all by himself. He simply didn't believe that was possible."

    How many people does Brown thing wrote the original version of DOS? Microsoft wouldn't have gotten their big break were it not for Tim Paterson's SOLO coding effort.

    Great article though...

  89. Re:Let's reignite the fight! by SmurfButcher+Bob · · Score: 4, Funny

    Windows is a special 3rd type of kernel, called a "three ring clusterfuck".

    --

    help me i've cloned myself and can't remember which one I am

  90. Re:I still love the classic conversations from 199 by Anonymous Coward · · Score: 0

    Let's see... development on GNU/Hurd started around 1984... ...so maybe by 2024 we will be able to run GNU/Hurd in a production enviroment, which allegedly is still in the 21st century, but by then probably my flying car will be running Linux.

  91. adti link broken by mattfite · · Score: 1

    Has anyone noticed that the original link to the press release has been password protected?

  92. Re:Let's reignite the fight! by Anonymous Coward · · Score: 0

    you forgot the most crappy one:

    micro: windows NT

  93. Even Ziff Davis is saying AdTI's stance is a crock by Zocalo · · Score: 5, Informative

    Matt Loney of ZDNet UK is covering the story, including Andy Tanenbaum's two Euro-cents here. I don't think anyone at AdTI, least of all Ken Brown, is going to be living off royalties any time soon - "falls at the starting gate" indeed. ZD even mention AdTI's ties to Microsoft least there be any doubt, which is nice of them. :)

    --
    UNIX? They're not even circumcised! Savages!
  94. I repent; Ken Brown is an idiot by A+nonymous+Coward · · Score: 1

    It's pretty clear that Ken Brown is an idiot. Here is a quote:

    "It's clear to me, at least from quotes from Tanenbaum, that Linus started from Minix...He just sat down with Minix and wrote this product. By definition, that is not an invention," Brown said. "If you sit down with the Ford blueprints and build a Chrysler and don't give Ford any credit, that's not invention."

    In an interview conducted for the study, Tanenbaum said Minix "was the base that Linus used to create Linux. He also took many ideas from Minix, including the file system, source tree and much more."


    He is clueless and has no brain which could absorb a clue. It would require intelligence to actually claim that Linux copied other work, and he doesn't seem to have the capacity to understand the difference between "inspired by" and "copied". I suppose that is why AdTI hired him, and why SCO or Microsoft ired AdTI.

  95. Don't forget BeOS by no+reason+to+be+here · · Score: 1

    Which is(was) also a microkernel, and incredibly fast.

    1. Re:Don't forget BeOS by Milton+Waddams · · Score: 1

      why can't you crazy BeOS people just accept the fact that BeOS is dead? :p

    2. Re:Don't forget BeOS by no+reason+to+be+here · · Score: 1

      Hey, be nice. It's hard to let go of a loved one. At least I stuck the parenthetical "was" in there.

    3. Re:Don't forget BeOS by chrish · · Score: 3, Informative

      BeOS did not have a microkernel, although it did borrow some ideas from microkernel design. Filesystems, drivers, etc. were loaded into the kernel at boot time, they weren't separate processes.

      --
      - chrish
  96. God bless you, Mr. Tanenbaum by Progman3K · · Score: 3, Insightful

    Thanks for setting the record straight.
    And especially for being brave enough to address the problem of political repression and scapegoating, if albeit a little obliquely.

    --
    I don't know the meaning of the word 'don't' - J
    1. Re:God bless you, Mr. Tanenbaum by Progman3K · · Score: 1

      Sorry to reply to myself, but I was reading the other posts in this discussion, and I noticed that an inordinate amount of them were about the existance of God/Atheism...

      So... We're discussing the Father of Linux and it winds up that we are looking for God?

      if
      Linus == God
      Then
      Bill Gates == ???

      --
      I don't know the meaning of the word 'don't' - J
    2. Re:God bless you, Mr. Tanenbaum by Anonymous Coward · · Score: 0

      Screw Tannebaum for his out-of-line Patriot Act scarcastic criticism. If there is a problem with the law, state it, don't make bullshit up 'cuz it sounds hip and coo'. Or does Andy really seek permission from Ashcroft prior to openning his mouth? Did he seek/get permission prior to making the snide comment? No? Then where are the damn brownshirts to take him down?

    3. Re:God bless you, Mr. Tanenbaum by Anonymous Coward · · Score: 0

      Personally, I'm glad he stated (not in so many words) that he thinks that Lyndie England is getting railroaded.

    4. Re:God bless you, Mr. Tanenbaum by Anonymous Coward · · Score: 0

      The damn brownshirts probably never left the Whitehouse, since he's not in the USA.

  97. In old world media, who creates something of... by dpilot · · Score: 1

    ...value is more important than what gets created.

    You have simply defined why so much of what is made by ??AA members in recent years is a bunch of drek. I'll add my pet theory - that too many of the *who* you talk about are money people first, and not movie or music people.

    --
    The living have better things to do than to continue hating the dead.
  98. If Linus didn't write Linux... by Anonymous Coward · · Score: 0

    ...then all I've got to say
    God didn't make little green apples and it don't rain in Indianapolis in the summertime
    There's no such thing as Doctor Suess
    Disneyland and Mother Goose is no nursery rhyme

  99. Malicious intent by mst76 · · Score: 4, Interesting

    After reading this, the Tanenbaum interview and this, there is little doubt that of Brown and the AdTI were determined in their slander campain against Linux from the start. From the AST interview, it is clear that he is just fishing for incriminating quotes. It is well known that initial Linux development took place on (and was inspired by) Minix. With selective quoting, it's likely that he will have AST seemingly accusing Linus of stealing Minix. One of his more persuasive arguments to the laymen will be that it took the highly experienced professor Tanenbaum years to develop Linux, while kid Linus hacked his OS together in 6 months. Of course, he knows this is not a truthful representation, but that doesn't matter as long as it will get him headlines. We (and AST it seems) may regard people like Brown and McBride as dumb and ignorant. But we should beware, these people are of a kind that we do not encounter often day-to-day: people with malicious intend.

    1. Re:Malicious intent by bstadil · · Score: 4, Informative

      Well they tried this crap two years ago at the behest of Microsoft. The article was so bad that it was pulled after just one day. Look here for a copy, captured before it was pulled..

      --
      Help fight continental drift.
  100. This whole thing is wonderful. by Cytlid · · Score: 2, Interesting

    I read the interview and followed the other two articles, the original and Linus' reply. I think this stuff is a must-read. [conspiracy theory] Perhaps someone, somewhere funding anti-Linux FUD is realizing the whole SCO thing is falling through? [/conspiracy theory]. It outlines the differences between what Linus believes in and what Tanenbaum believes in. The more articles I see like this, the better I feel. There's a lot of people out there who know the truth, and I don't care how many billions you have, your underhanded sneakiness will be revealed. This whole situation has been the posterchild for Open Source.

    --
    FLR
    1. Re:This whole thing is wonderful. by Anonymous Coward · · Score: 0

      i don't want to agree with you. m$ probably is funding both indenpendantly.

  101. Re:I still love the classic conversations from 199 by mst76 · · Score: 3, Informative

    > MINIX is licensed under the BSD licence, as mentioned in the article.

    Not until 2000, when Prentice Hall finally came to realize that nobody would pay for Minix with Linux and the BSDs out there.

  102. Re:Right, thanks for pointing out the origin of a by Galvatron · · Score: 1
    So this Ken Brown fellow with the 0.500 rating is doing rather splendidly then?

    I think it was meant as a joke. Because not only is Tanenbaum arguing that Linus DID invent Linux, but he also states that this guy was one of the worst interviewers of all time. So saying he's batting five hundred (that's how it's said out loud, not "point five" or whatever) when he's an incompetent idiot, is meant to be funny.

    --
    "The question of whether a computer can think is no more interesting than that of whether a submarine can swim" -EWD
  103. Level-headed and interesting by Junks+Jerzey · · Score: 5, Insightful

    I know many in the Linux community like to paint Mr. Tanenbaum as a bitter lunatic, but this is a great article, one that every Linux user/zealot should read.

    First, he goes into the history of why people were souring on UNIX and the various independently-written UNIXalikes. These were mostly individual projects, which really sets the record straight for the people who seem to think that Linus was the first person to do this, and that Linus was somehow the only person intelligent and manly enough to write his own kernel.

    At the same time, he lays out the history of UNIX clones, of which Linux was definitely one. It's surprising to me how many people seem to think of Linux as a great, independent OS, and fight so hard to deny that it has roots in UNIX. Of course these people are mostly young and don't know much about computer history. In that respect, this is an educational article.

    And, yes, he does talk about the micro vs. monolithic kernel issue, but he does so without fanaticism, and, you know, what he says is generally correct. He's all for small and reliable software, which is something that UNIX was originally but rapidly became the antithesis of. Performance issues, back when people were using 4.77 and 8 MHz desktop processors, well, let's just say that things were different then. Now you have people writing big applications in Python. The real reason Linux ended up with a monolithic kernel is because that's what Linus understood and it was easier for him to write that way.

    1. Re:Level-headed and interesting by Anonymous Coward · · Score: 0

      Performance issues, back when people were using 4.77 and 8 MHz desktop processors, well, let's just say that things were different then. Now you have people writing big applications in Python.

      As opposed to back then, when you had people writing big applications in interpreted languages like BASIC, UCSD Pascal, and Lisp?

      Interpreted languages are nothing new. "Performance at all costs" was a brief blip during the late '80s and early '90s; real programmers have been sacrificing runtime speed for development speed for decades.

      It's surprising to me how many people seem to think of Linux as a great, independent OS, and fight so hard to deny that it has roots in UNIX.

      It's surprising to me how many people seem to thing of Python as a great, independent language, and fight so hard to deny that it has roots in BASIC. :p

    2. Re:Level-headed and interesting by Anonymous Coward · · Score: 2, Funny

      Mr. Tanenbaum isn't a bitter lunatic. He's a professor.

      You may have trouble understanding this distinction-- it is, I admit, very fine-- but once you do understand many of his actions make much more sense :)

    3. Re:Level-headed and interesting by Junks+Jerzey · · Score: 1

      As opposed to back then, when you had people writing big applications in interpreted languages like BASIC, UCSD Pascal, and Lisp?

      On circa 1990 PCs, fairly rarely.

      It's surprising to me how many people seem to thing of Python as a great, independent language, and fight so hard to deny that it has roots in BASIC. :p

      Did I say it was great? If anything Python has roots in Lisp. At least you have Lisp experts like Norvig and Graham promoting Python as a reasonable alternative to Lisp.

      Personally, I don't see much connection between Python and BASIC. If anything hurts Python, it's being overly object-oriented.

    4. Re:Level-headed and interesting by AndroidCat · · Score: 1

      Dartmouth BASIC was compiled. And your "blip" was just one peak of a cycle that has repeated several times.

      --
      One line blog. I hear that they're called Twitters now.
    5. Re:Level-headed and interesting by Anonymous Coward · · Score: 0
      And, yes, he does talk about the micro vs. monolithic kernel issue, but he does so without fanaticism, and, you know, what he says is generally correct.

      Did you even RTFA? He sounded very very bitter and reasonably fanatic ("of course micro-kernels are the only way to go"). And whether he's correct or not is still hotly debated.

  104. Re:Right, thanks for pointing out the origin of a by Anonymous Coward · · Score: 0

    Channel 5 usually show all the obscure American sports late at night.

  105. Did they have a fight over a girl? by Derek · · Score: 4, Interesting

    What does this quote reference?

    "Some of you may find it odd that I am defending Linus here. After all, he and I had a fairly public "debate" some years back. My primary concern here is getting trying to get the truth out and not blame everything on some teenage girl from the back hills of West Virginia."

    Just curious...
    -Derek

    1. Re:Did they have a fight over a girl? by jake_eck · · Score: 2, Informative

      What does this quote reference? "Some of you may find it odd that I am defending Linus here. After all, he and I had a fairly public "debate" some years back. My primary concern here is getting trying to get the truth out and not blame everything on some teenage girl from the back hills of West Virginia."

      I thought it was a reference to Lindie England.

    2. Re:Did they have a fight over a girl? by eggboard · · Score: 4, Informative

      The teenage girl is a reference to the smiling, cigarette-smoking woman Lynndie England pictured pointing at a humiliated Iraqi man's genitals, and the fact that she and her smiling comrades will take the fall for Donald Rumsfeld and the rest of the chain of command.

      --
      Freelance tech journalist for the Economist, MIT Technology Review, Macworld, and others
    3. Re:Did they have a fight over a girl? by Darth23 · · Score: 1, Offtopic

      You're being patently unfair to Mr. Rumsfeld (or Darth Rumsfeld, as I like to call him).

      He publicly stated that there will be a full investigation AND that there were only low level grunts involved. Only and brilliant, insightful and honorable man can offer the conclusion that a 'full investigation' will rech before it's ever launched.

      While some people would claim that the a proper course to follow in an inquiry would be to actually interview people at the lowest level, then one level higher, then right up the chain of command, and maybe even talk to some of the actual PRISONERS who were featured in the famous photos or housed at the prison, I'm quite sure that the whitewas- er full inquiry that is going on now will discover all the final facts that the Amercian public is entitled to.

      --

      -------- In Soviet Russia, "Soviet Russia" sigs hate Slashdot.

    4. Re:Did they have a fight over a girl? by Anonymous Coward · · Score: 0

      Ah yes, they are good soldiers. Let's all be supportive of their brave efforts to take the fall for Donald Rumsfeld. This steadfast protection of the chain of command truly displays the spirit of America.

    5. Re:Did they have a fight over a girl? by Anonymous Coward · · Score: 1, Funny
      pointing at a humiliated Iraqi man's genitals

      How do you know he was humiliated - some men pay good money for that kind of treatment! :) I call it a freebie, myself.

    6. Re:Did they have a fight over a girl? by Anonymous Coward · · Score: 0

      ...whom you have already concluded are guilty. Your clairvoyance is most impressive. Any recomendations for the Belmont stakes?

    7. Re:Did they have a fight over a girl? by Anonymous Coward · · Score: 1, Insightful

      maybe even talk to some of the actual PRISONERS who were featured in the famous photos or housed at the prison

      Dead men tell no tales...

    8. Re:Did they have a fight over a girl? by mandolin · · Score: 1

      Actually, I'd like to see the entire chain of command incarcerated, including Ms. England (but with progressively stiffer sentences as you went up the chain).

    9. Re:Did they have a fight over a girl? by Anonymous Coward · · Score: 0

      Actually, they tell a lot more than some living persons with proper techniques. That's what forensic science does.

    10. Re:Did they have a fight over a girl? by Anonymous Coward · · Score: 0
      Torvalds and Tanenbaum had a debate regarding monolithic kernels versus microkernels. Tanenbaum favored microkernels. Torvalds favored monolithic kernels.

      Tanenbaum took stabs at Linux. Torvalds took stabs at Minix. It turned into a famous flamefest.

    11. Re:Did they have a fight over a girl? by rthille · · Score: 1

      That's not true. Because after you start with the live person, asking them questions and such, you can turn them into dead people and use forensics on them. :-)

      --
      Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
  106. The microkernel neverending story by Anonymous Coward · · Score: 0

    "The proof of this is that he messed the design up. MINIX is a nice, modular microkernel system, with the memory manager and file system running as user-space processes. This makes the system cleaner and more reliable than a big monolithic kernel and easier to debug and maintain, at a small price in performance, although even on a 4.77 MHz 8088 it booted in maybe 5 seconds (vs. a minute for Windows on hardware 500 times faster)."

    Sheesh. Windows now uses microkernel (NT kernel) as Minix does. Your demonstration is not convincing, Mr Tanenbaum :)

    1. Re:The microkernel neverending story by bonch · · Score: 0, Troll

      NT isn't a microkernel. It's a mix of architectures.

      Honestly, I think it's insane that to you have to compile the Linux kernel just to get drivers, but that's just me thinking all modern and against the hivemind grain...

  107. Re:Let's reignite the fight! by Waffle+Iron · · Score: 2, Informative
    So what's Windows? Micro? Monolithic? Neither?

    DOS, Win3.1, 95, 98, Me are all super-monolithic. Your copy of Minesweeper.exe runs in the same space as everything else and essentially becomes part of the kernel.

    NT 3.51 was a fairly pure microkernel implementation. However, it had some performance issues, so Microsoft moved a few things like the graphics drivers back into the kernel for later versions of NT, Win2K and WinXP. Modern versions of Windows are thus a kind of hybrid.

  108. I heard from Ken Brown by Anonymous Coward · · Score: 0

    Ken Brown sent me an email about my early involvement in Linux. Unlike Dr. Tanenbaum I looked him up on Google before responding.

    I then forwarded the email to Linus with a heads up. The lesson is, figure out who you are talking to before speaking.

  109. Well then, by lumpenprole · · Score: 1

    I guess we should ask who wrote this book? I mean, if Ken Brown just went around and asked a bunch of people for their opinion, then typed up the parts of others opinions he liked, and added some comments, then it looks like he didn't write his book did he? I think Tanenbaum should sue him for a slice of the royalties.

    Say, $699 per book?

    --
    Disclaimer: MINAA (Mummy! I'm Not An Animal!)
  110. Re:Right, thanks for pointing out the origin of a by Quill_28 · · Score: 1

    >So this Ken Brown fellow with the 0.500 rating is doing rather splendidly then

    Only if he was playing baseball, most other things he's not doing so good.,

  111. Re:I still love the classic conversations from 199 by ColonelPanic · · Score: 1

    I've often wondered what things will be like when Hurd is ready

    We'll be flying our rocket backpacks around our Martian colony and speaking Esperanto.

    --
    "Skill shows through where genius wears thin." -Wittgenstein || Religion: uniting aviation and architecture.
  112. I really don't like... by Anonymous Coward · · Score: 0

    ...his stereotyping reference to who plays baseball. Before I had to grow up, go to college, and get a job (before I left highschool), I played baseball for 13 years (from the time I was 4 until the time I was 17). Baseball is a much more international sport than the bum (he is bum a for more than just this reason) portrays it (that is why it is an Olympic sport).

    Also, the guy really doesn't understand people who use operating systems. That is why Minix never became as popular as any other Unix. Operating Systems are not useful unless they actually are operated.

  113. Summary: by nanojath · · Score: 3, Insightful
    From the AdTI website: " AdTI's Kenneth Brown reviews the origins and development of Linux -- in light of repeated expressions of contempt for intellectual property rights by Torvalds and some (but by no means all) open source programmers." (emphasis added).


    I don't have to read the book -particularly after reading Tanenbaum's very convincing presentation that the author doesn't know dick about intellectual property, not to mention he was basically lying about writing a book about the history of Unix, when it is clear his notion from the get go was to write a book titled "SCO is telling the truth about Linux - Really!" The quote above makes it clear that rather than bother to, oh, find some actual copyrighted code in Linux that is stolen, he is arguing the stellar logic that:
    1) Open source advocates are contemptuous of copyright law
    2) People who are contemptuous of copyright law are plagiarists
    3) The people who wrote Linux are open source advocates...


    Remind me what de Toqueville said about weaselly corporate shills again?


    A quote from the Yahoo article -


    "The report," according to Gregory Fossedal, a Tocqueville senior fellow, "raises important questions that all developers and users of open source code must face. While you cannot group all open source programmers and programs together; many are rigorous and respectful of the intellectual property rights, while others speak of intellectual property rights with open contempt." -Emphasis, again, added.


    Get it? Failing evidence for any credible claim that they are actually TREATING intellectual property rights with contempt, they will note that they "speak" of them with open contempt... as if there were something wrong with that.

    --

    It Is the Nature of Information to Transgress Artificial Boundaries

    1. Re:Summary: by Anonymous Coward · · Score: 1

      As an 'open' source developer, a user of 'open' source software, and advocate of 'open' source and freedom, and a believer in the rights of man (over corporation or government), and a lover of liberty, I speak with 'open' contempt on subjects that are 'openly' contemptible.

      Intellectual Property
      Microsoft Security
      Honest Politicians
      Congressional Ethics
      sane /. debate

  114. GLX is a fair name by beforewisdom · · Score: 1, Insightful

    GLX ( GNU, Linux, XWindows ), an alternative name for the operating system is very fair, IMHO.

    You can't do much with just the kernel ( linux ).

    You can't do much with just the software GNU made

    You can't do much with just XWindows.

    Give everyone credit for "GLX".

    I think it is catchier sounding the "Linux" and a whole let less clunky then "GNU/Linux'.

    Steve

    1. Re:GLX is a fair name by the+eric+conspiracy · · Score: 1

      You can't do much with just XWindows.

      You can do a lot without XWindows. any distros have an option to install Linux without X for use on servers.

    2. Re:GLX is a fair name by beforewisdom · · Score: 1

      Um, yah.
      My point, which you quoted, was that:
      "You can't do much with ***___JUST___*** XWindows."
      Steve

    3. Re:GLX is a fair name by Anonymous Coward · · Score: 0

      and it's pronounced "glitch".

    4. Re:GLX is a fair name by jc42 · · Score: 1

      My point, which you quoted, was that:
      "You can't do much with ***___JUST___*** XWindows."


      Sure you can. You can build an "X terminal". I've worked several places where that's what most of the machines were. You get a few xterms with $DISPLAY set up appropriately, and a small library of the obvious comm apps. You telnet/rsh/ssh to other machines and start running apps, whose windows appear on your screen. Some just have a window that lets you pick the remote host you want, a connection protocol, and a preferred terminal emulator (if any). Works like a charm. Aside from the need to connect to remote hosts initially, it's not materially different from a full workstation.

      Of course, there really is more than just X Windows. There's a minimal OS (such as Minix or Qnix) with device drivers. There are a few local apps that are mostly the comm tools that you need to get out of the terminal. But this is just the stuff you need so that the X server can run in a useful manner.

      (Newer X terminals now include things like browsers, and some even include a mail reader, which is sorta getting far away from the purity of the earlier X terminals. With time, they'll be fullblown systems in their own right. It's called creeping featuritis. ;-)

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    5. Re:GLX is a fair name by Anonymous Coward · · Score: 1, Interesting

      Wtf!?

      Why introduce a new name at all?

      and you do are aware of SGI's 3D infrastructure in X11 named GLX? also, X.Org and everyone else strongly discourage people to name X "XWindows", it's X or "The X Window System". Also there are production embedded Linux systems without GNU (my VoIP modem for example), and less embedded systems without X (my router for example)... All linux are not Mandrake.

      end rant

    6. Re:GLX is a fair name by the+eric+conspiracy · · Score: 1

      My point, which you quoted, was that:
      "You can't do much with ***___JUST___*** XWindows."


      Yes, but that is not the issue. You want to name it GLX, but X is not always a critical component. Just GL works fine in many applications.

    7. Re:GLX is a fair name by WWWWolf · · Score: 1
      Give everyone credit for "GLX".

      Personally, I only give GLX's credit for SGI and the contributors. The only estabilished definition for GLX, of course, being the glue layer between OpenGL and X11, which is pretty widely used these days, coming right out of box with XFree86 and all.

      Lesson number whatever: If you come up with a cool term, at least bother to google for it =)

    8. Re:GLX is a fair name by beforewisdom · · Score: 1

      Heh. I challenge you to find a 3 character abbreviation that is not taken. I would add "sue me", but these days that is just asking for trouble. Steve

    9. Re:GLX is a fair name by nomadic · · Score: 1

      Heh. I challenge you to find a 3 character abbreviation that is not taken. I would add "sue me", but these days that is just asking for trouble.

      Ýß

    10. Re:GLX is a fair name by leandrod · · Score: 1
      > there are production embedded Linux systems without GNU

      Probably not true. Applications aren't coded to Linux the kernel, but to the GNU C library.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  115. It's not gone, just /.ed by AuraSeer · · Score: 1

    I managed to get to the article. All it took was hitting Reload a few times, just like a normal slashdotting.

    The article hasn't been taken down.

  116. Ken Brown =~ /Idiot | MS Lackey/ by i_want_you_to_throw_ · · Score: 1

    Really does anything more need to be said?

    1. Re:Ken Brown =~ /Idiot | MS Lackey/ by Anonymous Coward · · Score: 0

      Shat ap!

      GrimRC

  117. Writing a kernel is easy! by Anonymous Coward · · Score: 5, Insightful

    Writing a simple OS kernel is easy. I wrote one, and believe me, it wasn't that hard. At the university where I am a grad student, we require the undergrads to write most of an OS kernel (including virtual memory and a filesystem) in a one-semester course. I read alt.os.development regularly, and there are high school students who are writing OS kernels. (I'm often depressed by the fact that they are much better programmers than I am :-)

    Writing a scalable, production-quality OS kernel is another matter entirely. That takes hundreds or thousands of person-years by talented programmers.

    Ken Brown is obviously a complete shithead if he doesn't understand this distinction. AST's rebuttal made the facts of the matter abundantly clear, and I'm sure any competent OS developer he asked would have told him the same thing.

    1. Re:Writing a kernel is easy! by cpghost · · Score: 1

      Writing an efficient kernel is much more difficult. L4ka::Pistachio is a good example.

      --
      cpghost at Cordula's Web.
    2. Re:Writing a kernel is easy! by denlin · · Score: 3, Interesting

      about 8 years ago, while still an undergrad, we had an os theory class where over the period of the semester implemented crude implementations of the various parts needed for a primitive os. it worked, albeit not wonderfully, but we were all quite proud with ourselves at the end of the semester. learned more in that one class, than nearly the rest combined.

      --
      Yes, I have RTFA. Yes, I have a girlfriend. Yes, I'm new here. And no, I don't want a free iPod.
  118. Re:Right, thanks for pointing out the origin of a by fatray · · Score: 1

    One of my New Zealand friends once said to me:

    "Now you're batting a thousand."

    I asked him if he knew where that came from (I, of course, thought he must have heard that from me). I think baseball references and cliches are pretty widespread these days. Blame us travelling Americans and the fact that our tv shows are shown everywhere.

    A lot of people are interested in American sports. Even baseball shows on up New Zealand cable TV once a week or so (in season). I much prefer rugby to baseball.

  119. Re:I still love the classic conversations from 199 by Dave_bsr · · Score: 1

    given your sig, shouldn't your nick be "byoGNU/linux" ?

    --


    Who is this Anonymous Coward character, how does he post so much, and why is he always such a whore?
  120. Google search for MINUX by hey · · Score: 2, Funny
    If you do a Google search for MINUX, it says:
    Did you mean: LINUX
    I am sure that makes Tanenbaum happy.
    1. Re:Google search for MINUX by Wm_K · · Score: 3, Insightful

      no you didn't mean linux, i'm sure you meant MINIX

    2. Re:Google search for MINUX by Anonymous Coward · · Score: 0, Informative

      If you do a Google search for MINUX, it says:
      Did you mean: LINUX I am sure that makes Tanenbaum happy.


      Dumbass. Next time try typing in the correct name, MINIX not minux.

    3. Re:Google search for MINUX by hey · · Score: 1

      Yes, you are right. I made a typo and thanks for not calling me a dumbass.

      By the way, I tried that Minux (minimal Linux, I guess).
      Seems like a really neat idea - a one floppy Linux.
      It printed "Loading" (or something like that) then printed out some garbage (maybe a register dump) in an infinite loop. Too bad. This was on a Pentium 4 that has run Windows2000 and PhatLinux.

  121. Wow. Mod this up by Anonymous Coward · · Score: 0

    This is a kid who was hired to do a fishing expedition in anticipation of hard questions.

    You add this up with MS funding and you've got a smoking gun here.

    Why doesn't someone email Justin and ask him who the bag man is/was?

  122. Re:Grain of salt please by gamorck · · Score: 1

    Wow. I don't comment on here much anymore but somebody who gets the joke ought to mod the parent up as funny. Then again they are probably watching too much anime around here to have time for cultured films like "The Royal Tenenbaums".

    Sigh...

    --
    I love idealists not because I am one, but because they make life bearable for pragmatists such as myself.
  123. I guess Stallman will anwer next by Anonymous Coward · · Score: 0, Flamebait

    and it's probably not hard to guess what he did tell in the interview. "No Linus did not write Linux, because it's actually GNU/Linux and consist of a lot of GNU tools and Linus did just write the Kernel". Wanna bet?

  124. And look at this Was:The plot thickens by Anonymous Coward · · Score: 1, Interesting

    http://groups.google.com/groups?dq=&start=75&hl=en &lr=&ie=UTF-8&group=linux.samba&selm=1Xf0Z-7VF-11% 40gated-at.bofh.it

    From: Justin Orndorff (raison__d_etre@hotmail.com)
    Subject: [Samba] research inquiry
    This is the only article in this thread
    View: Original Format
    Newsgroups: linux.samba
    Date: 2004-05-18 08:50:10 PST

    Greetings,

    I'm currently doing research into corporate contributions towards open
    source projects, such as Linux. One of the recent Credits Files lists Mr.
    Anton Blanchard as a contributor. Is Mr. Blanchard still an employee with
    the company?

    Also, does the company have any policies regarding open source contributions
    by employees? If so, are there any differences between on and off the clock
    contributions?

    Thanks very much for your time and apologies for posting on your mailing
    list. I did not find any other contacts on your website related to this side
    of your business.

    Best,
    Justin Orndorff

    1. Re:And look at this Was:The plot thickens by Anonymous Coward · · Score: 0

      And check out the date: 5/18/04. I guess we can expect more FUD from from Alexis de Tacoville. Note also that Justin stopped using his adti email .

      SCO is winding down, here comes the next attack.

  125. No. by Anonymous Coward · · Score: 2, Informative

    No. No he didn't.

    Read more history.

    More importantly, he didn't "invent" basic, he stole it from http://inventors.about.com/library/inventors/blbas ic.htm

    Dartmouth.

    That's a more interesting question is it not? That Bill Gates and Paul Allen stole Basic from Dartmouth?

  126. What about Royal? by daperdan · · Score: 2, Insightful

    Maybe we should consult Royal and Chaz Tanenbaum. This whole thing about Linux not being the author of Linux is about as funny as the artwork from the Movie the "Royal Tenenbaums". Absurdities like these really make me laugh...

  127. Re:I still love the classic conversations from 199 by Al+Al+Cool+J · · Score: 1
    "The name of the place is Babylon5."

    I'd just lust like to say, in a completly off-topic way, that that line alway bugged the heck out of me. It is such horribly awkward phrasing. What is wrong with "The place is Babylon 5"?

    If they were trying to come up with something to rival Kirk's "To boldly go...", they failed.

    I think that clumsy line is the main reason I gave up watching B5.

  128. Kenneth Brown by Seanasy · · Score: 2, Interesting

    He's also affiliated with Democratic Centruy Fund:

    We offer the opportunity for competitive rates of return on investment, but can manage funds only for qualified individuals and institutions who appreciate the potential and risks inherent in dealing in these markets.

    Because we protect the confidentiality of our investors, and our own methods, we can make only certain information about our firm available on the internet, through the operating links below.

    Sounds like "If you've got a lot of money that you can afford to lose and don't ask too many questions, invest with us." Most of the links on that site are broken, too.

    It always amazes me that people have the nerve to pull stunts like this guy does. I just have to believe that his Karma will catch up with him eventually.

  129. Re:I still love the classic conversations from 199 by maitas · · Score: 1

    It has recently changed and now is GPL

  130. The dog that didn't bark by maroberts · · Score: 4, Insightful

    Quote from Tannenbaum:
    That's when I discovered that (1) he had never heard of the patent, (2) did not know what it meant to dedicate a patent (i.e., put it in the public domain), and (3) really did not know a thing about intellectual property law. He was confused about patents, copyrights, and trademarks.

    Do you not find it strange that the President of an organisation involved in arguments about patents, copyrights and trademarks should be so ignorant of patents, copyrights and trademarks?

    --

    Donte Alistair Anderson Roberts - hi son!
    Karma: Chameleon

  131. Article text by Anonymous Coward · · Score: 0, Informative

    Background

    The history of UNIX and its various children and grandchildren has been in the news recently as a result of a book from the Alexis de Tocqueville Institution. Since I was involved in part of this history, I feel I have an obligation to set the record straight and correct some extremely serious errors. But first some background information.

    Ken Brown, President of the Alexis de Tocqueville Institution, contacted me in early March. He said he was writing a book on the history of UNIX and would like to interview me. Since I have written 15 books and have been involved in the history of UNIX in several ways, I said I was willing to help out. I have been interviewed by many people for many reasons over the years, and have been on Dutch and US TV and radio and in various newspapers and magazines, so I didn't think too much about it.

    Brown flew over to Amsterdam to interview me on 23 March 2004. Apparently I was the only reason for his coming to Europe. The interview got off to a shaky start, roughly paraphrased as follows:

    AST: "What's the Alexis de Tocqueville Institution?"
    KB: We do public policy work
    AST: A think tank, like the Rand Corporation?
    KB: Sort of
    AST: What does it do?
    KB: Issue reports and books
    AST: Who funds it?
    KB: We have multiple funding sources
    AST: Is SCO one of them? Is this about the SCO lawsuit?
    KB: We have multiple funding sources
    AST: Is Microsoft one of them?
    KB: We have multiple funding sources

    He was extremely evasive about why he was there and who was funding him. He just kept saying he was just writing a book about the history of UNIX. I asked him what he thought of Peter Salus' book, A Quarter Century of UNIX. He'd never heard of it! I mean, if you are writing a book on the history of UNIX and flying 3000 miles to interview some guy about the subject, wouldn't it make sense to at least go to amazon.com and type "history unix" in the search box, in which case Salus' book is the first hit? For $28 (and free shipping if you play your cards right) you could learn an awful lot about the material and not get any jet lag. As I sooned learned, Brown is not the sharpest knife in the drawer, but I was already suspicious. As a long-time author, I know it makes sense to at least be aware of what the competition is. He didn't bother.
    UNIX and Me

    I didn't think it odd that Brown would want to interview me about the history of UNIX. There are worse people to ask. In the late 1970s and early 1980s, I spent several summers in the UNIX group (Dept. 1127) at Bell Labs. I knew Ken Thompson, Dennis Ritchie, and the rest of the people involved in the development of UNIX. I have stayed at Rob Pike's house and Al Aho's house for extended periods of time. Dennis Ritchie, Steve Johnson, and Peter Weinberger, among others have stayed at my house in Amsterdam. Three of my Ph.D. students have worked in the UNIX group at Bell Labs and one of them is a permanent staff member now.

    Oddly enough, when I was at Bell Labs, my interest was not operating systems, although I had written one and published a paper about it (see "Software - Practice & Experience," vol. 2, pp. 109-119, 1973). My interest then was compilers, since I was the chief designer of the the Amsterdam Compiler Kit (see Commun. of the ACM, vol. 26, pp. 654-660, Sept. 1983.). I spent some time there discussing compilers with Steve Johnson, networking with Greg Chesson, writing tools with Lorinda Cherry, and book authoring with Brian Kernighan, among many others. I also became friends with the other "foreigner," there, Bjarne Stroustrup, who would later go on to design and implement C++.

    In short, although I had nothing to do with the development of the original UNIX, I knew all the people involved and much of the history quite well. Furthermore, my contact with the UNIX group at Bell Labs was not a secret; I even thanked them all for having me as a summer visitor in the preface to the first edition of my book Computer Networks. Amazingly, Brown knew not

  132. Actually by Anonymous Coward · · Score: 0

    The commies are all gone.

    He's more likely a terrorist. An islam-loving, jesus-hating, towel-wearing, beard-wearing terrorist.

    Not the first time, either.

    1. Re:Actually by Anonymous Coward · · Score: 0

      We'll wipe out the terrorists just like we wiped out the commies. Smoke 'em out and don't let them crawfish their way outta this one!
      The only punishment suitable is DEATH!

  133. Re:I still love the classic conversations from 199 by Pedersen · · Score: 0, Redundant

    "This is the story of the last of the Babylon stations. The year is 2258.

    "The name of the place is Babylon5."

    "Oh, and GNU Hurd was just released."

    Dude, you so rock! I just about spit my drink through my thanks to that. Thank you!

    --

    GPL made simple: What was my stuff is now our stuff. If you improve our stuff, please keep it our stuff.
  134. Re:I still love the classic conversations from 199 by Anonymous Coward · · Score: 0

    I think you want one of the later intros with "It was the year of flamewars.."

  135. Canada by xanadu-xtroot.com · · Score: 0, Offtopic

    The Canadians know aboot baseball...

    --
    I'm not a prophet or a stone-age man,
    I'm just a mortal with potential of a super man.
  136. ...and here he is on devhardware.com and others! by aug24 · · Score: 4, Informative

    Interesting...! I think I'll email PJ with this little lot!

    J.

    --
    You're only jealous cos the little penguins are talking to me.
  137. If you "don't need them" by Anonymous Coward · · Score: 0

    Then I kind of have to wonder, why is that every publically sold consumer microkernel operating system I've ever seen (Mac OS X, Windows NT) wound up giving up and debasing the microkernel model before long because actually sticking to principle provided unacceptable performance?

    That sounds like "need" to me

    1. Re:If you "don't need them" by Anonymous Coward · · Score: 0

      I don't think BeOS or QNX "debased the microkernel model".

    2. Re:If you "don't need them" by juhaz · · Score: 1

      I don't think BeOS or QNX "debased the microkernel model".

      BeOS is dead. QNX is a niche even in it's native embedded land. 'nuff said.

    3. Re:If you "don't need them" by Anonymous Coward · · Score: 0

      QNX is not a consumer operating system.

      As for BeOS, it would appear I misstated my original comment to some extent then. Perhaps something better to say would have been either "every currently sold consumer operating system", or else "every single operating system sold to consumers I have ever seen that used microkernels either debased the microkernel or died in the end."

  138. MINIX "nice" command by maitas · · Score: 2, Informative


    In fact, back at university I implemented the "nice" command for MINIX 2.0. The hard part was to pass the message from userland to the scheduler (which previosly I had modified so it sorts the process qeue according to the priority).
    I haven't try anything similar for Linux, but having a monolitic architecture surely simplifies the message passing burden (which was a lot!), although it migth add other problems I haven't consider...

    For a start, the simplest OS seems to be a monolitic approach, single-task, single-user, like DOS... taking to the extreme the KISS approach we would go back to pure assembly language...

  139. Did Ken Brown write his book? by iabervon · · Score: 2, Funny

    So Ken Brown is claiming that, because Linus didn't write Linux in a vacuum, but was exposed to Andy Tanenbaum's work on the subject, he doesn't really own it. In order to come to this view of history, Ken Brown exposed himself to Andy Tanenbaum's work on the subject. So is Linus isn't the originator of Linux, Ken Brown isn't the originator of his book.

    1. Re:Did Ken Brown write his book? by FuzzyDaddy · · Score: 1
      Ah, but you're wrong - according to the article, Ken Brown was apparently completly ignorant of copyright, patents, and the history of Unix - so his work can be said to be completely his!

      --
      It's not wasting time, I'm educating myself.
  140. Re:How many programmers does it take to write an O by iggymanz · · Score: 1

    for that matter, how many people does he think wrote the core routines of Windows NT (David Cutler of DEC, who also wrote the core of VAX VMS)

  141. So the question is by Anonymous Coward · · Score: 0

    How can we get Mr. Tanenbaum's article out into the hands of people who read AdTI?

    So this article will probably weed out the few remaining slashdot readers who still took AdTI seriously. But it would make me very happy if AdTI could be exposed for what they really are in terms that the people who might otherwise fall for their claptrap would actually understand.

  142. Re:Right, thanks for pointing out the origin of a by raygundan · · Score: 1

    I dunno... getting 1 out of 2 when you get three tries to succeed once is good no matter what you're doing.

    Of course, I still think baseball is silly.

  143. Mirror by Door-opening+Fascist · · Score: 4, Informative
    Looks like the server is bogged down. Here's a couple mirrors:

    Mirror #1

    Mirror #2

  144. Baseball is popular in... by The+Conductor · · Score: 1

    ...Japan! You left out Japan!

  145. Re:Grain of salt please by Sajarak · · Score: 1

    Many if not most of the software we use is probably obsolete according to the latest design criteria. Most users could probably care less if the internals of the operating system they use is obsolete. They are rightly more interested in its performance and capabilities at the user level.

    I would generally agree that microkernels are probably the wave of the future. However, it is in my opinion easier to implement a monolithic kernel. It is also easier for it to turn into a mess in a hurry as it is modified.

    -- Ken Thompson, comp.os.minix, 4/2/1992

  146. Re:Grain of salt please by Anonymous Coward · · Score: 0

    Andy listed 6 independantly developed UNIX-like OSes, but he didn't even get them all, for example he missed Microware's OS/9, of which the original 6809 version was largely written by one person, Ken Kaplan. Undoubtedly there were others out there as well. It really isn't that hard to believe that one person can develop a UNIX-like OS kernel...

  147. Which challenge? by StrawberryFrog · · Score: 3, Informative

    but Linux rose to the challenge, Minix pretty much didn't.

    RTA. particularly the bit where Tanenbaum says that he kept MINIX small in order to to keep it up the challenge of being a good teaching tool. And then goes on to imply that he was suprised that it took so long for the niche of free, open production-featured UNIX to be filled by Linux and BSD.

    Of course, Tanenbaum would have prefered that niche to be filled by a microkernel OS, but MINIX was never going to be that OS. MINIX was going to be the code that the creators of free UNIX cut thier teeth on at university. And guess what, it was.

    --

    My Karma: ran over your Dogma
    StrawberryFrog

  148. Alexis de Tocqueville by Pac · · Score: 2, Informative

    It is a shame that such a bunch of liers, obviously finnanced by the Microsoft Marketing Department, is allowed to use Tocqueville's name. The man must be almost rising from his grave to do them justice.

    Anyway, a quote of his seems to apply:"In order to enjoy the inestimable benefits that the liberty of the press ensures, it is necessary to submit to the inevitable evils it creates..."

    All is pretty clear: the Alexis de Tocqueville Foundation is nothing more than a front-end to third-party interests, the Foundation agenda is clearly determined by the ammount of money payed by its clients and the Foundantion and its members are willing to say and do anything, no matter how dishonnest, to please their clients.

    It is now just a matter using every opportunity to show the evidence to the press so the harm they can do is minimized. Until Microsoft chooses another "Foundation" to fund...

    1. Re:Alexis de Tocqueville by Fnkmaster · · Score: 1

      Agreed - I said essentially the same the other day http://slashdot.org/comments.pl?sid=107859&cid=917 3066. It is a shame to see de Tocqueville's name used this way. Google him and read a bit about what the man actually wrote if you've never read him before. Agree or not with all of it, he surely would roll over in his grave to be associated with these scumballs.

  149. Re:I still love the classic conversations from 199 by byolinux · · Score: 1

    It's historical, I'd really like it changed.

    byolinux, as a website hasn't existed for ages.

    Anyway, I should be byognu, or gnuboy, surely? ;)

  150. Re:Grain of salt please by AKAImBatman · · Score: 1

    You forgot AtheOS.

  151. Re:Right, thanks for pointing out the origin of a by Quill_28 · · Score: 1

    Ok i know you don;t like baseball but you statement is not correct.

    Suceeding in baseball is getting a hit, getting hit, walking, or in sacrificing. Only getting a hit counts in your average.

    You don't get three chance to succeed, if the first pitch you hit a lazy pop-up you are done. Only if you swing and miss, hit a foul ball or take a strike(assuming less than two strikes) do you get another chance.

    Sorry to get technical.
    Baseball is a great game too bad the owners and players have ruined it. Or should i just say money.

  152. Thank you for the mirror. by Anonymous Coward · · Score: 0

    Can anyone here explain the cryptic "teenage girl from virginia" comment toward the end?

  153. plot thickens indeed by mardoen · · Score: 2, Informative

    Ha. A search for the author of this posting reveals a rather lengthy list of "OS Research Questions" in forums, newsgroups and alike. Implementation details, amount of work, authors and ownership, etc.

    But shouldn't come as a surprise, as his email address "[name]@adti.net" belongs to the Alexis de Tocqueville Institution mentioned in the article.

  154. But you're using a similar argument by Burz · · Score: 1

    Aren't you, like Andy, taking a purist position?

    I find the comments about Mac OSX elsewhere in this thread very enlightening. OSX has attributes of both a micro- and monolithic kernel. Clearly Apple is supplying common drivers in the kernel space that are performance-critical. Yet users can still easily install other drivers without having to, er..., recompile their kernel.

    You lose, Andy loses... Apple wins.

    (FYI my primary OS is Linux.)

  155. Re:Right, thanks for pointing out the origin of a by raygundan · · Score: 1

    I didn't say I didn't like it, I just said it's silly. Monty Python is also silly, but I get a kick out of them as well. The game is comically complicated while simultaneously maintaining that old-timey feel. It's like a sport satire, without trying to be.

    You're right, I oversimplified. You get three chances to succeed, except that there are ways to forfeit some of your chances, like having your ball caught, or if you turn around and beat the catcher to death with your bat.

  156. Re:I still love the classic conversations from 199 by slashblog · · Score: 0

    Minix Source code download

    http://minix1.hampshire.edu/mxdownld.html

    -Enjoy

    --


    ---
    Error 404: WMD Not Found
  157. It's me, Al Gore by Anonymous Coward · · Score: 0

    Damnit, don't you guys get it? *I* created Linux, not long after finishing my master creation of the internet!

  158. Great article but .... by Anonymous Coward · · Score: 0
    Tanenbaum's remarks are marvelous, particularly the bit about Ken Brown's much repeated, "We have multiple funding sources." Yeah, multiple as in Microsoft, Bill Gates, Paul Allen....

    But he slips off into his own "Alice in Wonderland" with this remark:

    And this was before the Patriot Act, which requires John Ashcroft's written permission before you can open your mouth.
    Even taken as sarcasm, that's as strange as anything Ken Brown is saying. Nobody in America needs "Ashcroft's written permission" to say anything. My neighborhood is filled with people engaging in bizarre rants about why Bush should be impeached. Yet at the same time they're convinced that they are in a police state. Living in Seattle has become like living next door to a John Bircher in the 1950s.

    Yes, the left is now as nutty as the right was half a century ago. Conspiracy theories abound. Strange books of the None Dare Call It Treason variety flood the market and there'll soon be a movie with the same theme.

    Every few weeks the press is seduced by media attacks as bizarre as any cooked up by the drunken Senator Joe Macarthy. Any day now, I expect to see Senator Ed Kennedy, his gait a bit unsteady, hold a press conference to announce, "I hold in my hands the names of 132 people, known to authorities as part of 'Big Oil,' who are members of the Department of Commerce."

    Reality, as in the fact that demand from China and gas-guzzling domestic SUVs are driving up the price of oil, is beyond such folk. For every problem, they must have an evil conspiracy.

    It's like living in a time warp. A exceptionally likeable and decent president from the American heartland (Ike/Bush--both born in Texas) is alternatively portrayed as the dumb tool of dark forces or as evil incarnate. Like those suffering from some forms of mental illness, these poor folk can't even sort out why they hate this Ike/Bush so much. Perhaps it's because he's reasonable and sensible, while they are not.

    And if history repeats itself, like the right in Goldwater/1964, the left is headed for a big crash.

    Mike Perry, Inkling blog , Seattle

    1. Re:Great article but .... by __aalomb7276 · · Score: 3, Interesting

      The comment on Ashcroft is out-of-place in an otherwise blunt article. That snipe and the cocky back-patting smack of elitism.

      I support the Patriot Act because it works. Furthermore, nobody has shown that it has been abused since it became law. Tanenbaum needs to be a little more levelheaded about American laws.

    2. Re:Great article but .... by FrankDrebin · · Score: 1

      AT also points out that he had just returned to the Netherlands from a trip to the US. Unless he is also a US citizen (or perhaps a citizen of some other excluded country like Canada), that means he was fingerprinted and photographed on arrival, thanks to Patriot Act.

      Mr. Ken Burns surely didn't have to go through that same silly little exercise at Schipol (Amsterdam airport). IMHO that alone earns AT the chance to be a little snippy at the US Administration.

      --
      Anybody want a peanut?
  159. Tanenbaum is right by Anonymous Coward · · Score: 1, Interesting

    In my opinion, Tanenbaum is right in his discussion about the micro vs. monolithic kernel issue. This doesn't mean Linux is a mess, but it could have been better. The information for doing so was available when Linux was developed by Linus. Don't get me wrong, I never wrote an entire operating system like Linux or Minix, but my point is that the knowledge was available and it was not used in the (initial) development of Linux. Perhaps Linus is really convinced that monolithic is preferred, but that is not enough to debunk the reasoning of Tanenbaum concerning microkernels.

  160. Ken Brown by Anonymous Coward · · Score: 2, Informative

    In case you have any questions about his book, Ken Brown can be found here or here. (Source.)

  161. Re:How many programmers does it take to write an O by jc42 · · Score: 2, Funny

    Answer: One more than it takes to change a light bulb.

    (Punchline: "That's a hardware problem.")

    --
    Those who do study history are doomed to stand helplessly by while everyone else repeats it.
  162. Tanenbaum ROCKS!!! by ToasterTester · · Score: 3, Insightful

    I think Andrew lays things out quite nicely in this article. So hopefully Brown will crawl back under the rock he came from.

    Also Tanenbaum made one of my favorite comments, something like this...

    The wonderful thing about standards, is there are so many to choose from.

    Tanenbaum is one the best minds in Computer Science.

  163. Einstein... by jotaeleemeese · · Score: 2, Insightful

    .... was a Jew. Just so you weigh again your previous comment....

    --
    IANAL but write like a drunk one.
  164. Who is Justin Orndorff ? by Anonymous Coward · · Score: 4, Informative

    What do we know about Justin Orndorff

    1. On April 12, 2004, he asked about Linux ownership on usenet linux.kernel, using IP address 66.44.2.45 (RCN dialup access range). He used raison__d_etre@hotmail.com as his originating email address.
    References :
    http://groups.google.com/groups?selm=1Kbes-3hM- 1%4 0gated-at.bofh.it&output=gplain

    2. On April 28, 2004, he asked about obtaining older versions of Minix in a Minix related mailing-list. He used raison__d_etre@HOTMAIL.COM as his originating email address.
    References :
    http://listserv.nodak.edu/scripts/wa.exe?A2=ind 040 4d&L=minix-l&F=&S=&P=59

    3. On May 6, 2004, he posted questions about O.S. development on usenet alt.os.development, using IP address 66.44.4.15 (again, RCN dialup access range). He used jorndorff@adti.net as his originating email address.
    References :
    http://groups.google.com/groups?selm=b6920e1.04 050 61039.75c2fc2c%40posting.google.com&output=gplain)

    4. Later on May 6, 2004, the very same questions were asked in various web forums by someone using the nickname "jnana".
    References :
    http://www.webmasterworld.com/forum40/1067.htm
    http://forums.devhardware.com/showthread.php?t=18 1 19&goto=nextoldest
    http://www.osdev.org/board.jsp ?message=6907

    5. On may 18th, 2004, he asked questions about corporate contribution into Linux on usenet linux.samba, using IP address 138.88.144.59 (Verizon DSL access range). He used raison__d_etre@hotmail.com as his originating email address.
    References :
    http://groups.google.com/groups?selm=1Xf0Z-7VF- 11% 40gated-at.bofh.it&output=gplain

    It is very likely that it is indeed only one person as :
    - The topics are closely related.
    - The IP used when posting using the @adti.net address (3) is on the same range as the one used when posting using the @hotmail.com address (1).
    - The questions asked using the jnana nickname (4) are the same as the ones asked using the @adti.net address (3).

    Obviously, we have someone here, going by the names of Justin Orndorff/Jnana/Raison__d_etre (French for "reason to exist, or reason to be), and who seems very interested in Linux and other FOSS intelectual properties issues.

    This person has at least two email addresses :
    raison__d_etre@hotmail.com
    jorndorff@adti.net

    What else ?

    6. He apparently has a page/blog on Devianart. He uses the same Justin O. and Jnana names. He says he's 22 and lives in CP (?), Maryland. He has apparently started a new job on March 1st.
    References :
    http://jnana.deviantart.com/
    http://jnana.devi antart.com/journal/

    7. He seems to like movies, particularly the "poetic" genre.
    References :
    http://www.amazon.com/exec/obidos/tg/cm/member- gui des/-/A17FKWGJYHSEL2/103-1166439-6115864

    8. He likes VHS music tapes trading (particularly black metal), has an email address @wam.umd.edu (University of Maryland) where he seems to be a student.
    References :
    http://www.tapetradernetwork.com/Framed_body_ri ght .asp?ArtistID=3338
    http://www.tapetradernetwork.c om/Framed_Trader_Det ail.asp?ID=9856

    9. A while back he was looking for "Codreanu comp. ['Fidelis Legio']" (whatever that is, apparently more black metal).
    References :
    http://grumblesmurf.net/pipermail/coldmeat-l/20 02- February/010935.html

    10. Well, he actually seems to be an English student at U. of Maryland (College Park, CP again, see (6)), and interested in films production.
    References :
    http://cinemaminima.com/blogs/orndorff/

    OK, so maybe this is going a little fast but we apparently have an :
    - English student in Maryland,
    - Interested in films
    - Using email addresses raison__d_etre@hotmail.com, jorndorff@adti.net and maybe morpheus@wam.umd.edu (fake ?)
    - Working since March or April for the ADTI (A. de Tocqueville Institute)

    1. Re:Who is Justin Orndorff ? by isn't+my+name · · Score: 1

      11. And he may well be jnana on slashdot.

      If you look at the posts on your item 4, jnana is the alias that Justin chose. As you have show (10), he is an English major, and looking at some of the posts, it looks like this guy is an English major, or at least someone with humanities training.

      And, as much as it is somewhat disturbing how much can be dug up regarding someone on the web, his slashdot sig has a link to a Students for Orwell site, so I imagine in a perverse sort of way that Jusin might approve of all of this. And least an English major, he should appreciate the irony.

  165. Justin the nazi lover. by Anonymous Coward · · Score: 0

    Justin Orndorff seems to be a nazi lover:

    Romanian fascism and anti-semitism

    Justin trading warez.

    Greetings to stats_for_all on the yahoo SCOX board for the excellent research:

    Justin picked his Yahoo handle, "Coldwindflame" from an CD produced by "Genocide Music" in a **"legendary release feature 2 of Americas Elite kults going head to head in an all out BLACK METAL assault."**

    The set list say it all:

    Knights Of The Holocaust
    Fallen Ones
    Slit Their Throats To The Spine
    Shadows Of The Fallen Kingdom
    Power Of Darkness
    Coldwindflame

    SEE: www.geocities.com/SunsetStrip/Loge/3625/genrelease s.html

    This is the person working at AdTI trying to FUD linux!

    1. Re:Justin the nazi lover. by Breakfast+Cereal · · Score: 1
      WTF? I didn't see anything about that on the links you posted, and his CD list is pretty huge and suggests he's into spooky music, much of which I haven't heard of but some of which I own and that much, at least, is definitely not Nazi music.

      I think we can expose Microsoft's minions without defaming them. I certainly don't want anyone being called a Nazi because he listens to Coil, Godspeed You! Black Emperor, Black Tape For A Blue Girl, Lisa Gerrard, or - for cryin' out loud - Bjork!

      If you have anything more specific then post it, otherwise STFU.

  166. He slams Linus almost as much as Brown... by FurryFeet · · Score: 1, Troll

    Think someone is still sore about Minix's destiny compared to Linux's?

    1. Re:He slams Linus almost as much as Brown... by _Sprocket_ · · Score: 2, Interesting


      Think someone is still sore about Minix's destiny compared to Linux's?


      Hardly - if you can believe what he says. For example:

      The reason for my frequent "no" was that everyone was trying to turn MINIX into a production-quality UNIX system and I didn't want it to get so complicated that it would become useless for my purpose, namely, teaching it to students. I also expected that the niche for a free production-quality UNIX system would be filled by either GNU or Berkeley UNIX shortly, so I wasn't really aiming at that.

      So why slam Linus? Because Linus did something he fundimentally disagrees with. The disagreement has been public and heated. Andy aludes to this today. But he also notes:

      Some of you may find it odd that I am defending Linus here. After all, he and I had a fairly public "debate" some years back. My primary concern here is getting trying to get the truth out and not blame everything on some teenage girl from the back hills of West Virginia. Also, Linus and I are not "enemies" or anything like that. I met him once and he seemed like a nice friendly, smart guy. My only regret is that he didn't develop Linux based on the microkernel technology of MINIX.

      So yes - he still feels the same way after all these years. He acknowledges this disagreement. And notes that it's nothing personal.

      Bitter of Linux's success? I don't see it.
    2. Re:He slams Linus almost as much as Brown... by FurryFeet · · Score: 2, Funny

      Well, it's just my opinion. However, allow me to pull out a cliché.
      "In 1965, Professor Challis A. Hall Jr. read the term paper Fred Smith had submitted for his Economics class. It described a delivery system using a hub topology. Hall graded it a C, because altough it was original, it would never work in the real world.
      A couple of years later, Smith founded Federal Express."

      All I'm saying is, considering where Linux is today, Tennenbaum's assertions that Linus "should have paid more attention in class" sounds to me like what Hall would say.

    3. Re:He slams Linus almost as much as Brown... by swordgeek · · Score: 1

      Interesting, but I'd say incorrect.

      Monolithic kernels have been around for at least a decade and change. The model has been turned into reality. The theory has turned into practice. Now that we have ages of real experience, the microkernel model still holds substantial advantages despite being _behind_ on the development curve vs. a monolithic kernel.

      I think Andy's quite right, but it's a dead issue, unfortunately.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  167. The problem here by Anonymous Coward · · Score: 0

    Is that what we have is a "superior architecture" from the developer standpoint but not the user standpoint. The user gets no advantage. The user doesn't care that the developer's lives are easier, from their perspective if a product is "better designed" but 20% slower it just means it's worse.

    DEVELOPER: We want you to take a 20% speed hit on our next OS release because our new OS has a superior architecture. The new computers coming out are 20% faster so this wont matter

    USER: What's superior about it?

    DEVELOPER: The kernel is much more better designed, there is a more coherent separation between different intrakernel address spaces and functionalities

    USER: I don't know what that means

    DEVELOPER: It's just.. you know.. better. And it is the same speed in the aggregate since youre buying the new hardware anyway so its worth it

    USER: Or I could just not give you any more money, and run your previous software on the new hardware, and get a 40% speed gain

    DEVELOPER: Uhhhhh...

  168. Re:How many programmers does it take to write an O by Angst+Badger · · Score: 1

    How many people does Brown thing wrote the original version of DOS? Microsoft wouldn't have gotten their big break were it not for Tim Paterson's SOLO coding effort.

    Criminy, just check the OS section on DMOZ or Yahoo. It's amazing how many teenagers have written fairly sophisticated operating systems on their own. It's not easy, but it's not like sending men to the moon, either. Shit, *I* wrote one once, in 6502 assembly language, on a 8-bit microcomputer when I was sixteen. Mind you, it wasn't anything like Linux, but then I didn't have thousands of talented developers helping me out.

    It's difficult to imagine any application that couldn't be written by a reasonably smart programmer given time and motivation. Arguably, it's having too many developers that will screw up a project.

    --
    Proud member of the Weirdo-American community.
  169. What? by Anonymous Coward · · Score: 0

    How come stupid wankers like this have jobs? Compassionate conservatives?

  170. Re:I still love the classic conversations from 199 by Anonymous Coward · · Score: 1, Interesting

    I think that clumsy line is the main reason I gave up watching B5.

    Well, if that's the reason you gave up on B5, you gave up mighty early - that line was only present in the opening of the first season. Every season of B5 has a different opening blurb, and that line was dropped (along with most of the rest of the Season 1 blurb) at the opening of Season 2.

  171. Ken Brown a.k.a Ken Brawn by FeebleX · · Score: 1

    From the Springdale Police Department:

    KENNETH PAUL BROWN WANTED FOR GRAND THEFT AUTO 3 COUNTS WARRANTS ON FILE KENNETH PAUL BROWN AKA :
    KEN BRAWN

    http://www.springdale.org/DEPART/police/pdweb/do cu ments/wanted.htm

  172. Mr.Brown should know that Bill Gates wrote Windows by while(1)fork() · · Score: 2, Funny

    Everybody knows that Bill Gates wrote Windows! Didn`t he?

    So why does Mr. Brown wonder that Linux wrote Linux?

  173. Re:Mr.Brown should know that Bill Gates wrote Wind by while(1)fork() · · Score: 1

    I meant: Linus wrote Linux ;-)

    I should have used the preview button...

  174. Viruses and Popularity by Anonymous Coward · · Score: 0

    This just demonstrates that smart people can still say remarkably stupid things. The attentions of virus writers have never had anything to do with popularity.

    Your post just demonstrates that random Slashdotters fall for the same fallacy as "smart people" -- namely, that you possess the knowledge to determine how everybody develops viruses. I mean, seriously. You don't think that even a small percentage of virus writers think "Hey, this virus will infect 80% of all Windows boxes out there"? Good to see you've personally interviewed each and every virus writer and determined their intentions.

    You may not consider popularity a crucial influence, but I assure you that it is. Linux is far more secure to begin with, as Tannenbaum suggests, and suffers less attacks because of inherent design choices. But it is by no means the sole factor keeping it from being attacked.

    1. Re:Viruses and Popularity by jedidiah · · Score: 1

      Get over yourself.

      Platforms far more scarce than Linux have been besieged by virii in the past at a time when individual users were far more isolated. This is a simple historical fact that both you and the professor are ignoring.

      Tannebaum's comment is an assinine absurdity that is flatly contradicted by the direct first hand experience of many of us who have computed on systems that make Linux look remarkably popular.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  175. Re:Grain of salt please by Bull999999 · · Score: 1

    From reading the article, shouldn't it be that monolithic kernels are faster (but less secure) than microkernels but microkernel can be tweaked to be as fast as monolithic kernels?

    --
    1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
  176. Teenage girl from WV by sharp-bang · · Score: 1

    Perhaps this is a comment on the Abu Ghraib prisoner abuse scandal.

    --
    #!
  177. "Teenage girl from West Virginia" by sharp-bang · · Score: 1

    Perhaps this is a reference to the Abu Ghraib prisoner abuse scandal.

    --
    #!
  178. Re:Tanenbaum ROCKS!!! by throughthewire · · Score: 1
    "The nice thing about standards is that you have so many to choose from."

    Andrew S. Tanenbaum, Computer Networks, 2nd ed, p.254

    One of my favorite quotes as well, and applicable to so many things.

  179. SORRY REDUNDANT by sharp-bang · · Score: 1

    Got an error on the first posting and thought it had bombed out.

    --
    #!
  180. Why it was brought up by Synn · · Score: 4, Insightful

    He brought it up because it proves the point that Linus wrote Linux. If he had copied MINIX Linux would've been a microkernel design instead of a macro one.

    The fact that Linus wrote Linux "wrong", proves he wrote it and didn't steal it.

  181. Tanenbaum keeps using this word... by PCM2 · · Score: 2, Interesting
    ...I do not think it means what he thinks it means.
    While this not free software in the sense of "free beer" it was free software in the sense of "free speech" since all the source code was available for only slightly more than the manufacturing cost.
    How does selling me low-priced goods give me the right of free speech?
    --
    Breakfast served all day!
  182. Re:I still love the classic conversations from 199 by iantri · · Score: 1
    It's a bit of padding, I think to make the line take up enough room to fade into the music -- with out it there would be too much space between when the line ends and the music begins.

    I never thought of that line as being a big deal (well, actually, I never though of it at all -- it's the "It can be a dangerous place" bit that bugged me). It gets A LOT better with Season 2.

  183. Does technology grant freedom? by Deskpoet · · Score: 1

    From everything I've read, I'd say Linus is anything but casual about freedom. What he is *not* is an idealist. That's what we have RMS for. He's a pragmatist, exactly the kind of person you want in charge of an engineering project. Perhaps not the person you want at the head of a movement, but that's not what he is. He's first and foremost an engineer.

    As much as I admire the strength of RMS's conviction, Linus' pragmatism makes more sense because technology--at least, in the context about which we are talking, that of electronics, computers, etc.--is conducive to freedom at all.

    When we talk about "freedom", we're generally refering to a limited spectrum of "entropy" within a social system. Computers and communications technology, by their very nature, increase information availability, the very antithesis of entropic progression. High-falutin' words to merely restate: if it can be turned off, freedom doesn't factor into it.

    --
    "The more corrupt the state, the more numerous the laws."--Tacitus, The Histories
  184. Re:I still love the classic conversations from 199 by elFarto+the+2nd · · Score: 1

    Well, I suggest (as someone who has recently watched the whole thing) you go watch it now. As it's a brilliant series, maybe not so good in the SFX department by todays standards, but an absolutly great story line.

    Regards
    elFarto
  185. Context Switches by RAMMS+EIN · · Score: 1

    Aw, so it is true. I've heard before that x86 context switches are costly, this just adds to the clues. I guess that's what you get with a design that was never meant to do multitasking.

    --
    Please correct me if I got my facts wrong.
    1. Re:Context Switches by EvilTwinSkippy · · Score: 1

      little Endian addressing, 8 registers to play with, backward compadibility to an 8 bit processor, Intel has always been known as the first with the worst.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
  186. Before some idiot mods you up by Anonymous Coward · · Score: 0
    I think it's insane that to you have to compile the Linux kernel just to get drivers, but that's just me ...
    This is yet another lie from someone who speaks as though they know what the hell they're talking about when they obviously don't. Not only is this not true (cough NVidia cough) but a blatant misrepresentation--but then again bonch is a master of misrepresentation.

    Why don't you get your facts straight before you go spouting off like you know what you're talking about?
  187. Can we get reuters to cover this story? by jonathan_95060 · · Score: 2, Insightful


    I saw the original AdT slander on yahoo via reuters (I think).

    Can ESR or some other evangelist work to get an abridged version of AST's response on a major news wire?

    While preaching to the slashdot and other choirs is fun, getting the story into the same channels that the AdT report was in would be more helpful.

  188. Right by ink · · Score: 1

    Apple should probably ask if you want to install the "BSD Userland" tools or something.

    --
    The wheel is turning, but the hamster is dead.
  189. Re:I still love the classic conversations from 199 by ocelotbob · · Score: 1
    I don't know. Linux made it to 1.0 in a couple years. Surely 10 years is long enough for a big project.

    Additionally, it's not GNU/Linux. One can use, for example, ulibc X and MWM to have a complete operating system with no more GNU software than the typical BSD. So unless you want to suggest that we start calling it GNU/BSD, stop insisting that Linux is really GNU/Linux.

    --

    Marxism is the opiate of dumbasses

  190. Exactly by Anonymous Coward · · Score: 0

    Robert Oppenheimer: My God, what have we done
    Porting the analogy to F/OSS is left as an exercise to the reader.

  191. Yeah, it's out there... by blorg · · Score: 1
  192. Is it possible for Linus to sue? by Anonymous Coward · · Score: 0
    Doesn't Linus hold a copyright on the original source code for Linux? Doesn't the AdTI book amount to disparagement of copyright?


    IANAL, but I'm wondering of Linus has on open and shut case for slander, if not libel per se.

  193. Linux turning into a microkernel by ebresie · · Score: 1

    I still don't understand the whole monolithic vs microkernel of linux-ness.

    As linux has become more developed, it seems in my eyes to becoming more and more microkernel like. It is becoming more modular (with architectures and kernel subsystems such as file systems, memory management, scheduling, etc). With the clustering functionality being developed is seems more message/microkernel like. The VM tries to isolate memory between processes/threads which seems more microkernel like.

    The case could be made that linux does share memory and not do the whole message passing, but couldn't the whole method of using sysctrl and related interfaces be another form of message passing with another name?

    Seems like a tOmato / tomAto type of argument.

    --

    Eric B
    ebresie@gmail.com
  194. Is Microsoft really behind this? by belmolis · · Score: 4, Insightful

    The nonsense coming out out of AdTI together with Andrew Tanenbaum's description of his interview make me wonder whether the speculation that Microsoft is behind this is really correct. Microsoft has tons of money and some fairly smart people, even in management. I find it hard to believe that they couldn't do a better job than this. Even if they need a putatively independent institution as a front, they could write the material themselves. They could even have their chosen institution hire somebody halfway competant for the project. It's hard to believe that they couldn't do better than this.

    I wonder if this is perhaps just somebody trying to make a name for himself and/or bring in money for himself or his institute rather than something directly arranged by Microsoft.

  195. We have the picokernel already... by sczimme · · Score: 4, Funny


    It's what makes pine work.

    /ducks, runs away

    --
    I want to drag this out as long as possible. Bring me my protractor.
    1. Re:We have the picokernel already... by jack_csk · · Score: 1

      Sooner or later, pine will be bootable just like emacs

  196. Re:Even Ziff Davis is saying AdTI's stance is a cr by Anonymous Coward · · Score: 0

    You gotta love the "get the facts" ad in that article, asking "Can Linux deliver lower TCO?". If slander doesn't work, try TCO "studies". If those don't work, try slander again.

  197. Re:How many programmers does it take to write an O by zenyu · · Score: 1

    Criminy, just check the OS section on DMOZ or Yahoo. It's amazing how many teenagers have written fairly sophisticated operating systems on their own. It's not easy, but it's not like sending men to the moon, either. Shit, *I* wrote one once, in 6502 assembly language, on a 8-bit microcomputer when I was sixteen. Mind you, it wasn't anything like Linux, but then I didn't have thousands of talented developers helping me out.

    Yeah, I wrote an OS too in high school, before I had any programming classes under my belt (Just the Turbo Pascal Manuals and a couple issues of Dr. Dobbs my mom had seen in a trash can at work and brought home for me). I probably would have used Minix if I had known it existed, but I hadn't yet heard about the internet thing that my university might have from my Physics teacher. I spent more time figuring out where to place my bootloader on the floppy than I spent on multitasking (which started my long and eventually foolish habit of writing my own mutexes). I initially used the BIOS to interface with all the hardware, even the terminal. I could load .com's the first day. It really isn't hard to write a basic OS, everyone should do it just to demystify computers a bit.

    It's whether it snowballs into a something more featured that everyone wants to use that is the key. The genius of the GPL is that it allows others to contribute to your pet project without worrying that you might steal their work. They don't need to trust you much, they just need to trust the legal system a tiny bit. This lets the snowball get going. Once it's big enough, a BSD license might even be sufficient, but the GPL really excels in getting that initial momentum.

  198. Windows and Linux are both monolithic kernels by Animats · · Score: 1
    Windows and Linux are both monolithic kernels. Both have drivers, networking, and file systems inside the kernel. Windows NT 4.0 and later even have much of the GUI inside the kernel. (NT 3.51 and earlier did not. The reason that stuff moved inside the kernel had to do with replicating the exact, if broken, behavior of Windows 95 in NT 4.)

    Microkernels are hard to do, but QNX demonstrates that you can do everything you need to do with a very small microkernel.

    1. Re:Windows and Linux are both monolithic kernels by drinkypoo · · Score: 1

      It had nothing to do with replicating the exact behavior - the two operating systems came out looking the same but behaving pretty differently in most cases, just not where the GUI was concerned. It had everything to do with performance, which just wasn't there. Of course, if accelerated video devices had been more readily available at the time, we might have ended up with an OS which used graphics acceleration to get around the problem instead. There certainly were (2d) accelerated graphics cards for PCs at the time, like Orchid's Fahrenheit cards, but the vast majority of VGA cards were basically dumb framebuffers. They had video BIOS for handling graphics from DOS programs, but their windows drivers had to do all the work for them. The video BIOS is executed on the processor in any case.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Windows and Linux are both monolithic kernels by bored · · Score: 1

      Here we go again, techically NT isn't really either a microkernel, or a monolithic kernel. This is primarly due to the fact that windows has a microkernel arch but all the speed critical systems are running at the same protection level as the core kernel. Meaning, that message passing is happening between the diffrent kernel subsystems like a microkernel, but there arn't any scheduler evenets occouring, which means you get most of the advantages of both microkernels and monolithic kernels with the monolithic problem of single subsystem failure taking down the whole machine.

    3. Re:Windows and Linux are both monolithic kernels by drsmithy · · Score: 1
      There certainly were (2d) accelerated graphics cards for PCs at the time, like Orchid's Fahrenheit cards, but the vast majority of VGA cards were basically dumb framebuffers.

      Eh ? Video cards with 2D acceleration were commonplace from the early 90s (some better than others, obviously). NT4 didn't come out until late '96.

  199. From CNet Review by gordguide · · Score: 2, Informative

    " Microsoft indeed has provided funding to the Alexis de Tocqueville Institution for five years, a Microsoft representative said, without disclosing how much has been granted. Microsoft funds several public policy institutes, including the American Enterprise Institute, the Center for Strategic and International Studies, the Heritage Foundation, and the Cato Institute, the representative said. "

    CNet

  200. The plot thickens further by overunderunderdone · · Score: 1
    A quick google search also brought up this
    http://lkml.org/lkml/2004/4/12/72
    Hello, my name is Justin and I'm doing some research into the specifics of Linux. Out of curiosity, who owns the Linux kernel?

    Is it owned by Linus Torvalds, its contributors or the public?

    Thanks for your time. Best, Justin Orndorff
    Along with similar posts in other forums
  201. Re:I still love the classic conversations from 199 by Brandybuck · · Score: 1

    that line alway bugged the heck out of me

    That line has meter! It has rhythm! It has strength and character!

    --
    Don't blame me, I didn't vote for either of them!
  202. Brilliant stuff. by aug24 · · Score: 1

    Nice work 'Anonymous Coward'!

    Thanks for the help... if you find anything else, and want to continue this rather interesting game, please mail me at justin at aug24 dot co dot uk.

    We'll show these dodgy buggers that the human community is stronger than any greed bastards' company!

    Justin.

    --
    You're only jealous cos the little penguins are talking to me.
  203. Crazy question - micro vs macro by crucini · · Score: 2, Interesting

    Could you write a "microkernel" that becomes a macrokernel if compiled with certain parameters? Message passing would be done via a macro which can become simply a function call.

    Then kernel developers can run the "micro" version and have the freedom to easily hack parts while the system is running. But production machines could run the "macro" version.

    1. Re:Crazy question - micro vs macro by cakoose · · Score: 1

      I think Mac OS X is structured like a microkernel but everything's compiled and statically linked together for speed. With this setup, you can have your clean design but you still get rid of the context switches. That said, the design itself will impose some overhead (though the tradeoff may be worth it).

      Another solution is to use a safe language to eliminate the need for address space separation and let the kernel JIT code when it's loaded. Compilation techniques for safe languages are getting better and better so performance is becoming less of an issue. One example is Brix, which runs everything in kernel space (even applications).

      However, I don't know how you would deal with a misbehaving process in a shared address space (i.e. how would you write an OOM killer?). The Spin OS has a way of detecting badly-behaving code, but I think that dynamically-loadable code is restricted in what kind of functions it's allowed to perform.

  204. All I want to know is... by commodoresloat · · Score: 1

    if Linus didn't write Linux, can we go back to pronouncing it with the long "i" (lie-nucks)? It sounded so much cooler that way.

  205. Think of Minix as a big success by geoswan · · Score: 1
    I think we should go farther than that. Minix was a big success. Even if he had never written his book and the only people who used it were his students I think we could fairly classify it as a success. But it was used by a great many more people than that. So it was a big success.

    In terms of users, of course, Linux too was a big success. I think that it is only in comparison to Linux that Minix doesn't look like a success. But it is a success, a big success.

  206. Bah that makes him human by SmallFurryCreature · · Score: 3, Insightful
    I wouldn't even call it sour grapes or hubris. He believes in the micro-kernel and Linus didn't use one. So to him Linus is a smart kid who should have paid better attention in class. He talks like a professor. Well that is what he is. His comment on students says it all :)

    It is not unlike the whole GNU/linux argument that Stallman keeps bringing up. Stallman fundamentaly believes in the GNU and what it stands for.

    Linus isn't to concerned about ideals. That is his secret. He is rather pragmatic and makes the choice that works right now. It is why it is the cute little penguin and not some super slick logo or the BSD devil that is the symbol for everything MS is not. Minix, BSD, hurd. All are free and true to some higher ideal about software. But linux rules them all in actually being used.

    Tanenbaum and Stallman are the shoulders Linux stands on (with a lot of others of course) but at the same time it is also betraying them a little. That tanenbaum and Stallman can't help but point this out makes them real human people. Not some politically correct mouthpiece. I like them all the more for it.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Bah that makes him human by drinkypoo · · Score: 1

      Betraying them? What Linus learned from using Minix is that its design got in the way of implementing features he wanted. If he wasn't dissatisfied with Minix, would he have ever created Linux? There's no way to tell, I guess...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Bah that makes him human by SmallFurryCreature · · Score: 1
      But GNU and minix have ideals wich Linux does not follow. Linux isn't about ideas but about practicality. It explains why it is working when so many other free opensource OS'es are available. Exactly why is BSD dying? Why doesn't anybody use minix? Why does everyone use the term Linux and not the proper GNU/Linux or Linux/GNU?

      Because Linus got the balance right. But in a sense this betrays the ideals behind GNU and Minix. GNU for everything to be truly open and free (linus uses the non-free bitkeeper) and for Minix to make a secure stable simple to understand OS. (linux is stabler then window and can be understood but it is minix and wich each new kernel version more and more people are saying the kernel is growing to large)

      I am not talking major betrayal here as in stabbing people in the back. Just little minor every day betrayal that people can be upset about for decades after.

      --

      MMO Quests are like orgasms:

      You may solo them, I prefer them in a group.

    3. Re:Bah that makes him human by drinkypoo · · Score: 1
      First: We are talking about the linux kernel here. It is not properly called GNU/Linux, Linux/GNU, GNUix, or anything else. If you want to apply GNU to the name of a kernel, apply it to the HURD. Even when it comes to distributions, Debian is GNU/Linux, everything else is whatever people want to call it. Just because someone says it should have a GNU on it doesn't make it so. Linus himself has a marked tendency to not refer to it as GNU/Linux.

      Being about practicality is what computing is about. Computers help us do stupid things faster and thus make the impossible possible. Operating systems help us use computers. However, Linux is GPL'd, so I can not possibly imagine what you are bitching about in terms of Linux's practicality being a betrayal of the ideas behind GNU and Minix. First, forget about Minix. Linux was inspired by Minix, and the inspiration was "This OS doesn't do shit!" That is the beginning and end of the relationship 'twixt the two besides that Linux was apparently originally hosted on Minix.

      It's not any kind of betrayal. Linux is good and it works. I don't know why the HURD has received so little attention, surely if it had received as much attention as Linux has, it would be great today I am sure. Well, assuming it had someone as even-tempered and rational as Linux Torvalds at the helm, which you may have noticed it doesn't.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  207. I created Linus by Temporal · · Score: 1

    I built him from a kit as part of a science project in fifth grade.

  208. Re:I still love the classic conversations from 199 by EddWo · · Score: 1

    I first read about it from the Google Groups Timeline I was reading "Modern Operating Systems" at university and I thought it funny that the guy who wrote a hugely popular operating system was having a massive row with the guy who wrote the book on operating system design.

    It made me want to find out more about the differences between NT and Linux so I could more objectively compare them.

    --
    "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
  209. Re:I still love the classic conversations from 199 by lahi · · Score: 1

    There is a tremendous difference between:
    the thing itself,
    what the thing is called,
    the name of the thing,
    and what the name is called.

    Didn't you know? It's just like pointers in C or (better) refs in Algol68.

    -Lasse

  210. Security and microkernels by juhaz · · Score: 1

    Heh. Tanenbaum is bashing macrokernels because Windows is insecure.

    Kind of ironic considering the fact that Windows NT is actually more of a microkernel design.

  211. Two kinds of people I can't stand by Anonymous Coward · · Score: 0

    People who are intolerant of other people's cultures....
    and the Dutch.

  212. Re:I still love the classic conversations from 199 by drinkypoo · · Score: 1
    Giving up in the first season makes sense, though. If you weren't enough of a sci-fi fan to stick it out through the "acting" in the first season, I don't blame you. Admittedly part of it is us becoming comfortable with the characters, but much more of it was the actors doing the same thing. IMO the only people who didn't improve dramatically after the first season are Andreas Katsulas and Jerry Doyle, with a possible tip of the hat to Peter Jurasik who got much better about a third to half of the way through the first season. Even when I go back now and watch B5 again (which is still fun) I am struck by just how foul much of the acting in the first season is.

    If you made it through the first season, you generally got hooked in the second if you weren't already. I was hooked in spite of the bad acting because prior to that I had been a star trek (TNG - I loved TOS too but let's put it aside for now) fan and if you really examine it with a critical eye, the acting in that show might have started out slightly better (by a RCH or so) but it really took some time before those characters felt natural to me. Eventually I stopped watching TNG religiously even though the rest of my household at the time always watched it, but I stuck with B5 for quite a while until sometime around season 4 at which point for some reason it became difficult for me to watch for some reason, time slot or something.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  213. Re:I still love the classic conversations from 199 by mirabilos · · Score: 1

    About your sig: it better describes the LGPL.
    To describe the viral narute of the GNU GPL,
    a sig's space would not suffice.

    --
    My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
  214. Re:I still love the classic conversations from 199 by FuzzyBad-Mofo · · Score: 1

    Granted, it took a little while for the actors to settle into their roles, but by "The Parliment of Dreams", things were moving along quite well. One of my favorite things about B5 were the well developed characters.. Londo, G'Kar, Vir, Ivanova, Garibaldi, Sheridan.. it would not have been the same without them. The science fiction was the backdrop to the story, not the story itself. As it should be.

  215. Mod parent insightful by daniel23 · · Score: 1


    at least that's what I'd do if I had any mod points left

    --
    605413? Yes, it's a prime.
  216. mini bio:Alexis de Tocqueville by cwg_at_opc · · Score: 1
    i'm embarrased to say i'd never heard of him despite having two years of Political Science in College;
    after Googling many uninformative links(read:i'm lazy and i wanted a synopsis ;-), I found this link
    which says:

    Alexis de Tocqueville

    Tocqueville, Alexis Charles Henri Maurice Cl érel de (1805-59), French political writer and statesman, whose work on the United States political system became a classic.

    Tocqueville was born July 29, 1805, in Verneuil, and studied law in Paris. With the French publicist Gustave Auguste de Beaumont de la Bonninière, he went abroad in 1831 to study the penal system in the U.S. The two men reported their findings in Du syst ème p énitentiaire aux États-Unis et son application en France (The Penitentiary System in the United States and Its Application in France, 1832). After returning to France in 1832, Tocqueville wrote his most famous work, Democracy in America (2 vol., 1835-40; trans., 4 vol., 1835-40). One of the earliest and most profound studies of American life, it concerns the legislative and administrative systems in the U.S. and the influence of social and political institutions on the habits and manners of the people. Tocqueville maintains in this work that the full development of democracy occurred in the U.S. because conditions there best permitted the diffusion of European social ideas. He was highly critical of certain aspects of American democracy. For example, he believed that public opinion tended toward tyranny and that majority rule could be as oppressive as the rule of a despot.

    As a member of the French Chamber of Deputies (1839-48), Tocqueville advocated a number of reforms, including the decentralization of government and an independent judiciary. He became vice president of the National Assembly in 1849 and for part of that year was minister of foreign affairs. After opposing the 1851 coup d'état of Louis Napoleon Bonaparte, later French emperor as Napoleon III, Tocqueville retired from political life. He died on April 16, 1859, in Cannes.

    Tocqueville's major works offer a penetrating analysis of the principal political and social ideas of his period. His main emphasis was the evolutionary developments underlying all changes in society. His second most important work, The Old Regime and the Revolution (1856; trans. 1856), which he left unfinished at his death, interprets the French Revolution as having been the result of gradual changes in the structure of government and in political attitudes toward equality and freedom. Among his other writings is Recollections (1893; trans. 1896). An English translation of his notebooks for the period 1833-35 was published as Journeys to England and Ireland (1970).



    There are other more in-depth biographies, but this was the most succinct. Spinning in his grave may be an understatment given the philosophy of this "institute" - He is probably closer to the spin-rate of a millisecond pulsar
    --
    "...that's as white as it gets; all the bits are on..."
  217. You deserve +INSIGHTFUL by Anonymous Coward · · Score: 0

    or at least +INFORMATIVE

  218. See Also: Burgess, Richard A. "Developing Your Own by Specter · · Score: 1

    Developing Your Own 32-Bit Operating System
    Richard A. Burgess
    (c) 1995
    SAMS Publishing
    ISBN: 0-672-30655-7
    LoC: 94-69271

    "Have you ever wanted to write your own operating system?

    Or have you ever wanted to find out what it would take?

    Or have you just wanted to see the source code with _real_ comments?

    If so, then this book is for you! This book contains the ideas, suggestions,
    and tools you will need -- plus a sample operating system, MMURTL.

    You will see these features of MMURTL highlighted:

    Micro-kernel
    Message based
    Real-time
    Multitasking
    Multithreaded
    Cli ent/server oriented
    ISA 32-bit PC-compatible

    The CD-ROM contains:

    Complete MMURTL operating system source code
    Sample applications, including source code
    A 32-bit assembler, including source code
    A 32-bit C compiler, including source code"

  219. Bill Joy claimed he can write BSD in 1 summer by kerb · · Score: 1

    even bill joy in one of his interviews claimed that he can rewrite a BSD OS clone in just one summer.

  220. Interesting misunderstanding by tcoady · · Score: 1
    Linux has been the victim of fewer attacks than Windows because (1) it actually is more secure, but also (2) most attackers think hitting Windows offers a bigger bang for the buck so Windows simply gets attacked more.
    I guess that's why Apache is routinely attacked and compromised while IIS is ignored as its share leaves so little bangs for bucks.
    1. Re:Interesting misunderstanding by Anonymous Coward · · Score: 0

      I guess that's why Apache is routinely attacked and compromised while IIS is ignored as its share leaves so little bangs for bucks.

      Nah, it's just that IIS is usually disabled by a worm already. You're right about Apache, though. Every time I surf to an Apache-hosted site, the signs of destruction are everywhere. How the net holds together at all is just beyond my understanding. Thank God IIS is there to save us!

  221. Heh by warrax_666 · · Score: 1
    only on the x86 is swapping tasks expensive,

    Translation: It's only expensive on 90% of all deployed systems. (Yes, yes, I made the statistic up, but it's just to make a point).
    --
    HAND.
  222. Re: Nanokernels by some+guy+I+know · · Score: 1
    A nanokernel is a (kernel * 10^-9).
    Actually, no.
    The micro/nano/etc. prefix does not determine the size of the kernel, but instead denotes how finely the kernel is chopped up.

    A microkernel puts each subsystem in its own process/address space.
    A nanokernel puts each function in its own process/address space.
    A picokernel puts each line of source code in its own process/address space.
    A femtokernel puts each machine language instruction in its own process/address space.
    An attokernel puts each transistor in its own process/address space.
    Beyond that, the benefits of increased modularity start to be outweighed by increasingly decreasing performance.

    And kilokernels, megakernels, gigakernels, etc., are a whole 'nother story.
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  223. The best part by hummassa · · Score: 1

    No, it's definitively "As I sooned learned, Brown is not the sharpest knife in the drawer, ..."
    I ROTFLOLed in the office when I got to that point.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  224. Follow-up to yesterday's discussion by andy-at-vu · · Score: 5, Informative

    After seeing all the responses yesterday, I think I have a better idea of Ken Brown's motivation in coming to see me and also his motivation in writing the book. If you are curious, take a look at

    www.cs.vu.nl/~ast/brown/followup

    Andy Tanenbaum

    1. Re:Follow-up to yesterday's discussion by isn't+my+name · · Score: 1

      Actually, from your first response, it seemed pretty clear that you had a reasonable suspicion of his motivation at the time of the interview.

  225. Generous but still arrogant as always by grimharvest · · Score: 1

    "The proof of this is that he messed the design up."

    Notice he never says, "I simply disagree with Linus". With Tannenbaum, it's never a matter of opinion... he's just right, and everybody else is wrong. Minix is apparently a work of genius, everything else is mediocre at best in his world.

  226. Don't second-guess, win friends over instead by IceAgeComing · · Score: 1


    Second-guessing who's behind it is a waste of valuable time. Unless you believe in fairy tales, it will almost surely never be known who exactly is financing the effort. We can infer that whoever it is, they have a desire to influence public opinion. That is, after all, why people write books.

    A better use of time is to think what your Windows-running friends might like: burn copies of OpenOffice for Windows or Freeduc or KnoppiXMAME, all of which will run or boot from Windows machines.

    Help someone new fall in love with free software...today!

  227. Re:How many programmers does it take to write an O by drsmithy · · Score: 1
    for that matter, how many people does he think wrote the core routines of Windows NT (David Cutler of DEC, who also wrote the core of VAX VMS)

    Uh, at the time NT was being developed it was David Cutler of *Microsoft*.

  228. Re:How many programmers does it take to write an O by iggymanz · · Score: 1

    yep, that's where he went after DEC job. Too bad his cool stuff was surrounded by crap & cruft...

  229. On the Alexis de Tocqueville Institution by dh003i · · Score: 1
    Firstly, I have to commend Tannenbaum for being a real stand-up guy, and defending Linus Torvalds against unwarranted charges of "stealing code", despite all of the disagreements between AZT and Linus about what makes for better kernel design.

    The Alexis de Tocqueville Institution is a half-assed supporter of economic freedom and liberty, and unfortunately negatively reflects on free-market ideas. In fact, they don't really support freedom at all. They are enemies of freedom, like Milton Friedman was critical in the development of the witholding tax. Far from being a libertarian, free-market supporter, and laissez faire supporter -- like his son, David Friedman, or Murray Rothbard -- Milton Friedman is a technician of the State, who works to make it more efficient in its task of robbing from and stealing from its victims (the tax-payers). The de Tocqueville Institution is a State-supporting Institution, supporting State grants of monopoly priviledge (patents/copyrights).

    Unfortunately, there is this general opinion out there that the institution is a champion of capitalism. The de Toqueville institution is a champion of Statist Intervention.

    For a real libertarian analysis of intellectual property "rights", see:

    Against Intellectual Property. Stephan Kinsella.. Journal of Libertarian Studies, vol 15(2).

    Finally, lest you think that free-market advocates are anti-GNU/Linux, see:

  230. Re:Grain of salt please by Anonymous Coward · · Score: 0

    Tanenbaum said Linux must be an original work because Linus did it wrong and did not follow Minix's example.

  231. I'd say so by crayz · · Score: 1

    From ZDNet, here's who Microsoft funds:

    Microsoft indeed has provided funding to the Alexis de Tocqueville Institution for five years, a Microsoft representative said, without disclosing how much has been granted. Microsoft funds several public policy institutes, including the American Enterprise Institute, the Center for Strategic and International Studies, the Heritage Foundation, and the Cato Institute, the representative said.

  232. However... by crayz · · Score: 1

    as I posted elsewhere in this thread, here's who Microsoft funds, according to ZDNet:

    Microsoft indeed has provided funding to the Alexis de Tocqueville Institution for five years, a Microsoft representative said, without disclosing how much has been granted. Microsoft funds several public policy institutes, including the American Enterprise Institute, the Center for Strategic and International Studies, the Heritage Foundation, and the Cato Institute, the representative said.

    Notice any patterns?

    1. Re:However... by praksys · · Score: 1

      Notice any patterns?

      Not really. Two are conservative. One is run by Democrats, and one is is libertarian. And the source doesn't say what other think tanks they fund.

  233. Byte, September 1989, page 95 by Jeremy+Erwin · · Score: 1

    so says a old alt.folklore.computers post. Apparently, it could be had for a mere $18,000. I'd imagine that the prices had declined somewhat by late 1991, though.