Slashdot Mirror


The Linux Kernel Archives

Jeremy Andrews writes "KernelTrap offers an interesting look at the history behind the Linux Kernel Archives, home of the Linux kernel. They start from the beginning in 1997, when kernel.org ran on a generic "white box PC" using a shared T1, to the present where it runs on multiple quad Opterons each with 24 gigabytes of RAM, 10 terabytes of disk space, and a gigabit link to the internet. Much of the article is based on an interview with Peter Anvin, also including quotes from Linus Torvalds, Paul Vixie of Internet Systems Consortium, Inc who donates the bandwidth, and Matt Taggart of Hewlett-Packard who donated the hardware."

9 of 154 comments (clear)

  1. Yes but... by PR_Alistair · · Score: 5, Funny
    multiple quad Opterons each with 24 gigabytes of RAM, 10 terabytes of disk space, and a gigabit link to the internet
    ...does it run Linux?
  2. Slashdot history! by Dante · · Score: 4, Interesting

    This was a great article! I can attest the there is quite a difference with the new hardware, I got a 500KBps download last night while downloading rc3-mm2.

    Can we please have the same kind of article about slashdot hardware?

    --
    "think of it as evolution in action"
    1. Re:Slashdot history! by VistaBoy · · Score: 4, Funny

      Oh, you mean the Macintosh Plus that CmdrTaco has in the corner of his living room?

  3. Interesting quote by LiENUS · · Score: 5, Interesting

    The 'kernel.org' domain name was picked because by that time in 1997 the more logical seeming Linux dot names were already taken. The Transmeta domain was intentionally not used to avoid creating the false perception that Transmeta owned Linux.

    I wonder what would have happened with Transmeta and Linux if they had used the Transmeta domain to host the kernel archives. Would IBM have gotten involved with Linux? Would SCO have sued Transmeta instead of IBM? Would Linus have left Transmeta?

  4. load average 1024??!!! by teeker · · Score: 4, Interesting

    Referring to 32-bit systems, Peter noted, "we learned that the Linux load average rolls over at 1024. And we actually found this out empirically."

    Can you even get the server to TELL you what the load is when it's that high?? That's INSANE!

    --
    teeker
  5. Hat's off to HP by oni · · Score: 4, Insightful

    I'm really happy to see HP giving so much support. I'll definitely remember this the next time someone asks my opinion about what server hardware to buy.

  6. noatime interesting by redelm · · Score: 4, Interesting
    More people should look into `noatime` for file-intensive systems. Peter said all the access time updates doubled his load average, and I've seen worse. Try running the `updatedb` to freshen the locate database. Takes minutes. remount FS noatime, flush buffers with a grepbomb, and it takes seconds. Remount with atime, back to minutes.

  7. Re:here's an idea by diegocgteleline.es · · Score: 4, Interesting

    DONT USE APACHE.

    This was suggested. The kernel.org people didn't seem to have interest in it. Those light http servers are probably good for lots of small static html files. kernel.org is not like that - it needs to serve + 20 MB files and CD ISOs. Your benchmarks don't measure that. I can bet the kernel.org people knows what they're using and they'd have switched if it'd be really useful.

  8. Re:here's an idea by hpa · · Score: 4, Informative

    We have, indeed, considered that, but it'd not really buy us anything. Earlier Apaches would sit on a lot of memory while serving large files, but current versions just have a thread sitting in sendfile(), which is just about as lightweight as you get.

    Sure, the startup cost of the transaction is higher than for a lightweight HTTP server, but the startup cost of the transaction isn't a big deal for us, and we appreciate the flexibility that Apache offers.