Slashdot Mirror


A Visual Expedition Inside the Linux File Systems

RazvanM writes "This is an attempt to visualize the relationships among the Linux File Systems through the lens of the external symbols their kernel modules use. We took an initial look a few months back but this time the scope is much broader. This analysis was done on 1377 kernel modules from 2.6.0 to 2.6.29, but there is also a small dip into the BSD world. The most thorough analysis was done on Daniel Phillips's tree, which contains the latest two disk-based file systems for Linux: tux3 and btrfs. The main techniques used to establish relationships among file systems are hierarchical clustering and phylogenetic trees. Also presented are a set of rankings based on various properties related to the evolution of the external symbols from one release to another, and complete timelines of the kernel releases for Linux, FreeBSD, NetBSD, and OpenBSD. In all there are 78 figures and 10 animations."

5 of 85 comments (clear)

  1. Hmm by Anonymous Coward · · Score: 5, Funny

    I could use a visual expedition among the various links on this summary.

  2. Let me correct that for you! by Azeroth48 · · Score: 4, Funny

    This analysis was done on 1337 kernel modules

    --
    This is where we are, our rock we stand, among the world, looking forward, eternally.
  3. Typo in summary. by SharpFang · · Score: 4, Funny

    This analysis was done on 1377 kernel modules from 2.6.0 to 2.6.29

    I think they meant 1337 kernel modules?

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  4. My chart by iamdrscience · · Score: 4, Funny

    Usefulness of a hammer:
    XXXXXXXXXXXXXXXXXXXXXXXXX

    Usefulness of an average Slashdot article:
    XXXXXX

    Usefulness of a screen door on a submarine:
    XXXX

    Usefulness of this Slashdot article:
    X

  5. Re:One other observation though... by jeremyp · · Score: 3, Funny

    It's easy.

    I did it once and the fact that it couldn't be mounted was offset by the fact that no bugs were ever reported, nor did it it ever corrupt or lose any data. In fact, I didn't even have to write any of the implementation.

    --
    All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe