Slashdot Mirror


A Historical Look At The First Linux Kernel

LinuxFan writes "KernelTrap has a fascinating article about the first Linux kernel, version 0.01, complete with source code and photos of Linus Torvalds as a young man attending the University of Helsinki. Torvalds originally planned to call the kernel "Freax," and in his first announcement noted, "I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones." He also stressed that the kernel was very much tied to the i386 processor, "simply, I'd say that porting is impossible." Humble beginnings."

46 of 173 comments (clear)

  1. No sooner had I finished compiling... by kaleco · · Score: 5, Funny

    ...than Gentoo using kernel 0.02 was made available.

    --
    Prosperity is only an instrument to be used, not a deity to be worshipped. Calvin Coolidge
  2. Official kernel development strategy by Anonymous Coward · · Score: 5, Funny

    "When the first kernel pops, then toss in about 1/2 cup of open source developers and shake vigorously until the popping dies down. You don't want to leave it on until you hear nothing, because then it's sure to be burnt."

  3. Too bad by Anonymous Coward · · Score: 5, Funny

    that that Torvalds guys project never amounted to anything useful.

  4. That's it! by Constantine+XVI · · Score: 4, Interesting
    Instead of trying to convince Linus to go to GPL v3, we can just convince him to go back to the original liscence! :)

    This kernel is (C) 1991 Linus Torvalds, but all or part of it may be redistributed provided you do the following: - Full source must be available (and free), if not with the distribution then at least on asking for it. - Copyright notices must be intact. (In fact, if you distribute only parts of it you may have to add copyrights, as there aren't (C)'s in all files.) Small partial excerpts may be copied without bothering with copyrights. - You may not distibute this for a fee, not even "handling" costs. Mail me at [email blocked] if you have any questions. Sadly, a kernel by itself gets you nowhere. To get a working system you need a shell, compilers, a library etc. These are separate parts and may be under a stricter (or even looser) copyright. Most of the tools used with linux are GNU software and are under the GNU copyleft. These tools aren't in the distribution - ask me (or GNU) for more info.
    --
    "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
    1. Re:That's it! by tepples · · Score: 3, Insightful

      You may not distibute this for a fee, not even "handling" costs. There's your show-stopper.
    2. Re:That's it! by MindStalker · · Score: 2, Insightful

      Back in those days people were selling buckets of free software at high "fee" cost. Linus apparently didn't like this.

  5. Linus even wrote a book about it by bomanbot · · Score: 5, Informative

    To get an even deeper look into the beginnings of the Linux Kernel, I like the book that Linus wrote which is called Just for Fun - The story of an accidental revolutionary (ISBN 1-58799-080-6, google the rest).

    It contains the entire back history how Linux began as a side project and of course the famous spat with Andrew Tanenbaum over Minix and Linux and I found it to be a good (if very nerdy) read.

    But the pictures in the article? Just sad, he reminds me so much of myself ;-)

  6. you insensitive clod by someone1234 · · Score: 3, Interesting

    I didn't know about this (that the first kernel was completely i386 specific) and consider the article interesting.

    --
    Patents Drive Free Software as Hurricanes Drive Construction Industry
  7. It's Also a Great Story by eldavojohn · · Score: 4, Interesting

    Anyone who cares already knows. Anyone who wants to find out, can find out. Well, that's not true, as it turns out, I care but I'm not afraid to admit I didn't know any of these things that Linus felt (having joined the game late, nor have I seen the documentation for the first release). And I don't go around looking at the history of software I use, I simply use the software. I use gcc but I'm not so sure its history would be that interesting to me.

    Come on, this is like doing a history of the First World War again, complete with photos of the Arch-Duke. I don't think that's a very good analogy. This wasn't really a history of the Linux kernel, more so a short intro to the attitude of the single point in the beginning. In my opinion, reading through this and scanning the attached documents would be more like if you had given me the first three pages of the Bible. "In the beginning, there was this guy that wasn't very sure anything would come of a project ..." This is a good article because I kind of always thought that Torvalds started Linux knowing it was going to be big. I imagined him sitting down one day and saying, "F this noise, I'm going to write an operating system that works ... and I'll distribute it for free!" ... except in Swedish?

    But that's not what happened and I think that's important for people to recognize. This was not unlike Frodo starting off on a quest thinking he wasn't going to get anywhere (though the motivation and implications are not so huge). It's the classic hero-by-accident story and since it's a true story, I love it all the more.

    You know, I always thought about writing to Paul Harvey (if he's still alive) and asking him to do a "And that's the rest of the story" on Linus. That would be some classic stuff. Although most the listeners, probably not even sure what Linux is let alone know its creator Linus, would probably think he's suffering from some form of dementia set on by age ...

    And it isn't something the is deserving of a place on this website! Are you kidding me? This actually makes me want to start some open source project even though I recognize it will probably go nowhere. Of course this belongs on this site.
    --
    My work here is dung.
  8. Oh No! by MyLongNickName · · Score: 5, Funny

    He looks just like Bill Gates at that age!

    --
    See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    1. Re:Oh No! by dn15 · · Score: 2, Funny

      Or like Stephen Hawking, looking at that one drunk photo ^^
      I was actually going to say the same thing but decided it was in poor taste.... Insensitive bastard.
  9. At least two people agree on 640kB by Centurix · · Score: 5, Funny
    From memory.c

    * NOTE 2!! When from==0 we are copying kernel space for the first
      * fork(). Then we DONT want to copy a full page-directory entry, as
      * that would lead to some serious memory waste - we just copy the
      * first 160 pages - 640kB. Even that is more than we need, but it
      * doesn't take any more memory - we don't copy-on-write in the low
      * 1 Mb-range, so the pages can be shared with the kernel. Thus the
      * special case for nr=xxxx.
    --
    Task Mangler
  10. uh huh by thatskinnyguy · · Score: 5, Interesting

    I have a poster in my office with all the lines of code for kernel 0.0.1. It's uber-geek. A must have for most slashdotters!

    --
    The game.
  11. Re:"Humble beginnings" by ttnb · · Score: 2, Insightful
    Anyone who cares already knows. Anyone who wants to find out, can find out.

    I'm not interested in learning the history of everything -- I'm just interested in learning the history of events that can teach me significant lessons, e.g. by inspiring me (starting humble can work out really well if there is significant demand and an empowering license like the GPL is used) or by warning of dangers.

    Therefore, articles like this are important to me. I wouldn't know to look for this particular bit of history if it weren't for people pointing out that this is a worthwhile bit of history to read up on.

    (In this particular instance, I knew already, but only because I came across an article on the same topic some time ago. Nevertheless I'm appreciating the reminder.)

  12. Re:"Humble beginnings" by mce · · Score: 2, Interesting

    Well, I was there back then (read my sig) and yet even so I enjoyed the trip down Linux memory lane while going through this article. Sure, this is not top-quality journalism, but if you don't want to read it, then don't.

    Slashdot is not anymore what to used to be when I joined (look at my /. id to see what I mean), but even so I still use it as my home page on my home boxen. If there's stuff that I don't want to read, I simply don't.

    PS: I happen to be interested in military history as well. So yes, I do still read stuff about WWI, archduke included, even after so many years. In fact, your mentionaing of it just caused me to read what Wikipedia says about Franz Ferdinand.

  13. Re:"Humble beginnings" by Corporate+Troll · · Score: 2, Informative

    Besides, for those too lazy to read up the history of Open Source and Linux, just watch Revolution OS. Features Richard Stallman, Linus Torvalds, Bruce Perens, Eric Raymond and many more.

  14. Note the mention of GNU by DrXym · · Score: 4, Insightful

    Yup, GNU Mach was well into development BEFORE Linux was even written. This is an example why open source projects are more effective when they're driven by pragmatism and not politics.

    1. Re:Note the mention of GNU by DrXym · · Score: 2, Informative

      Correction GNU Hurd.

    2. Re:Note the mention of GNU by sayfawa · · Score: 5, Insightful

      Maybe if the GNU folks had only been working on a kernel instead of also doing the hundreds of other programs as well, they would have made more headway with HURD. And if Linus had been trying to do a whole OS and not just the kernel, Linux the kernel would still be early in development.

      The mention of GNU should merely point out how important the GNU is in GNU/Linux. As Linus said in the post: Sadly, a kernel by itself gets you nowhere. To get a working system you need a shell, compilers, a library etc. These are separate parts and may be under a stricter (or even looser) copyright. Most of the tools used with linux are GNU software and are under the GNU copyleft.

      --
      Free the Quark 3 from asymptotic confinement! Bring your charm! Don't get down! All colours and flavours welcome!
    3. Re:Note the mention of GNU by ajs · · Score: 2, Insightful

      Maybe if the GNU folks had only been working on a kernel instead of also doing the hundreds of other programs as well, they would have made more headway with HURD. And if Linus had been trying to do a whole OS and not just the kernel, Linux the kernel would still be early in development. Very doubtful.

      First off, keep in mind that originally, Linux was aimed at being more on-par with Minix than Hurd. Linus would have written it even if the Gnu folks didn't exist, though it would have been written with pcc instead of gcc. Early on, he didn't have or even target creating a "whole OS", just a terminal server.

      The mention of GNU should merely point out how important the GNU is in GNU/Linux. Every time I hear "GNU/Linux", I have to chuckle. It's a bit like Pittsburgh demanding that Ford vehicles be called Steel/Ford. It's the ultimate example of RMS's hubris, and frankly I find it unfortunate, since most of his fundamental ideas are not unreasonable, just his ego and his behavior.
    4. Re:Note the mention of GNU by Peaker · · Score: 2, Insightful

      The purpose of the GNU work is to make people aware of Freedom-related issues.

      Saying Stallman insisting on calling it GNU is hubris is funny, when you consider that its not Stallman who named it after his first name.

      Its reasonable to request distributions that are heavily based on Linux and GNU to mention GNU in their name.

      I would also think it is reasonable for a huge codebase such as KDE to request that, too. For example, "Kubuntu" for short, and "A KDE frontend to a GNU/Linux system" for long.

      Calling it "Kubuntu Linux" (or "Redhat Linux") despite that simple request is not "illegal" or even not legitimate, but it is not very considerate of the many people who contributed to GNU in the hopes of raising awareness to the GNU project and software Freedom.

    5. Re:Note the mention of GNU by Just+Some+Guy · · Score: 5, Insightful

      This is an example why open source projects are more effective when they're driven by pragmatism and not politics.

      The problem is that politics is interested in you even if you're not interested in it. The pragmatic approach involves taking politics into account even if you're personally bored to tears by the subject.

      --
      Dewey, what part of this looks like authorities should be involved?
    6. Re:Note the mention of GNU by ajs · · Score: 2, Insightful

      The purpose of the GNU work is to make people aware of Freedom-related issues. Ah... look, young'un... GNU was founded to create a system that wouldn't restrict people's ability to use it to its fullest, which many of the people involved early on, including Stallman, felt needed to involve the ability to read, modify and distribute source code. It was not some sort of "sowing the seeds of freedom among the heathens," effort.

      Saying Stallman insisting on calling it GNU is hubris is funny, when you consider that its not Stallman who named it after his first name. Wherein my example is quite apt... We could say that it's horrible hubris of Ford to have named his company after himself... really, the so-called "Ford" was a result of the tremendous advances made in the previous 20 years by the Steele industry. It's only fair for such a misguided naming to be corrected by the "Steele/Ford Motor Company."

      No. People name things, not to ascribe merit, but in order to provide them with a label. Linux was named Linux. Why it was named Linux is irrelevant, that's it's name.

      Its reasonable to request distributions that are heavily based on Linux and GNU to mention GNU in their name. Not at all.

      I would also think it is reasonable for a huge codebase such as KDE to request that, too. For example, "Kubuntu" for short, and "A KDE frontend to a GNU/Linux system" for long. Great. Enjoy booting your GKXMITBSDBunnix. Bottom line: a name is a label, not a laundry list of ingredients.
  15. Well by akkarin · · Score: 5, Funny

    "Oh, Linux will *never* have a fan base. Never. Ever. Period."
    - Bill Gates

    --
    This sig left intentionally blank.
  16. Re:History of GCC by gr8_phk · · Score: 4, Interesting

    I use gcc but I'm not so sure its history would be that interesting to me.
    I'm no historian, but I think the origin of GCC is very interesting. When RMS started the GNU project, he was not a compiler guy. He had written system tools, but never a compiler. He recognized that any free operating system (GNU in particular) would require a free compiler and that this was a requirement, not an option. So he sat down and wrote the first GCC himself. It wasn't something he wanted to do, but it was fundamental to his vision so he did it anyway. That speaks to his insight, ability, and dedication. Most important was the insight. Imagine where GNU/Linux would be today if it had to rely on commercial compilers. Yep, that's right - it wouldn't exist.

    Also, there is much discussion about GCC transitioning to GPLv3 license. Apparently once the 4.3 branch is released, 4.2 will no longer be maintained under GPLv2. I believe this is because the FSF knows the compiler is fundamental and the license change is so important they don't really want patches contributing to the version under the old license.

  17. More than just a kernel by sepluv · · Score: 4, Informative
    just as a preemptive strike against all the Linus-entirely-made-the-OS-himself trolls before they come out of the woodwork, here is the last paragraph of section 2 from the announcement in the TFA. Torvalds says it better than I could:

    Sadly, a kernel by itself gets you nowhere. To get a working system you need a shell, compilers, a library etc. These are separate parts and may be under a stricter (or even looser) copyright. Most of the tools used with linux are GNU software and are under the GNU copyleft. These tools aren't in the distribution - ask me (or GNU) for more info.
    --
    Joe Llywelyn Griffith Blakesley
    [This post is in the public domain (copyright-free) unless otherwise stated]
  18. Re:How would one build this? by squiggleslash · · Score: 4, Insightful

    It got quiet a bit of interest, but was hampered by two major issues initially.

    First, it wasn't free software. It was shared source, you could obtain the source after buying a copy and share that source with others who had also bought a copy, but you couldn't just modify it and pass on your modifications to anyone who wanted. That extra step of "Receiver must already have a license" was an issue, and reduced the number of experimenters and tinkerers drastically. GNU/Linux has achieved much of its popularity through the ability of virtually anyone who has a copy to pass on that copy to others, with freely downloadable LiveCDs and other ways to be exposed to it with little commitment on your part.

    The other was that it was (usually, at least in x86) 16 bit. Applications generally ran in 64k memory spaces (albeit different spaces for code and data.) This severely limited the available functionality.

    Linus, in part, wrote the first Linux kernel to try to overcome the second issue. By using Linux + the GNU toolchain instead of Minix, you had a full blown 32 bit operating system. Things like the X11 Windowing System suddenly became possible. His eventual adoption of the GPL also gave Linux users the freedom needed to ensure they could build a much bigger community around that kernel than Minix was able to achieve.

    Today, Minix version 3 is available as free software, and in 32 bit form, but it happened too late to stop the GNU/Linux juggernaut from rolling right over it.

    --
    You are not alone. This is not normal. None of this is normal.
  19. Embarassing change of context by Anonymous Coward · · Score: 5, Funny

    Am I the only one twisted enough to have fixed for a moment on the once perfectly innocent sentence : "Could someone please try to finger me from overseas?"... :)

  20. Ready? by bollucks · · Score: 4, Funny

    ...and it was almost ready for the desktop.

    1. Re:Ready? by RAMMS+EIN · · Score: 2, Informative

      ``...and it was almost ready for the desktop.''

      At the time, it sort of was. Remember, this was the age of DOS. I don't know how much you could actually do with Linux at the time, but GNU was already a vastly more featureful system than DOS. When the first Linux distribution came out (Slackware, 1993), it sported all the glory of the GNU system, a GUI (XFree86), the ability to run DOS, and, if I recall correctly, even some support for running win16 (remember, Windows 95 wasn't out yet) programs.

      --
      Please correct me if I got my facts wrong.
  21. Re:History of GCC by LWATCDR · · Score: 2, Informative

    Hate to tell you this but GCC wasn't the first free compiler. It wasn't even the first c compile.
    There was the Small c compiler that dates back all the way to 1980. There was also the DICE compiler for the Amiga written by Matt Dillon of FireflyBSD fame that was from around the same time frame.
    Now GCC is leaps and bounds ahead of those compilers today but without if RMS hadn't written GCC frankly I think Somebody would have like Matt Dillon maybe.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  22. Ah, the good old days...accounting by wandazulu · · Score: 4, Interesting

    Because I was a computer-room assistant back in college I got a couple of Unix accounts (that's what they were called) to learn and possibly help the grad students who were doing all the "cool" stuff on them (as opposed to showing a freshman how to print from WordPerfect 5.1 for DOS (F7 baby!)). The problem with the Unix machines (a SunOS and an Ultrix box) was that they both had accounting turned on and so I had $5000 of computer time to use until I had to go back and ask for more, which they actually gave only begrudgingly. I guess some departments really paid some $$$ for access.

    Anyway, along comes Linux (not .01 but some very pre-1.0 version) and somebody else put it on a Gateway2000 486 machine) and all of a sudden I had, along with all the other assistants, a Unix-like machine we could call our own, do whatever we want and not worry about screwing up the "real" work being done. So when it came to learning how the Unix-world worked, I learned far more on that early Linux box than either SunOS or Ultrix if only because I didn't have to deal all the accounting stuff.

    The funny thing is that I remember feeling that the Linux box responded better than the Sun machine or the VAX in that it seemed to handle more users better (though I suppose on the Linux box we were just mucking about with standard commands instead of doing heavy-duty work).

  23. Re:How would one build this? by LWATCDR · · Score: 4, Informative

    Well I think that is a bit unfair.
    Minix and Linux where different proposes in mind from the start. I would consider them be both be highly successful.
    Minix was included with a text book. Minix was written to teach students how a Unix like OS worked so they could learn how write operating system code! Minix was very portable, clearly written, and would even run on an 8088 and 68000. It's technical limitations where just a logical trade off.
    Requiring people to own the book to have the OS was probably a mistake but My guess is that the author wanted to prevent people from reselling Minix. Plus he really wanted people to buy his book.
    Linux was some guy that wanted to write a free Unix Kernel for his 386 and he didn't care if it worked on anything but a 386 or frankly anything but his own computer.
    Frankly at that time I and everybody else was waiting for the real free UNIX that the GNU project was going to write. The future was going to be GNU Unix and it was going to be a state of the art micro kernel based UNIX like OS. Of course the future doesn't really feel obligated to follow our plans.
    Minix was a brilliant success. How many of the early Linux Kernel developers read Operating Systems: Design and Implementation by Andrew S. Tanenbaum?
    I would say that Minix it did it's job very well.

    Now Minix3 is a very new project. Frankly I find it very interesting. It is micro kernel and it runs drivers in user space. The goal is to create self healing OS. AKA a driver crashing will not take out the OS.
    It uses BSD instead of the GPL which I am beginning to favor because of what I consider the bad spirited anti-Tivo clauses in GPLV3.
    I really hope that Minix3 does get the attention that it deserves. Just as I hope the OpenBSD, FreeBSD, NetBSD, DragonflyBSD, and Linux continue to grow and thrive.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  24. Re:History of GCC by fsmunoz · · Score: 2, Informative

    Hate to tell you this but GCC wasn't the first free compiler. It wasn't even the first c compile.
    Maybe not, but your examples don't seem to totally support that :)

    There was the Small c compiler that dates back all the way to 1980.
    That's correct, but the scope of Small C and GCC are, I think, a bit different... Small C was made for embeded systems and supports a subset of the C language. It was there, true, but GCC was the first ANSI C free compiler.

    There was also the DICE compiler for the Amiga written by Matt Dillon of FireflyBSD fame that was from around the same time frame.
    DICE was shareware (... I sold DICE as shareware and it quite unexpectedly generated a fair chunk of income. This allowed me to expand into later Amiga models (A3000) as well as put together some fairly souped up PC's (for the times), on which I ran Linux...). The source code has been made available (http://www.obviously.com/dice/) but that was in 1997, so quite recently comparing with GCC. I'm not even going into the DICE licence.

    if RMS hadn't written GCC frankly I think Somebody would have like Matt Dillon maybe.

    Sure. That can be said of anything ever done by anyone I think...
  25. Re:5 most important OSS figures by SL+Baur · · Score: 2, Insightful

    Richard Stallman - ... I couldn't believe it when I noticed you actually bothered to reply to my e-mail when I asked you something about X window system. Spamming for a donation to the League for Programming Freedom doesn't count.

    You have a strange list. You left out the most important kernel programmer ever - Ken Thompson, you also left out Dennis Ritchie (first C compiler, designer of the first Unix file system), and for promoting excellent modern programming practices and teaching us all how to program the right way - Brian Kernighan and PJ Plauger.

    And what about Larry Wall for Perl? John McCarthy for Lisp (say what you want about Lisp, but it's the only language that has survived with programming mindshare for over half a century)? The lead engineer of the group at IBM who wrote the first high level language compiler for Fortran, proving that assembly language wasn't the end-all for efficient programming? Donald Knuth for his programming books and TeX?
  26. Re:How would one build this? by RAMMS+EIN · · Score: 3, Informative

    ``Plus he really wanted people to buy his book.''

    He, or the publisher. IIRC, it took quite some convincing on Andy's part to actually allow Minix to be distributed by third parties at all.

    --
    Please correct me if I got my facts wrong.
  27. Re:"Humble beginnings" by RockoTDF · · Score: 2, Funny

    Funny....no one in the IT dept where I work (besides me) knows shit about Linux...much less its history. No wonder nothing here works properly...

    --
    There is more to science than physics!

    www.iomalfunction.blogspot.com
  28. IBM, Intel, and MS say "you're welcome" by ClosedSource · · Score: 2, Insightful

    because they were the companies that made a low-cost Linux-capable machine economically feasible.

  29. MS had this too ya know.... by conares · · Score: 2, Funny

    ...only problem is all their correspondance was written in an proprietary format and theres no app to read it anymore....

    --
    That, that really grinds my gears!
  30. Linus gone wild by doorwayboy · · Score: 3, Funny

    Anyone else notice the two pics of a young Linus were are linus1.gif and linus3.gif?
    http://kerneltrap.org/files/linus2.gif

  31. More like Phoenix and AMD by IvyKing · · Score: 2, Informative
    If it weren't for the PeeCee clone market made possible by the Phoenix BIOS and the competition in the processor market keeping Intel on their toes, the low cost high performance Linux system as we know it wouldn't exist.


    Remember, back around 1990, IBM and Compaq system prices were pretty close to what was being asked for low end HP/Apollo, Sun and MIPS boxes. Now if DEC had been more agressive with the pricing for Alpha and Ultrix...

    1. Re:More like Phoenix and AMD by IvyKing · · Score: 2, Insightful
      If you're going to bring up MS-DOS, you might as well mention Seattle Computer Products. The reason that MS-DOS was available for other machines was that it was originally written by SCP for their own hardware - and since IBM did not pay for the original development, they had no exclusive rights to MS-DOS. BTW, Compaq and a few other companies had their own forks of MS-DOS. Also BTW, DR-DOS was the result of DR reverse engineering a reverse engineered version of CP/M.


      What made the business case for the IBM PC was Lotus 1-2-3, which was written specifically for the PC. What helped the clone market was that the IBM PC design was pretty generic, allowing for relatively easy cloning.


      As for AMD's market share in 386 systems, it doesn't take much to force a change in Intel's pricing. FWIW, 486 motherboards were cheaper to build than 386 motherboards - the 486 had onchip cache and didn't need a numeric co-processor.

  32. It's too bad about teh Lunix, really by Anonymous Coward · · Score: 3, Funny

    You know, it really is a shame Lunis couldn't have been bothered to write it properly in the first place.

    All these years later, and he's still trying to cludge it together and keep it working. And let's not even talk about security- naming the problems with that would cause a buffer overflow on the forum.

    Had Lunis and company written it properly at the start, maybe he wouldn't still be chasing Windows 95's tail lights.

  33. Re:History of GCC by vga_init · · Score: 2, Informative

    Strictly speaking, he didn't just "sit down" and write his own compiler from scratch. He spent a lot of time searching for a free compiler that was already complete, and finally he found one. It wasn't a C compiler, so he made the necessary modifications to get it going. Also, he didn't do it by himself--Leonard Tower was working on it full time, and there were other assistants.

  34. OT: Look at all the low-id's come out! by WoTG · · Score: 2, Interesting

    I don't recall ever seeing so many 3 and 4 digit /. IDs post. Kind of an odd feeling in a geeky way.

    1. Re:OT: Look at all the low-id's come out! by Kilroy · · Score: 2, Funny

      We don't get out much anymore. It takes forever to render these new comment threads in Mosaic.