fhs_ncomp.pcap.har

{
  "log": {
    "browser": {
      "name": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)", 
      "version": "mumble"
    }, 
    "creator": {
      "name": "pcap2har", 
      "version": "0.1"
    }, 
    "entries": [
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
        }, 
        "response": {
          "bodySize": 183005, 
          "content": {
            "compression": 0, 
            "mimeType": "text/xml", 
            "size": 183005, 
            "text": "<?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>\r\n<?xml-stylesheet type=\"text/xsl\" href=\"fhs.xsl\"?>\r\n\r\n<!--\r\n=====================================================================\r\n    Presence of <children> element indicates that the containing\r\n    file is a directory instead of a plain file, even if it's empty.\r\n=====================================================================\r\n-->\r\n\r\n<filesystem>\r\n\r\n    <intro>\r\n        <p>When using a Linux system, it's important to know how the operating system's filesystem hierarchy\r\n        is organized. Learning how the files on the system are organized is important to knowing how and\r\n        where software is installed, how it and the whole system are configured, where various information\r\n        is stored, and how all the pieces fit together. This document aims to help its reader learn how the\r\n        Linux filesystem is structured, by allowing them to explore it interactively while giving explanations\r\n        of what the reader is looking at.</p>\r\n        <p>Before the filesystem hierarchy was standardized, every Linux distributor put files wherever they wanted in\r\n        the hierarchy. There were a few conventions about naming and locations, but it was difficult to know\r\n        where to find something, documentation was hard to write, and everything was just a mess. Some Linux\r\n        people got together around 1993 and created a standard filesystem layout for Linux systems. This was\r\n        called the FSSTND (File System STaNDard), and was released in 1994. A few years later, they\r\n        collaborated with other people from BSD Unix to create a more broadly applicable standard, for not\r\n        only Linux but other Unixes and Unix-like systems (commonly called *nixes). This they called the\r\n        Filesystem Hierarchy Standard, or FHS. As of 2010, its latest version is 2.3, released in 2004 (FHS).</p>\r\n        <p>It has a faintly recursive structure, with certain names and structures repeated\r\n        and nested. Knowing what they mean allows one to get an idea of what a directory contains by its name and context. The FHS\r\n        separates shareable and non sharable files, and dynamic and static files, to allow them to be\r\n        organized and stored independently. It makes extensive use of\r\n        <a href=\"http://en.wikipedia.org/wiki/Symbolic_link\">symbolic links</a>, or symlinks, to enhance\r\n        flexibility by making files appear in more than one place; in many cases an actual file or symlink\r\n        to one are equally acceptable to the standard.</p>\r\n        <p>Frequently, the FHS seeks to specify not what files/directories should be present, but\r\n        simply where they should be found if they are present on the system. These files are described\r\n        in the standard as being \"required if the corresponding subsystem is installed.\" Here, they\r\n        are simply marked as \"optional\".</p>\r\n        <p>This document is aimed at intermediate beginners, with basic knowledge of how Linux works. It \r\n        uses the FHS as a base, and adds things that one is likely to find on a \"typical\" Linux system.\r\n        The reader is encouraged to poke around on his own system to see what's there.\r\n        The standard parts should also be applicable\r\n        to a BSD system, or any other FHS-compliant system. The standard and Linux-specific parts are both\r\n        distinguished. Angle-brackets (&lt;&gt;) are used to denote parts of filenames that need something\r\n        substituted in, like a name or number. A '*' will occasionally be used to denote a variable\r\n        substring in a filename, like in a shell wildcard.\r\n        Clicking on a filename will either expand or collapse its description and, if the file in question\r\n        is a directory, will also show its files and subdirectories. In addition to MLA-style references,\r\n        references will frequently be made to man pages, like df(1) or fstab(5). See the entry for \r\n        /usr/share/man for how to interpret those.</p>\r\n    </intro>\r\n\r\n    <file> <name>/</name>\r\n        <summary>The root directory for the entire virtual filesystem.\r\n            <a href=\"http://www.pathname.com/fhs/pub/fhs-2.3.html#THEROOTFILESYSTEM\">(standard)</a>\r\n        </summary>\r\n        <desc>\r\n            <p>The partition that the OS was booted from defines the contents of the root directory.\r\n            This partition must contain (at least) everything required to boot the system and/or restore\r\n            it from backups. This includes /boot, /bin, /sbin, and /lib at the least.</p>\r\n            <p>It's considered good practice to keep this partition small, moving large\r\n            directories like /usr, /var, and /opt to separate partitions. This helps isolate\r\n            disk corruption errors and makes the essential root partition less vulnerable to them.\r\n            Of course, these concerns don't apply as much to small home systems.\r\n            It may still be advisable to separate things with partitions, but you could just as\r\n            easily put everything in one partition.</p>\r\n        </desc>\r\n        <children>\r\n        \r\n            <file> <name>bin</name>\r\n                <summary>Essential programs (standard)</summary>\r\n                <desc>\r\n                    The name <tt>bin</tt>, wherever it appears, means that the folder in question\r\n                    contains programs, either binary executables or scripts. This directory contains basic,\r\n                    core commands that are always needed to run the system, for either users or administrators,\r\n                    as determined by the sysadmin. It must not contain any subdirectories. For the full list of\r\n                    required files, see the /bin entry in the\r\n                    <a href=\"http://www.pathname.com/fhs/pub/fhs-2.3.html#BINESSENTIALUSERCOMMANDBINARIES\">FHS</a>.\r\n                    The ones below are just a sample of the ones required by the standard, which are in\r\n                    turn just a small subset of the ones you are likely to find on your own system.\r\n                </desc>\r\n                <children>\r\n                    <file> <name>cat</name> <summary>Prints the contents of one or more files to standard output, con'cat'enating them. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/cat\">cat(1)</a></desc></file>\r\n                    <file><name>chmod</name> <summary>Changes permissions on a file. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/chmod\">chmod(1)</a></desc></file>\r\n                    <file><name>chown</name> <summary>Changes which user owns a file. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/chown\">chown(1)</a></desc></file>\r\n                    <file><name>cp</name> <summary>Copies files and directories. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/cp\">cp(1)</a></desc></file>\r\n                    <file><name>date</name> <summary>Sets or displays the system time and date. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/date\">date(1)</a></desc></file>\r\n                    <file><name>df</name> <summary>Reports disk space usage and related information. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/df\">df(1)</a></desc></file>\r\n                    <file><name>kill</name> <summary>Sends signals between processes. (standard)</summary>\r\n                        <desc>Typically used to send kill signals to a process, hence the name. <a href=\"http://linux.die.net/man/1/kill\">kill(1)</a></desc></file>\r\n                    <file><name>ln</name> <summary>Makes links between files. (standard)</summary>\r\n                        <desc>Both hard and symbolic links. <a href=\"http://linux.die.net/man/1/ln\">ln(1)</a></desc></file>\r\n                    <file><name>ls</name> <summary>Lists the contents of a directory. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/ls\">ls(1)</a></desc></file>\r\n                    <file><name>mkdir</name> <summary>Makes a new directory. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/mkdir\">mkdir(1)</a></desc></file>\r\n                    <file><name>more</name> <summary>Prints a file, either a disk file or standard input, to standard output, screen-full by screen-full. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/more\">more(1)</a></desc></file>\r\n                    <file><name>mount</name> <summary>Mounts a filesystem onto the existing filesystem. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/8/mount\">mount(8)</a>. See L\u00e5ngstedt.</desc></file>\r\n                    <file><name>umount</name> <summary>Unmounts a filesystem. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/8/umount\">umount(8)</a>. That's right, \"umount,\" not \"unmount\". See /bin/mount.</desc></file>\r\n                    <file><name>mv</name> <summary>Moves a file from one location to another, or renames it. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/mv\">mv(1)</a></desc></file>\r\n                    <file><name>ps</name> <summary>Displays the processes running on the system. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/ps\">ps(1)</a></desc></file>\r\n                    <file><name>rm</name> <summary>Deletes files. (standard)</summary>\r\n                        <desc><a href=\"http://linux.die.net/man/1/rm\">rm(1)</a></desc></file>\r\n                    <file> <name>sh</name> <summary>The standard Bourne command shell. (standard)</summary>\r\n                        <desc>Sometimes, this file is a symlink to /bin/bash, the Bourne-Again SHell. <a href=\"http://linux.die.net/man/1/sh\">sh(1)</a>.</desc></file>\r\n                </children>\r\n            </file>\r\n            \r\n            <file> <name>boot</name>\r\n                <summary>Files that are needed to boot the system. (standard)</summary>\r\n                <desc>\r\n                    <p>Contains files that are needed to boot the system. May include the operating system kernel, which is\r\n                    either here or directly in /, and static (unchanging) configuration files. For more, see the\r\n                    <a href=\"http://www.pathname.com/fhs/pub/fhs-2.3.html#BOOTSTATICFILESOFTHEBOOTLOADER\">/boot entry\r\n                    of the FHS</a>.</p><p>Sometimes this directory is placed in a separate partition. This way, the kernel\r\n                    can be placed in lower parts of the disk, which is the only place the BIOS's of some PC's can find it.\r\n                    Once the kernel takes over, it will be able to see the rest of the disk.</p></desc>\r\n                <children>\r\n                </children>\r\n            </file>\r\n            \r\n            <file> <name>dev</name>\r\n                <summary>Device files. (standard)</summary>\r\n                <desc>\r\n                    <p>Files that represent hard disk partitions, input devices, tty's, etc are stored here. For more, see the\r\n                    <a href=\"http://www.pathname.com/fhs/pub/fhs-2.3.html#DEVDEVICEFILES\">/dev entry in the FHS</a>. Only a\r\n                    sample can be shown here. The directories often just contain symlinks to files in /dev itself, and serve\r\n                    only as a way of highlighting them by their function.</p><p>On naming: The vast majority of device\r\n                    filenames here consist of a base name and an optional number, ordered according to the order in which\r\n                    the kernel discovered or created them (Debian Installation Guide, Appendix C.4). Here, these files are\r\n                    represented as the base name and an asterisk to represent the number, like hda*. This is the same\r\n                    syntax as is used in shell wildcards.</p><p>See also L\u00e5ngstedt.</p>\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file><name>block</name>\r\n                        <summary>Block devices. (Linux)</summary>\r\n                        <desc>\r\n                            This directory collects all block devices together, that is, devices that read and write data in\r\n                            big chunks, and whose reads and writes are buffered. It contains symlinks with names of the format\r\n                            &lt;major-number&gt;:&lt;minor-number&gt;, with the major and minor numbers of the device. 3:2 for example, which\r\n                            link to the actual device in /dev itself. The major number of a device\r\n                            identifies the device driver, while the minor number distinguishes individual devices (Mohr).\r\n                        </desc>\r\n                        <children>\r\n                            <file><name>&lt;major-number&gt;:&lt;minor-number&gt;</name><summary>Symlink to a block device in /dev.</summary></file>\r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>bus</name>\r\n                        <summary>Devices organized by bus type. (Linux)</summary>\r\n                        <desc>\r\n                            Contains subdirectories for each bus type, or each type of information pathway in the computer\r\n                            hardware. Further subdirectories eventually lead to device files, which correspond to physical\r\n                            devices that use that type of bus.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>char</name>\r\n                        <summary>Character devices. (Linux)</summary>\r\n                        <desc>\r\n                            This directory contains links to all character devices, that is, devices that read and write data\r\n                            one character at a time. The links have names with the format &lt;major&gt;:&lt;minor&gt;, which link back\r\n                            the actual file /dev itself. For example, 2:14. The major number of a device identifies the\r\n                            device driver, while the minor number distinguishes individual devices (Mohr).\r\n                        </desc>\r\n                        <children>\r\n                            <file><name>&lt;major-number&gt;:&lt;minor-number&gt;</name><summary>Symlink to a character device in /dev.</summary></file>\r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>disk</name>\r\n                        <summary>Disk devices, organized by various criteria. (Linux)</summary>\r\n                        <children>\r\n                        \r\n                            <file><name>by-id</name>\r\n                                <summary>Disks organized by their ID's.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>by-label</name>\r\n                                <summary>Disks organized by their labels.</summary>\r\n                                <desc>\r\n                                    If any disks have labels, they show up here.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>by-path</name>\r\n                                <summary>Disks organized by the hardware path to access them.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>by-uuid</name>\r\n                                <summary>Disks organized by their UUID.</summary>\r\n                                <desc>\r\n                                    UUID stands for Universally Unique Identifier. Every disk has one.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                     </file>\r\n                     \r\n                     <file><name>input</name>\r\n                        <summary>Input devices. (Linux)</summary>\r\n                        <desc>\r\n                            Mice and keyboards and stuff. Also contains other character files.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>by-id</name>\r\n                                <summary>Input devices organized by ID.</summary>\r\n                                <desc>\r\n                                    Contains appropriately-named symlinks to devices in the containing directory.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>by-path</name>\r\n                                <summary>Input devices organized by hardware path.</summary>\r\n                                <desc>\r\n                                    Contains symlinks to devices in containing directory, named so as to indicate the hardware\r\n                                    path to access the actual device.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                     </file>\r\n                     \r\n                     <file><name>pts</name>\r\n                         <summary>The slave ends of pseudo terminals. (Linux)</summary>\r\n                         <desc>\r\n                             A pseudo terminal consists of two virtual character devices, which together form a channel of communication for two processes. One of the ends is a master end, and the other is the slave end (pty(7)). This directory contains the slave ends of Unix98-style psuedo-terminals, as they are created(pts(4)).\r\n                         </desc>\r\n                         <children></children>\r\n                     </file>\r\n                     \r\n                     <file><name>snd</name>\r\n                         <summary>Sound-related devices. (Linux)</summary>\r\n                         <children></children>\r\n                     </file>\r\n                     \r\n                     <file><name>cd*</name>\r\n                         <summary>CDROM devices. (Linux)</summary>\r\n                         <desc>\r\n                             Numbered in order of their appearance to the kernel. May be the same as an hd* or scd* device.\r\n                         </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>fd*</name>\r\n                         <summary>Floppy disk drives. (Linux)</summary>\r\n                         <desc>\r\n                             Numbered as they appear to the kernel.\r\n                         </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>hda*</name>\r\n                         <summary>IDE primary master and its partitions. (Linux)</summary>\r\n                         <desc>\r\n                             An IDE controller can have two devices attached to it, a master and a slave, and there can usually\r\n                             only be two IDE controllers, giving four IDE devices in total, named hda to hdd. They might be hard\r\n                             disks, CD drives, or anything else that can interact with the system through the IDE interface.\r\n                             Primary partitions on a device are referred to by number from 1 to 4, like hda1, hda2, etc.\r\n                             Logical partitions are numbered starting at 5; hda5 is the first logical partition on the primary\r\n                             master IDE device (Debian Installer Team, Appendix C.4)\r\n                         </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>hdb*</name>\r\n                         <summary>IDE primary slave and its partitions. (Linux)</summary>\r\n                         <desc>See hda* for details.</desc>\r\n                     </file>\r\n                     \r\n                     <file><name>hdc*</name>\r\n                         <summary>IDE secondary master and its partitions. (Linux)</summary>\r\n                         <desc>See hda* for details.</desc>\r\n                     </file>\r\n                     \r\n                     <file><name>hdd*</name>\r\n                         <summary>IDE secondary slave and its partitions. (Linux)</summary>\r\n                         <desc>See hda* for details.</desc>\r\n                     </file>\r\n                     \r\n                     <file><name>sda*</name>\r\n                        <summary>First SCSI disk and its partitions. (Linux)</summary>\r\n                        <desc>\r\n                            SCSI disks are named sda, sdb, sdc, sdd, etc, ordered according to their SCSI ID. They can represent\r\n                            either a hard disk or another SCSI device. Primary partitions on a device are referred to by\r\n                            number from 1 to 4, like sda1, sda2, etc. Logical partitions are numbered starting at 5; sda5\r\n                            is the first logical partition on the first SCSI device (Debian Installer Team, Appendix C.4).\r\n                        </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>sdb*</name>\r\n                         <summary>Second SCSI device and its partitions. (Linux)</summary>\r\n                         <desc>See sda* for details.</desc>\r\n                     </file>\r\n                     \r\n                     <file><name>sdc*</name>\r\n                         <summary>Third SCSI device and its partitions. (Linux)</summary>\r\n                         <desc>See sda* for details.</desc>\r\n                     </file>\r\n                     \r\n                     <file><name>sdd*</name>\r\n                         <summary>Fourth SCSI device and its partitions. (Linux)</summary>\r\n                         <desc>See sda* for details.</desc>\r\n                     </file>\r\n                     \r\n                     <file><name>tty*</name>\r\n                         <summary>TTY devices. (Linux)</summary>\r\n                         <desc>\r\n                             <p>TTY devices are terminal devices. They are not only used for user terminals, but for access to\r\n                             serial ports and network connections. Basically, they're a generic two-way stream of characters.</p>\r\n                             <p>At a terminal, you can find out what terminal file you're using by using the tty command, which\r\n                             prints the name of the terminal it is connected. It may be a psuedo-terminal; see /dev/pts and\r\n                             /dev/pty*.</p>\r\n                         </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>pty*</name>\r\n                         <summary>Slave ends of pseudo-terminals. (Linux)</summary>\r\n                         <desc>\r\n                             The slave ends of BSD-style pseudo-terminals See <a href=\"http://linux.die.net/man/7/pty\">pty(7)</a> for\r\n                             details on the difference between a pty and pts.\r\n                         </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>null</name>\r\n                          <summary>The \"black hole\" file. (Linux)</summary>\r\n                          <desc>\r\n                              Sometimes you just want to run a program and completely get rid of its output. Redirect its\r\n                              output to /dev/null, and it will never trouble the land of the living. Reads always fail.\r\n                          </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>zero</name>\r\n                        <summary>Zero file. (Linux)</summary>\r\n                        <desc>\r\n                            When read, returns nothing but zeros. Handy if you want a file of a specific length without\r\n                            bothering about its contents. Ignores writes.\r\n                        </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>MAKEDEV</name>\r\n                        <summary>Command to make device files (standard, optional).</summary>\r\n                        <desc>\r\n                            Sometimes, device files need to be manually created. If so, then this executable file needs to\r\n                            be here, and needs to create the device files.\r\n                        </desc>\r\n                     </file>\r\n                     \r\n                     <file><name>MAKEDEV.local</name>\r\n                        <summary>Command to create local devices. (standard, optional)</summary>\r\n                        <desc>\r\n                            This is a script written by the system administrator for creating devices,\r\n                            specific to the machine. (Wirzenius et al)\r\n                        </desc>\r\n                     </file>\r\n                     \r\n                </children>\r\n            </file>\r\n            \r\n            <file> <name>etc</name>\r\n                <summary>Configuration files. (standard)</summary>\r\n                <desc>\r\n                    <p>Most static configuration files for the system are kept here. They are always human-readable text files.\r\n                    Many of them take the form of scripts, most notably the system startup scripts, but no binary programs\r\n                    are allowed anywhere in /etc. These files are specific to the computer on which they reside. They may\r\n                    contain settings that are only valid for the hardware of that one machine. (FHS)</p><p>There may be a few\r\n                    dynamic files here, holdovers from non-standardized days and left in for backwards compatibility.</p>\r\n                </desc>\r\n                <children>\r\n                    \r\n                    <file><name>opt</name>\r\n                        <summary>Configuration for /opt. (standard)</summary>\r\n                        <desc>\r\n                            Configuration files for software packages installed in /opt. Contains directories named after each\r\n                            directory in /opt, which can contain any structure desired by the package. The configuration\r\n                            files for a package can be placed somewhere else if necessary for the package to function. See /opt/.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>foo</name>\r\n                                <summary>Configuration for a package named foo.</summary>\r\n                                <desc>\r\n                                    A package installed in /opt/foo would have its configuration files here. It can be organized\r\n                                    however the package designer desires. See /opt/foo/\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>baz-inc</name>\r\n                                <summary>Configuration for Baz Inc.'s products.</summary>\r\n                                <children>\r\n                                    <file><name>baz</name>\r\n                                        <summary>Configuration for product Baz.</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                </children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>local</name>\r\n                        <summary>Configuration for programs installed in /usr/local. (standard, optional)</summary>\r\n                        <desc>\r\n                            Ideally, programs in /usr/local are configured in /usr/local/etc, but if the sysadmin wants to\r\n                            have all configuration in one place, they can symlink /usr/local/etc to this folder (FHS). See /usr/local.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>X11</name>\r\n                        <summary>Configuration for the X11 window system. (standard, optional)</summary>\r\n                        <desc>\r\n                            If the X11 window system is installed, this is where its configuration files live. It may contain\r\n                            configuration files for subdirectories for window managers, or other programs related to X.\r\n                            Directories for window managers must have the same name as the window manager binary.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>Xconfig</name>\r\n                                <summary>Old form of XFree86 config file. (standard, optional)</summary>\r\n                                <desc>\r\n                                    XFree86 is an X server implementation. If the system uses an old version that uses this\r\n                                    type of configuration file, this is where it must be located.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>XF86Config</name>\r\n                                <summary>Configuration file for XFree86 versions 3 and 4. (standard, optional).</summary>\r\n                                <desc>If you have one of these versions of XFree86, this is its configuration file.</desc>\r\n                            </file>\r\n                            \r\n                            <file><name>Xmodmap</name>\r\n                                <summary>Global keyboard modification file for X. (standard, optional)</summary>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>sgml</name>\r\n                        <summary>Configuration files for SGML. (standard, optional)</summary>\r\n                        <desc>\r\n                            SGML stands for Standard Generalized Markup language. It's a precursor to XML, eXtensible Markup\r\n                            Language. It is, among other things, the meta-language in which HTML is defined. Here is where\r\n                            configuration files for systems that use SGML live, if they are needed at all.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>*.cat</name>\r\n                                <summary>DTD-specific catalogs. (standard)</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>*.conf</name>\r\n                                <summary>Normal configuration files. (standard, optional)</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>catalog</name>\r\n                                <summary>\"Super-catalog\" that references all the centralized catalogs. (standard, optional)</summary>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>xml</name>\r\n                        <summary>Configuration files for XML. (standard, optional)</summary>\r\n                        <desc>\r\n                            Configuration files for programs that use XML live here. XML stands for eXtensible Markup Language,\r\n                            and is the successor of SGML.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>*.conf</name>\r\n                                <summary>Generic configuration file for XML systems. (standard, optional)</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>catalog</name>\r\n                                <summary>\"Super catalog\" that references all other centralized catalogs. (standard, optional)</summary>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>init.d</name>\r\n                        <summary>System startup scripts.</summary>\r\n                        <desc>\r\n                            There are many different ways of organizing startup scripts, not all of which even include this\r\n                            particular directory. This document will not attempt to illustrate them.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>adjtime</name>\r\n                        <summary>Historical location for adjtime file.</summary>\r\n                        <desc>\r\n                            File used by hwclock(8) to correct for system clock drift. See /var/lib/hwclock/adjtime.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>crontab</name>'\r\n                        <summary>Configuration for cron.</summary>\r\n                        <desc>\r\n                            Cron is a program that performs scheduled tasks. This is the file that tells cron which commands\r\n                            to execute when. See <a href=\"http://linux.die.net/man/5/crontab\">crontab(5)</a> for the details\r\n                            of the format.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>csh.login</name>\r\n                        <summary>System-wide startup file for C shell logins. (standard, optional)</summary>\r\n                        <desc>\r\n                            Every time someone logs into a C shell, this file is run. A system administrator can use it to\r\n                            set environment variables, or do other house-keeping tasks.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>csh.cshrc</name>\r\n                        <summary>System-wide .cshrc.</summary>\r\n                        <desc>\r\n                            This is another file executed by csh upon login. Its purpose is to set things like search paths\r\n                            and command aliases, as opposed to general commands executed by /etc/csh.login. The\r\n                            distinction is largely up to the sysadmin. It should not, however, contain commands that\r\n                            produce output, or assume that the shell is connected to a tty.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>csh.logout</name>\r\n                        <summary>System-wide logout file for csh.</summary>\r\n                        <desc>This file is run whenever a csh shell exits.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>fstab</name>\r\n                        <summary>Describes how filesystems should be mounted.</summary>\r\n                        <desc>\r\n                            Each entry in fstab consists of a device file name, the location where it should be mounted,\r\n                            the filesystem type presumed to be on the device, and several configuration parameters,\r\n                            including whether the device should be mounted at bootup, whether it should be read-only,\r\n                            etc. If a device is listed in fstab, you can run <tt>mount</tt> with just either the device name\r\n                            or its mount point, and it will be mounted automatically with the parameters in fstab. fstab\r\n                            also dictates whether the device should be automatically backed up by <tt>dump</tt>, and the order\r\n                            in which devices should be checked by <tt>fsck</tt>. For more information see this page:\r\n                            http://www.tuxfiles.org/linuxhelp/fstab.html or fstab(5).\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>group</name>\r\n                        <summary>List of user groups. (standard, optional)</summary>\r\n                        <desc>\r\n                            This file defines the names, passwords, numeric group id's (GID), and members of user groups.\r\n                            A group is used to give a number of users specific privileges on files. Every file has both an\r\n                            owner and a group, and a list of actions that each can take. If you are in the group that owns\r\n                            the file, you can do the things that the file's permissions grant to the group. The password\r\n                            is used for people who are not actually members of the group to gain temporary access to group\r\n                            privileges. See <a href=\"http://linux.die.net/man/5/group\">group(5)</a> for more.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>gshadow</name>\r\n                        <summary>Actual group passwords.</summary>\r\n                        <desc>\r\n                            See /etc/group for how group passwords work, and /etc/shadow for\r\n                            why they might be hidden in this file.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>hosts</name>\r\n                        <summary>Contains static mappings of IP addresses to hostnames.  (standard, optional)</summary>\r\n                        <desc>\r\n                            Usually used when hostnames need to be resolved into IP addresses but DNS is not running for some\r\n                            reason, during bootup, for instance. See also <a href=\"http://linux.die.net/man/5/hosts\">hosts(5)</a>.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>inittab</name>\r\n                        <summary>Configuration file for init process (standard, optional)</summary>\r\n                        <desc>\r\n                            The init process is the parent of all other processes. It reads this file to determine what\r\n                            processes it should start at any runlevel. In other words, this file describes what the state\r\n                            of the system should be in single-user mode, multi-user mode, when it restarts or shuts down,\r\n                            etc. See <a href=\"http://linux.die.net/man/5/inittab\">inittab(5)</a>.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>mtab</name>\r\n                        <summary>Historical location for dynamic information about filesystems that are mounted. (standard, optional)</summary>\r\n                        <desc>\r\n                            This is an exception to the rule that only static information should be in /etc. It is only granted\r\n                            because of historical precedent. See /proc/mounts.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>passwd</name>\r\n                        <summary>Login password file. (standard, optional)</summary>\r\n                        <desc>\r\n                            Stores several pieces of information about each user, including their name, possibly their password,\r\n                            numerical user id, home directory, and default shell\r\n                            (<a href=\"http://linux.die.net/man/5/passwd\">passwd5</a>)). The actual encrypted passwords\r\n                            may be in /etc/shadow instead. See the /etc/shadow entry for more.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>profile</name>\r\n                        <summary>System-wide login script for the sh shell (standard, optional)</summary>\r\n                        <desc>\r\n                            Every time a sh or related shell starts, like bash, csh, or ksh, it first runs this file,\r\n                            which can do any setup desired by the system administrator.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>profile.d</name>\r\n                        <summary>Login scripts.</summary>\r\n                        <desc>\r\n                            This directory contains scripts called by login scripts, to keep them out of the way in /etc/ itself.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>shadow</name>\r\n                        <summary>Shadow password file.</summary>\r\n                        <desc>\r\n                            Many programs need to be able to map user names to numerical id's, but it's dangerous to\r\n                            allow anyone to read the actual encrypted passwords in /etc/passwd. When using /etc/shadow,\r\n                            anyone can get basic information about users from /etc/passwd, but the password\r\n                            information can be separated into this file, where it can be shielded by restricted\r\n                            read permissions. (<a href=\"http://linux.die.net/man/5/shadow\">shadow(5)</a>)\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>shells</name>\r\n                        <summary>Trusted shell programs.</summary>\r\n                        <desc>\r\n                            The <a href=\"http://linux.die.net/man/1/chsh\">chsh(1)</a> program only allows users to change\r\n                            their login shell to a shell in this list.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>skel</name>\r\n                        <summary>'Skeleton' directory for new users' home directories.</summary>\r\n                        <desc>\r\n                            The contents of this directory are copied into the home directories of new users\r\n                            (<a href=\"http://linux.die.net/man/8/useradd\">useradd(8)</a>). It can be used to\r\n                            set default settings for users.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>sysctl.conf</name>\r\n                        <summary>System parameters. (Linux)</summary>\r\n                        <desc>\r\n                            This file is read by the program <a href=\"http://linux.die.net/man/8/sysctl\">sysctl(8)</a> at\r\n                            startup, which uses it to set the values of whatever kernel variables the\r\n                            sysadmin sees fit to include.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file> <!-- etc -->\r\n            \r\n            <file> <name>home</name>\r\n                <summary>Home directories for users. (standard, optional)</summary>\r\n                <desc>\r\n                    <p>Users on a linux system have a home directory, where they can keep their personal files and projects.\r\n                    Sometimes this is a directory named after them in /home, like /home/frank, but systems that have to\r\n                    support a large number of users may put frank in /home/f/frank, or even /home/f/fr/frank. It's up\r\n                    to the system administrator. Programs should not rely on any assumptions about this directory's\r\n                    internal layout or even its existence.</p><p>This is another directory that can be good to put\r\n                    on a separate partition. That way, one can re-install the operating system or anything else\r\n                    without affecting anyone's personal files.</p><p>See /etc/skel/.</p>\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file><name>frank</name>\r\n                        <summary>Sample home directory for a user named frank.</summary>\r\n                        <desc>\r\n                            <p>In this directory, frank can put pretty much anything he wants. Also here are his user-specific\r\n                            configuration files, like personal settings in his programs and his shell login profile. A few of\r\n                            the common ones are listed here. Many of them are hidden files, named beginning with a '.', so\r\n                            they stay out of the way of the users day-to-day work. An applications that stores user-specific\r\n                            settings in a user's home directory should either name their file starting with a '.', or put them\r\n                            in a folder starting with a '.'.</p><p>When a user is logged in, their home directory can be\r\n                            referred to by the name '~' in the shell. For examle, a user's .profile can be referred to as\r\n                            ~/.profile.</p>\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>.profile</name>\r\n                                <summary>Default user login script.</summary>\r\n                                <desc>User login run by sh and its relatives.</desc>\r\n                            </file>\r\n                            \r\n                            <file><name>.bash_profile</name>\r\n                                <summary>Default login script for bash shell.</summary>\r\n                                <desc>\r\n                                    This is bash's preferred login script. The bash shell, when starting in interactive mode\r\n                                    (ie, not just running a script), runs the first of the following files it finds:\r\n                                    ~/.bash_profile, ~/.bash_login, and ~/.profile. (bash(1))\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>.bash_logout</name>\r\n                                <summary>Bash logout script.</summary>\r\n                                <desc>\r\n                                    If it exists, bash executes this file upon exiting interactive mode. (bash(1))\r\n                                </desc>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file>\r\n                \r\n                </children>\r\n            </file>\r\n            \r\n            <file> <name>lib</name>\r\n                <summary>Essential shared libraries for the programs in /bin and /sbin. (standard)</summary>\r\n                <desc>\r\n                    <p>This directory stores shared libraries \"needed to boot the system and run the commands in the root\r\n                    filesystem, i.e. by binaries in /bin and /sbin\", according to the FHS.</p><p>Shared libraries allow\r\n                    many programs to share the same code, reducing disk usage and allowing them all to be updated at once\r\n                    with minor bug-fixes and the like. They have the extension .so (which stands for \"shared object\"),\r\n                    sometimes with an additional extension containing the version number.</p><p>The name 'lib', where\r\n                    it appears in the filesystem hierarchy, can refer not only to shared libraries but to any other static\r\n                    data or code required by a program, including other programs which are not meant to be used directly\r\n                    by users. However, shared libraries are the most common thing in lib directories.</p>\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file> <name>modules</name>\r\n                        <summary>Where loadable kernel modules are placed.</summary>\r\n                        <desc>\r\n                            Kernel modules, or \"loadable kernel modules\" to be specific, are a mechanism of extending the Linux kernel without having to recompile the whole thing. A kernel module is basically a shared library that is loaded into the kernel. Modules are separated based on the version of the kernel they are compiled for.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>&lt;kernel-version&gt;</name>\r\n                                <summary>Modules for the kernel &lt;kernel-version&gt;</summary>\r\n                                <desc>\r\n                                    Contains a lot of things besides just shared libraries. There are several data files,\r\n                                    which mostly have to do with interdependecies between modules. The actual kernel modules\r\n                                    (which have the extension '.ko' for \"kernel object\" since 2.6), start in the kernel directory.\r\n                                </desc>\r\n                                <children>\r\n                                \r\n                                    <file><name>build</name>\r\n                                        <summary>Symlink to the directory where the kernel was built.</summary>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>source</name>\r\n                                        <summary>Symlink to the kernel source tree.</summary>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>kernel</name>\r\n                                        <summary>Where the actual modules are stored.</summary>\r\n                                        <desc>The modules are separated into directories according to their purpose.</desc>\r\n                                        <children>\r\n                                            \r\n                                            <file><name>arch</name>\r\n                                                <summary>Kernel modules specific to the hardware architecture of the system.</summary>\r\n                                                <children></children>\r\n                                             </file>\r\n                                            \r\n                                            <file><name>crypto</name>\r\n                                                <summary>Cryptography-related modules.</summary>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>drivers</name>\r\n                                                <summary>Device drivers.</summary>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>fs</name>\r\n                                                <summary>Filesystem drivers.</summary>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>lib</name>\r\n                                                <summary>General, miscellaneous modules.</summary>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>net</name>\r\n                                                <summary>Network-related modules.</summary>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>sound</name>\r\n                                                <summary>Sound-related modules.</summary>\r\n                                                <children></children>\r\n                                            </file>\r\n                                       </children>\r\n                                     \r\n                                     </file>\r\n                                </children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- modules -->\r\n                    \r\n                    <file><name>libc.so.*</name>\r\n                        <summary>The dynamically-linked form of the C standard library. (standard, optional)</summary>\r\n                        <desc>\r\n                            Most of the basic programs in a Linux system are written in the C programming language, and almost\r\n                            all of these rely on the C standard library. They can find it here.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>ld*</name>\r\n                        <summary>Execution time loader/linker. (standard, optional)</summary>\r\n                        <desc>\r\n                            The programs by this name take an executable, gather up all its dynamic (shared) library\r\n                            dependencies, prepare the program to run, and run it.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>cpp</name>\r\n                        <summary>Link to the C preprocessor (standard, optional)</summary>\r\n                        <desc>\r\n                            \"If a C preprocessor is installed, /lib/cpp must be a link to it, for historical reasons.\" (FHS)\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file> <!-- lib -->\r\n            \r\n            <file><name>lib&lt;qual&gt;</name>\r\n                <summary>Alternate-format shared libraries. (standard, optional)</summary>\r\n                <desc>\r\n                    Some systems may support more than one kind of executable file format, which will likely need different\r\n                    kinds of libraries. For instance, a system may support both 32- and 64-bit binaries, which may need\r\n                    separate libraries.These alternate-format libraries can be placed in an appropriately suffixed /lib*\r\n                    directory (eg., lib64).\r\n                </desc>\r\n                <children></children>\r\n            </file> <!-- lib<qual> -->\r\n            \r\n            <file><name>lost+found</name>\r\n                <summary>Files recovered from a bad shutdown are stashed here. (Linux)</summary>\r\n                <desc>\r\n                    When the system is shut down without the disks being properly dismounted, the filesystem may be\r\n                    corrupted. The next time the system boots, the disk check program, fsck(8), will go through the\r\n                    disk and attempt to recover any bits of files it can find that were corrupted by the bad shutdown.\r\n                    The files will then be dumped here, in /lost+found. Every partition has or will be given its\r\n                    own lost+found. (Nguyen 1.10)\r\n                </desc>\r\n                <children></children>\r\n            </file>\r\n            \r\n            <file> <name>media</name>\r\n                <summary>Mount points for removable media. (standard)</summary>\r\n                <desc>\r\n                    Files on devices like additional hard disks, CD's, floppies, and USB devices are accessed by mounting\r\n                    them over another directory in the filesystem. In this way, the contents of the device are included\r\n                    seamlessly in the same virtual hierarchy as everything else (L\u00e5ngstedt). This directory provides a\r\n                    single, easy-to-find place to mount different devices, without cluttering up the root directory with\r\n                    them. It contains subdirectories intended to be used as mount points for the devices they are named\r\n                    after, for example, <tt>cdrom</tt>. They can be appended with digits, i.e. <tt>cdrom0</tt>, <tt>cdrom1</tt>,\r\n                    if there is more than one of the given device available, but the plain name must also exist.\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file> <name>floppy</name>\r\n                        <summary>Mount point for floppy disks. (standard, optional)</summary>\r\n                        <desc>\r\n                            If floppy disks are available on the system, there must be\r\n                            either a directory or a symlink to one with this name.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>cdrom</name>\r\n                        <summary>Mount point for CDROM's. (standard, optional)</summary>\r\n                        <desc>\r\n                            If a CDROM drive is available on the system, there must be\r\n                            either a directory or a symlink to one with this name.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>cdrecorder</name>\r\n                        <summary>Mount point for CD writers. (standard, optional)</summary>\r\n                        <desc>\r\n                            If a CD writer/burner is available on the system, there must be\r\n                            either a directory or a symlink to one with this name.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>zip</name>\r\n                        <summary>Mount point for zip drives. (standard, optional)</summary>\r\n                        <desc>\r\n                            If zip drives are available on the system, there must be either\r\n                            a directory or a symlink to one with this name.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file> <!-- media -->\r\n            \r\n            <file> <name>mnt</name>\r\n                <summary>Mount point for temporarily mounted filesystems. (standard, optional)</summary>\r\n                <desc>\r\n                    A place for the system administrator to temporarily mount a filesystem. Programs should not rely on any\r\n                    contents of this directory, nor should they use it to mount anything, but should instead use an\r\n                    appropriate temporary directory. Many distributions use /mnt the way /media is supposed to be used,\r\n                    but it's not a big issue. See also\r\n                    <a href=\"http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/mnt.html\">Nguyen 1.12</a>,\r\n                    which includes an explanation of mounting filesystems and /etc/fstab.\r\n                </desc>\r\n                <children></children>\r\n            </file>\r\n            \r\n            <file> <name>opt</name>\r\n                <summary>Add-on software packages. (standard)</summary>\r\n                <desc>\r\n                    This directory is a place for software packages to install themselves without getting mixed up with\r\n                    other software on the system. Some recommend installing all third-party applications here (Nguyen 1.13).\r\n                    Packages installed here must put their static files in a subdirectory of /opt named either after the\r\n                    package or its provider. The directory trees under these directories can mostly be arranged however the\r\n                    package provider wants them. Configuration files for the software must be placed in /etc/opt, and\r\n                    variable files, files that change regularly as the software is used, must be in /var/opt. The package\r\n                    must not put files anywhere else in the system, except files that must be in a particular location\r\n                    to work, like lock files in /var/lock and device files in /dev (FHS).\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file><name>foo</name>\r\n                        <summary>An example software package named foo.</summary>\r\n                        <desc>\r\n                            The structure of this directory is basically up to the provider of the package, but there are a few requirements on it for the sake of uniformity. It should contain everything needed for the package, including files intended to be copied into /etc/opt, /etc/var and the sysadmin-reserved directories.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>bin</name>\r\n                                <summary>Programs for users. (standard, optional)</summary>\r\n                                <desc>\r\n                                    If the package includes programs for users, they must be located here (FHS).\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>share</name>\r\n                                <summary>Data shareable between machines.</summary>\r\n                                <desc>See /usr/share for an explanation of what \"shareable\" means.</desc>\r\n                                <children>\r\n                                \r\n                                    <file><name>man</name>\r\n                                        <summary>Man pages for the package. (standard, optional)</summary>\r\n                                        <desc>\r\n                                            If the package includes man pages, they must be located here. The structure used\r\n                                            here must be the same as in /usr/share/man.\r\n                                        </desc>\r\n                                        <children></children>\r\n                                    </file>\r\n                                \r\n                                </children>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file> <!-- foo -->\r\n                    \r\n                    <file><name>baz-inc</name>\r\n                        <summary>The /opt subdirectory for an example package provider named Baz Inc..</summary>\r\n                        <desc>\r\n                            <p>The structure of provider subdirectories of /opt is up to the provider. It is recommended for\r\n                            packages to be installed to be installed in a /opt/&lt;provider&gt;/&lt;package&gt; directory.</p><p>The\r\n                            name used for this directory should be the provider's LANANA-registered name. LANANA (Linux\r\n                            Assigned Names And Numbers Authority) is an organization that makes sure that the names of,\r\n                            among other things, package providers do not collide and interfere with each other. See\r\n                            <a href=\"http://www.lanana.org/\">the Lanana website</a>.</p>\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>baz</name>\r\n                                <summary>The flagship product of Baz Inc.</summary>\r\n                                <desc>\r\n                                    It is recommended that packages provided by the provider be installed in subdirectories\r\n                                    of the provider's own subdirectory of /opt. It should contain everything needed \r\n                                    for the package, including files intended to be copied into /etc/opt, /etc/var and\r\n                                    the sysadmin-reserved directories.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file> <!-- baz-inc -->\r\n                \r\n                    <file> <name>bin</name>\r\n                        <summary>Reserved for the system administrator.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>include</name>\r\n                        <summary>Reserved for the system administrator.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>info</name>\r\n                        <summary>Reserved for the system administrator.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>lib</name>\r\n                        <summary>Reserved for the system administrator.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>man</name>\r\n                        <summary>Reserved for the system administrator.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file> <!-- opt -->\r\n            \r\n            <file> <name>proc</name>\r\n                <summary>Virtual files detailing the state of the kernel and running processes. (Linux)</summary>\r\n                <desc>\r\n                    <p>Here the concept of a virtual filesystem is taken to its logical extreme. /proc contains a variety\r\n                    of virtual files created by the operating system kernel containing information like memory usage,\r\n                    network stats, and the state of input devices and running processes. None of them actually exist\r\n                    on the disk. They are created in memory by the procfs filesystem driver. </p>\r\n                    <p>Many of the files have 0 length. The OS conjures\r\n                    their contents out of thin air if you try to read to them. A few of them are even writable\r\n                    (by root), allowing you to mess with properties and parameters of the system. For more detail\r\n                    on a particular file, look in the man page for the proc hierarchy, proc(5). Most of the\r\n                    information in this section is derived from the man page.</p><p>See also\r\n                    <a href=\"http://www.linux.com/archive/feature/126718\">Discovering the possibilities of the /proc directory</a>\r\n                    and <a href=\"http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html\">Nguyen 1.14</a>.</p>\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file><name>&lt;pid&gt;</name>\r\n                        <summary>Directory for process with PID number &lt;pid&gt;</summary>\r\n                        <desc>\r\n                            Every process running on the system has its own directory, with its PID (Process ID) as the name.\r\n                            The directory contains information about that process. For example, /proc/1 or /proc/3527 contain\r\n                            information about process 1 and 3527, respectively.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>fd</name>\r\n                                <summary>Directory containing the files opened by the process.</summary>\r\n                                <desc>\r\n                                    Specifically, it contains symlinks, named with the integer file descriptor, to the actual file in use by the program.\r\n                                </desc>\r\n                                <children>\r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>fdinfo</name>\r\n                                <summary>Contains files named as in fd, but with information about the actual file.</summary>\r\n                                <desc>\r\n                                    Only readable by the process's owner. Mostly just contains the file's\r\n                                    mode flags and read and write position.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>net</name>\r\n                                <summary>The process's network statistics.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>task</name>\r\n                                <summary>Information about the process's threads.</summary>\r\n                                <desc>\r\n                                    Every thread in the process has its own directory here, named for the thread's\r\n                                    numeric ID, or TID. The contents of these directories basically the same as\r\n                                    that of a process. In a multi-threaded process, the contents of this directory\r\n                                    are not available if the main thread has terminated.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>auxv</name>\r\n                                <summary>The contents of the ELF interpreter information passed to the process at exec time. (since kernel 2.6.0-test7)</summary>\r\n                                <desc>\r\n                                    \"This contains the contents of the ELF interpreter information passed to the\r\n                                    process at exec time. The format is one unsigned long ID plus one unsigned long\r\n                                    value for each entry. The last entry contains two zeros\"\r\n                                    (<a href=\"http://linux.die.net/man/5/proc\">proc(5)</a>). Often empty.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>cmdline</name>\r\n                                <summary>Command line by which the process was executed.</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>cwd</name>\r\n                                <summary>Symlink to current working directory of the program.</summary>\r\n                                <desc>\r\n                                    In a multi-threaded process, the contents of this link are not available if the main\r\n                                    thread has terminated (<a href=\"http://linux.die.net/man/5/proc\">proc(5)</a>).\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>environ</name>\r\n                                <summary>The values of environment variables, separated by null bytes.</summary>\r\n                                <desc>\r\n                                    \"To print out the environment of process 1, you would do: <tt>(cat /proc/1/environ; echo)\r\n                                    | tr \"\\000\" \"\\n\"</tt>.\" (<a href=\"http://linux.die.net/man/5/proc\">proc(5)</a>)\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>exe</name>\r\n                                <summary>Symlink to the executable file of the program.</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>limits</name>\r\n                                <summary>Resource limits for the process.</summary>\r\n                                <desc>Only readable by the process itself.</desc>\r\n                            </file>\r\n                            \r\n                            <file><name>maps</name>\r\n                                <summary>Memory-mapped regions belonging to the process.</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>mem</name>\r\n                                <summary>Can be used to read the process's memory pages.</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>mountinfo</name>\r\n                                <summary>Information about mount points.</summary>\r\n                                <desc>\r\n                                    Mount points in the process's mount namespace. See /proc/&lt;pid&gt;/mounts for details\r\n                                    on mount namespaces.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>mounts</name>\r\n                                <summary>Filesystems currently mounted in the process's mount namespace.</summary>\r\n                                <desc>\r\n                                    Linux supports process-specific mount namespaces, which basically makes it possible for\r\n                                    a process to have its own view of what filesystems are mounted and where. Usually,\r\n                                    processes share the same mount namespace. The file's format is the same\r\n                                    as that of /etc/fstab.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>mounstats</name>\r\n                                <summary>Statistics about filesystems mounted in the process's mount namespace.</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>oom_adj</name>\r\n                                <summary>Writing to this file adjusts the process's OOM score.</summary>\r\n                                <desc>\r\n                                    See oom_score for details. A process must be priviledged to change this file.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>oom_score</name>\r\n                                <summary>The process's likelihood of being killed in an Out-Of-Memory condition.</summary>\r\n                                <desc>\r\n                                    In conditions where there is little or no memory left, the kernel looks for processes with\r\n                                    high OOM-scores to kill to free up memory. This \"score\" starts at 0 and is adjusted by the\r\n                                    kernel based on its CPU and resource consumption, among other factors. See proc(5) on your\r\n                                    system for valid values.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>personality</name>\r\n                                <summary>The process's execution personality, or exec_domain.</summary>\r\n                                <desc>See /proc/execdomains.</desc>\r\n                            </file>\r\n                            \r\n                            <file><name>root</name>\r\n                                <summary>The root of the filesystem as seen by the process.</summary>\r\n                                <desc>\r\n                                    A process can set its own root directory. This file is a symlink to the directory chosen.\r\n                                    In a multi-threaded process, the contents of this link are not available if the main\r\n                                    thread has terminated. (<a href=\"http://linux.die.net/man/5/proc\">proc(5)</a>)\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>stat</name>\r\n                                <summary>Process status information in a dense format designed for being read by programs.</summary>\r\n                                <desc>See <a href=\"http://linux.die.net/man/5/proc\">proc(5)</a> for details.</desc>\r\n                            </file>\r\n                            \r\n                            <file><name>statm</name>\r\n                                <summary>Memory usage status information.</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>status</name>\r\n                                <summary>Process status in a  human-digestible format.</summary>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file><!-- /proc/<pid> -->\r\n                    \r\n                    <file><name>apm</name>\r\n                        <summary>Advanced Power Management info.</summary>\r\n                        <desc>Only when CONFIG_APM is defined when the kernel is compiled.</desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>bus</name>\r\n                        <summary>Contains a subdirectory for each bus type.</summary>\r\n                        <children>\r\n                            \r\n                            <file><name>pci</name>\r\n                                <summary>Information about PCI busses, devices, and drivers.</summary>\r\n                                <children>\r\n                                \r\n                                    <file><name>devices</name>\r\n                                        <summary>PCI devices known to the system.</summary>\r\n                                        <desc>They can be accessed through the commands lspci(8) and setpci(8).</desc>\r\n                                    </file>\r\n                                \r\n                                </children>\r\n                             </file>\r\n                            \r\n                            <file><name>usb</name>\r\n                                <summary>USB stuff.</summary>\r\n                                <desc>\r\n                                    Where the usbfs filesystem is mounted. See <tt>Documentation/usb/proc_usb_info.txt</tt>\r\n                                    in your kernel source, probably in <tt>/usr/src/linux</tt>.\r\n                                </desc>\r\n                                <children>\r\n                                \r\n                                    <file><name>devices</name>\r\n                                        <summary>Information about USB devices connected to the system.</summary>\r\n                                        <desc>\r\n                                            This is a text file, but rather cryptic. See <tt>Documentation/usb/proc_usb_info.txt</tt>\r\n                                            in your kernel source for details of the format.\r\n                                        </desc>\r\n                                    </file>\r\n                                \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>pccard</name>\r\n                                <summary>PCMCIA devices.</summary>\r\n                                <desc>\r\n                                    Only when CONFIG_PCMCIA is defined at compilation time.\r\n                                </desc>\r\n                                <children>\r\n                                \r\n                                    <file><name>drivers</name>\r\n                                        <summary>PCMCIA drivers.</summary>\r\n                                    </file>\r\n                                \r\n                               </children>\r\n                            </file>\r\n                            \r\n                            <file><name>input</name>\r\n                                <summary>Input devices.</summary>\r\n                                <children>\r\n                                \r\n                                    <file><name>devices</name>\r\n                                        <summary>Input devices.</summary>\r\n                                        <desc>\r\n                                            Includes how to find the devices listed in the sysfs tree, /sys/devices.\r\n                                        </desc>\r\n                                    </file>\r\n                                \r\n                                </children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- bus -->\r\n                    \r\n                    <file><name>driver</name>\r\n                        <summary>Information from certain drivers.</summary>\r\n                        <children>\r\n                        \r\n                            <file><name>rtc</name>\r\n                                <summary>Information about the Real-Time-Clock.</summary>\r\n                                <desc>Includes the current time and battery status.</desc>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>fs</name>\r\n                        <summary>Directory for filesystem-specific information.</summary>\r\n                        <desc>Certain filesystem drivers expose information in this directory.</desc>\r\n                        <children>\r\n                            \r\n                            <file><name>ext4</name>\r\n                                <summary>Information about the ext4 filesystem.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>xfs</name>\r\n                                <summary>Information about the XFS filesystem.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>ide</name>\r\n                        <summary>Information about IDE devices and channels, on systems that have them.</summary>\r\n                        <desc>\r\n                            Contains subdirectories for each IDE channel on the system, which contain directories for each\r\n                            IDE device on that channel. There are also symlinks directly in /proc/ide, named for their\r\n                            corresponding device in /dev, that point to the appropriate subdirectory of /proc/ide.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>ide0</name>\r\n                                <summary>Directory for IDE channel number 0.</summary>\r\n                                <children>\r\n                                \r\n                                    <file><name>hda</name>\r\n                                        <summary>Information about the IDE device hda.</summary>\r\n                                        <desc>\r\n                                            This directory, and its equivalents for other devices, contain several files that\r\n                                            describe different attributes of the devices after which they are named.\r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>net</name>\r\n                        <summary>Information regarding networking.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>scsi</name>\r\n                        <summary>Information about SCSI devices.</summary>\r\n                        <children>\r\n                        \r\n                            <file><name>scsi</name>\r\n                                <summary>List of SCSI devices known to the kernel at the moment.</summary>\r\n                            </file>\r\n                        \r\n                            <file><name>&lt;driver-name&gt;</name>\r\n                                <summary>Information specific to the SCSI driver &lt;driver-name&gt;</summary>\r\n                                <children></children>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>self</name>\r\n                        <summary>Symlink the process directory of the process reading the file.</summary>\r\n                        <desc>\r\n                            A shortcut for a process looking for its own information. If the process with PID 42 looks at\r\n                            this file, it will point to <tt>/proc/42</tt>. Note that this means it will point to a different folder\r\n                            every time a command like <tt>ls</tt> or <tt>file</tt> is used to inspect it, unless the command is\r\n                            built into the shell.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>sys</name>\r\n                        <summary>Files pertaining to kernel variables.</summary>\r\n                        <desc>\r\n                            This directory contains files that represent variables in the kernel.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>abi</name>\r\n                                <summary>Application binary information.</summary>\r\n                                <desc>\r\n                                    Info about how to construct different execution personalities. Not present on some systems. See Documentation/sysctl/abi.txt in your kernel source.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>debug</name>\r\n                                <summary>Debugging information from the kernel.</summary>\r\n                                <desc>May be empty.</desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>dev</name>\r\n                                <summary>Device-specific information. May be empty.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>fs</name>\r\n                                <summary>Configuration for the current filesystem driver(s), as the kernel relates to it.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>kernel</name>\r\n                                <summary>General kernel configuration parameters.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>net</name>\r\n                                <summary>Networking info and configuration.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- sys -->\r\n                    \r\n                    <file><name>cmdline</name>\r\n                        <summary>Contains the boot parameters to the kernel.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>cpuinfo</name>\r\n                        <summary>Information about the CPU(s) on the machine.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>config.gz</name>\r\n                        <summary>Kernel compilation configuration file in gzipped form.</summary>\r\n                        <desc>\r\n                            If the kernel was compiled with the CONFIG_IKCONFIG_PROC option, the configuration file used\r\n                            for compiling the kernel is kept and exposed here in gzipped format. It can be read with\r\n                            zcat, zless, or a similar program that reads gzip files.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>devices</name>\r\n                        <summary>List of currently configured devices.</summary>\r\n                        <desc>\r\n                            Actually, it's two lists. The devices listed in this file are broken into two sections:\r\n                            character devices and block devices, or buffered devices. Character devices immediately\r\n                            pass all input through, while block devices use a chunk of memory to store writes before\r\n                            doing them all at once, which helps with efficiency in some cases. Block devices can\r\n                            also send and receive information in fixed-size chunks. For each device, /dev/devices\r\n                            lists the device's major number, which identifies the driver for the device, and its\r\n                            name. It does not include devices whose kernel modules are not loaded.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>iostat</name>\r\n                        <summary>Disk I/O statistics.</summary>\r\n                        <desc>\r\n                            Try the <tt>iostat</tt> command to get some information about disk statistics, among other things.\r\n                            Look at Documentation/iostats.txt in the kernel source tree to get an idea of what all\r\n                            the obscure numbers mean (the kernel source is probably in /usr/src/linux).\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>dma</name>\r\n                        <summary>\"This is a list of the registered ISA DMA (direct memory access) channels in use.\" (proc(5))</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>execdomains</name>\r\n                        <summary>List of supported ABI personalities.</summary>\r\n                        <desc>\r\n                            Linux supports the setting of different execution domains, or personalities, for a process,\r\n                            for example to emulate the behavior of another Unix or Unix-like system.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>fb</name>\r\n                        <summary>Frame-buffer information.</summary>\r\n                        <desc>When CONFIG_FB is defined when the kernel is compiled.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>filesystems</name>\r\n                        <summary>List of filesystems compiled into the kernel.</summary>\r\n                        <desc>\r\n                            That is, a list of filesystem drivers compiled into the kernel, or whose kernel modules\r\n                            are loaded. The presence of <tt>nodev</tt> indicates that the filesystem doesn't need a\r\n                            block device to be mounted. In other words, it is at least capable of being a completely\r\n                            virtual filesystem. Among other uses, the mount command may cycle through this file\r\n                            trying different filesystems when it can't figure out which filesystem driver to use\r\n                            when mounting a volume (proc(5)).\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>interrupts</name>\r\n                        <summary>The number of interrupts per CPU per I/O device.</summary>\r\n                        <desc>See proc(5) for more.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>iomem</name>\r\n                        <summary>I/O memory map, since Linux 2.4.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>ioports</name>\r\n                        <summary>\"This is a list of currently registered Input-Output port regions that are in use.\"</summary>\r\n                        <desc>proc(5).</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>kallsyms</name>\r\n                        <summary>Symbols (names) exported by the kernel for loadable kernel modules to use.</summary>\r\n                        <desc>Since Linux 2.5.71. Before this, there was a similar file named ksyms.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>kcore</name>\r\n                        <summary>Physical memory of the system in ELF core-dump format.</summary>\r\n                        <desc>\r\n                            The length of the file is the size of the physical memory plus 4 KB.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>kmsg</name>\r\n                        <summary>Kernel messages.</summary>\r\n                        <desc>\r\n                            A process with super-user (root) privileges can read this file. Said process must make sure\r\n                            that is the only process reading it at the time. Kernel messages can also be read by the\r\n                            dmesg(1) command.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>loadavg</name>\r\n                        <summary>Average CPU load.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>locks</name>\r\n                        <summary>Current file locks and leases.</summary>\r\n                        <desc>See /var/lock for a discussion of file locks.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>mdstat</name>\r\n                        <summary>Information about RAID devices.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>meminfo</name>\r\n                        <summary>Information about memory usage in the system.</summary>\r\n                        <desc>\r\n                            The MemTotal entry represents the total physical memory on the system. MemFree is the free\r\n                            physical memory.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>Filesystems mounted on the system.</name>\r\n                        <summary>Filesystems mounted on the system.</summary>\r\n                        <desc>\r\n                            Before Linux 2.4.19, this was a list of all filesystems mounted. But with the introduction of\r\n                            per-process mount namespaces in kernel version 2.4.19, this file became a symlink to self/mounts.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>partitions</name>\r\n                        <summary>Partition info.</summary>\r\n                        <desc>\r\n                            Includes the major and minor numbers of each partion and the number of blocks they contain.\r\n                            The major number of a device identifies the device driver, while the minor number distinguishes\r\n                            individual devices (Mohr).\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>pci</name>\r\n                        <summary>Deprecated interface to PCI bus information. Look in /proc/bus/pci.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>profile</name>\r\n                        <summary>Simple performance profiling information from the kernel.</summary>\r\n                        <desc>\r\n                            When the kernel is booted with profiling enabled (profile=2 for example), then this file\r\n                            contains information about how much time different functions in the kernel are taking.\r\n                            It must be read by the program readprofile.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>swaps</name>\r\n                        <summary>Description of swap space available to the system.</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>stat</name>\r\n                        <summary>Kernel/System statistics.</summary>\r\n                        <desc>Varies with hardware architecture. See proc(5) for details.</desc>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file><!-- proc -->\r\n            \r\n            <file> <name>root</name>\r\n                <summary>Home directory for the superuser, or root. (standard, optional)</summary>\r\n                <desc>\r\n                    Can contain the same stuff as any other user's home directory. In practice, it probably won't\r\n                    and shouldn't contain that much; no one should be using the root account for daily work.\r\n                    It should only be for system administration when absolutely necessary, and this doesn't\r\n                    require a lot of personal files.\r\n                </desc>\r\n                <children>\r\n                </children>\r\n            </file>\r\n            \r\n            <file> <name>sbin</name>\r\n                <summary>Programs and scripts for use by the system administrator. (standard)</summary>\r\n                <desc>\r\n                    The name 'sbin', wherever it appears, indicates programs intended for system administration purposes,\r\n                    or intended for root only. In /sbin are essential system programs for booting, restoring,\r\n                    or repairing the system. Includes those for making filesystems.\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file><name>fastboot</name>\r\n                        <summary>Reboots the system without checking the disks. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>fasthalt</name>\r\n                        <summary>Halt the system without checking the disks. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>fdisk</name>\r\n                        <summary>Disk partition editor. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>fsck</name>\r\n                        <summary>Checks and repairs filesystems. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>fsck.*</name>\r\n                        <summary>Filesystem repairer for a specific filesystem.  (standard, optional)</summary>\r\n                        <desc>For example, fsck.reiserfs or fsck.ext2.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>getty</name>\r\n                        <summary>Short for Get TTY. (standard, optional)</summary>\r\n                        <desc>\r\n                            Program that grabs a tty port, a username and password and logs the user in. On Linux,\r\n                            you're likely to see agetty, which is just an alternate implementation of basically\r\n                            the same thing. (getty(1))\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>halt</name>\r\n                        <summary>Stops, or halts, the system. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>ifconfig</name>\r\n                        <summary>Configures a network interface. (standard, optional)</summary>\r\n                        <desc>\r\n                            Also displays the properties of currently configured network interfaces.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>init</name>\r\n                        <summary>The init process's executable. (standard, optional)</summary>\r\n                        <desc>\r\n                            This is the first process that the kernel runs after it loads everything. See /etc/inittab.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>mkfs</name>\r\n                        <summary>Makes a filesystem on a particular disk or partition. (standard, optional)</summary>\r\n                        <desc>\r\n                            Creates the data on the disk necessary for a filesystem driver to operate on it.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>mkfs.*</name>\r\n                        <summary>Filesystem-creation commands for specific filesystems. (standard, optional)</summary>\r\n                        <desc>For example, mkfs.ext2 or mkfs.ntfs.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>mkswap</name>\r\n                        <summary>Prepares a partition or file to be used as memory swap space. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>reboot</name>\r\n                        <summary>Reboots the system. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>route</name>\r\n                        <summary>Shows or modifies the IP routing table. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>swapon</name>\r\n                        <summary>Starts using a file or partition as memory swap space. (standard, optional)</summary>\r\n                        <desc>The file or partition must first have been prepared with mkswap.</desc>\r\n                    </file>\r\n                    \r\n                    <file><name>swapoff</name>\r\n                        <summary>Stops using a file or partition as swap space. (standard, optional)</summary>\r\n                    </file>\r\n                    \r\n                    <file><name>update</name>\r\n                        <summary>\"Daemon to periodically flush filesystem buffers\". (standard, optional)\"</summary>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file> <!-- sbin -->\r\n            \r\n            <file><name>srv</name>\r\n                <summary>Information \"served\" by this system. (standard)</summary>\r\n                <desc>\r\n                    The structure of this directory is up to the sysadmin. Programs should not rely on any\r\n                    particular structure or data being here. It simply exists as the default location for data\r\n                    that the system serves. This is likely to be files for the internet, or a local intranet.\r\n                </desc>\r\n                <children></children>\r\n            </file>\r\n            \r\n            <file><name>sys</name>\r\n                <summary>On Linux, a virtual dir of virtual system files, like proc.</summary>\r\n                <desc>\r\n                    <p>Though the name /sys has had other meanings on other systems, in Linux, since kernel 2.6, it\r\n                    is a directory of virtual files, driven by the sysfs filesystem driver, which gives information about\r\n                    hardware drivers and the kernel. There isn't really a firm line between the functionality of /proc\r\n                    and /sys. /proc was supposed to just have process information, but then spread out into device and\r\n                    kernel status; /sys was later originated to specialize in those things (Mochel). So there's some overlap.</p>\r\n                    <p>Kernel objects, that is, loadable kernel modules, are represented in sysfs as directories, with their\r\n                    attributes as files. Sometimes these files are writable by root, allowing the administrator to tune the\r\n                    system. For clarification on the nature of a kernel object, see the documentation files in the Linux\r\n                    kernel source: Documentation/kobject.txt and Documentation/filesystems/sysfs.txt (the kernel source\r\n                    is probably in /usr/src/linux/)</p>\r\n                </desc>\r\n                <children>\r\n                    \r\n                    <file><name>block</name>\r\n                        <summary>Information about block devices.</summary>\r\n                        <desc>\r\n                            Contains a directory, or rather a symlink to a directory for each block device discovered on\r\n                            the system (see /dev/block for the definition of a block device). The symlinks are named with\r\n                            the same name as the corresponding device in /dev, and point to the devices entry in the\r\n                            global device tree, /sys/devices. (Mochel \u00a73.1)\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>bus</name>\r\n                        <summary>Information about physical busses.</summary>\r\n                        <desc>\r\n                            Contains subdirectories for each physical bus type on the system. In each of these directories,\r\n                            there are directories <tt>devices</tt> and<tt>drivers</tt>. Every bus type has roughly the same\r\n                            organization (Mochel \u00a73.2).\r\n                        </desc>\r\n                        <children>\r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>class</name>\r\n                        <summary>Devices organized by class.</summary>\r\n                        <desc>\r\n                            Here are directories for each class of device, or each functional type of device. In each of\r\n                            these class directories are symlinks to entries in the global device tree, /sys/devices,\r\n                            containing information about each device (Mochel \u00a73.3). Here is listed just a sampling\r\n                            of the device classes likely to be on your system.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>graphics</name>\r\n                                <summary>Graphics devices.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>net</name>\r\n                                <summary>Network devices.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>input</name>\r\n                                <summary>User input devices.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>tty</name>\r\n                                <summary>TTY devices.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- class -->\r\n                    \r\n                    <file><name>dev</name>\r\n                        <summary>Devices organized based on whether they are block or character devices.</summary>\r\n                        <desc>\r\n                            There are two directories here, <tt>block</tt> and <tt>char</tt>. These directories contain symlinks with\r\n                            names of the format &lt;major-number&gt;:&lt;minor-number&gt;, with the major and minor numbers of the\r\n                            device. The symlinks point to the device's entry in the global device tree, /sys/devices\r\n                            (Mochel \u00a73.4). The major number of a device identifies the device driver, while the\r\n                            minor number distinguishes individual devices (Mohr).\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>block</name>\r\n                                <summary>Block devices, named by major and minor numbers.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>char</name>\r\n                                <summary>Character devices, named by major and minor numbers.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>devices</name>\r\n                        <summary>The global device hierarchy.</summary>\r\n                        <desc>\r\n                            This directory contains all devices on the system, organized according to their actual, physical dependencies, with a few exceptions in devices that are deeply integral to the system, like CPU's or certain legacy x86 devices (Mochel sec 3.4).\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>firmware</name>\r\n                        <summary>Interfaces to firmware objects and attributes.</summary>\r\n                        <desc>\r\n                            Contains directories that contain information and writable attributes\r\n                            for firmware objects and properties (Mochel \u00a73.5).\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>fs</name>\r\n                        <summary>Information about filesystem drivers.</summary>\r\n                        <desc>Some filesystem drivers export information to their own directory here.</desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>kernel</name>\r\n                        <summary>Information from the kernel itself.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>module</name>\r\n                        <summary>Info about each loaded kernel module.</summary>\r\n                        <desc>\r\n                            This directory contains a directory for every module loaded by the kernel. These directories\r\n                            may contain information about the module and how many devices are using it, and attributes\r\n                            for tuning the module. (Mochel \u00a73.6)\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>power</name>\r\n                        <summary>Power management.</summary>\r\n                        <desc>Attributes relating to power management (Mochel \u00a73.7).</desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file><!-- sys -->\r\n            \r\n            <file> <name>tmp</name>\r\n                <summary>Temporary files. (standard)</summary>\r\n                <desc>\r\n                    Many programs need some place to stash files for various purposes. This is the official place\r\n                    to put them. Programs should not rely on anything remaining here between boots. Many systems\r\n                    delete everything here on every boot, and this is the official recommendation of the FHS.\r\n                </desc>\r\n                <children>\r\n                </children>\r\n            </file>\r\n            \r\n            <file> <name>usr</name>\r\n                <summary>Shareable stuff for users. (standard)</summary>\r\n                <desc>\r\n                    <p>This is read-only data, intended to be shareable between FHS-compliant systems. It's the location\r\n                    of most user programs. Sometimes, it is put on a separate filesystem which is mounted read-only.\r\n                    Note that this is not the place for a large software package to make its own directory. That's\r\n                    what /opt is for. (FHS)</p><p>On software installation directories: Things are designed so that\r\n                    the location in which a piece of software is installed can be described by a single path, commonly\r\n                    called its prefix. For instance, Python may be installed with a prefix of /usr, in which case its\r\n                    binary goes in /usr/bin, include files for its C API go in /usr/include, and so on. This is why\r\n                    there is that recurring, recursive bin/sbin/lib/include structure. Any directory can potentially\r\n                    be used as a prefix. You could use ~/myprograms as a prefix for installing a program just in your\r\n                    user account, or a directory in opt, like /opt/newprogram.</p>\r\n                </desc>\r\n                <children>\r\n                \r\n                    <file><name>bin</name>\r\n                        <summary>User Programs. (standard)</summary>\r\n                        <desc>\r\n                            <p>The main source of programs used by users, beside the very basic ones like ls and cat in\r\n                            /bin (FHS). Editors, web browsers, media players, mail readers, development tools, and others\r\n                            live here.</p><p>The locations of several scripting languages are listed here. Scripts that\r\n                            use the <a href=\"http://en.wikipedia.org/wiki/Shebang_%28Unix%29\">shebang syntax</a>, ie.\r\n                            <tt>#!/usr/bin/interpreter</tt> on the first line to run themselves need to be able to\r\n                            find their interpreter on various systems. So the FHS dictates that if these languages\r\n                            are present, their interpreters must be accessible from /usr/bin, so that their script\r\n                            files can reliably find them there.</p>\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>X11</name>\r\n                                <summary>X11-related programs. (standard, optional)</summary>\r\n                                <desc>Must be a symlink to /usr/X11R6/bin, if the latter exists (FHS). See /usr/X11R6.</desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>perl</name>\r\n                                <summary>The Perl programming language interpreter. (standard, optional subystem)</summary>\r\n                                <desc>\r\n                                    See the Perl homepage: <a href=\"http://www.perl.org/\">http://www.perl.org/</a>.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>python</name>\r\n                                <summary>The Python programming language interpreter. (standard, optional subystem)</summary>\r\n                                <desc>\r\n                                    See the Python homepage: <a href=\"http://www.python.org/\">http://www.python.org/</a>\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>tclsh</name>\r\n                                <summary>A simple shell including a Tcl interpreter. (standard, optional subystem)</summary>\r\n                                <desc>\r\n                                    An interactive shell for the Tcl programming language.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>wish</name>\r\n                                <summary>Tcl/Tk windowing shell. (standard, optional subystem)</summary>\r\n                                <desc>\r\n                                    Allows a user to write Tcl scripts that create graphical windows, or even to run\r\n                                    Tcl/Tk commands interactively.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>expect</name>\r\n                                <summary>Automates the running of interactive programs. (standard, optional subystem)</summary>\r\n                                <desc>\r\n                                    This program \"talks\" to programs, giving it input according to a script. Basically,\r\n                                    it automates the running of interactive programs that might otherwise be tedious to\r\n                                    use. (expect(1))\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- bin -->\r\n                    \r\n                    <file> <name>include</name>\r\n                        <summary>Include files for C/C++ programs. (standard)</summary>\r\n                        <desc>\r\n                            Programs or libraries can create directories here in which to store their include files.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>X11</name>\r\n                                <summary>Include files for C/C++ programs and the X11 window system. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Must be a symlink to /usr/X11R6/include/X11, if the latter exists (FHS). See /usr/X11R6.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>games</name>\r\n                        <summary>Game binaries. (standard, optional)</summary>\r\n                        <desc>Games and educational programs.</desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>info</name>\r\n                        <summary>Files for the GNU Info program.</summary>\r\n                        <desc>See /usr/share/info.</desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>lib</name>\r\n                        <summary>Libraries and other architecture-dependent data. (standard)</summary>\r\n                        <desc>\r\n                            This directory contains mostly dynamic and shared libraries, but it can also contain internal\r\n                            binaries, or other data dependent on the machine the program is running on. Programs can\r\n                            create directories here to install their data in. Architecture-independent data should go\r\n                            in /usr/share. If a program uses a subdirectory, all of its architecture-dependent data\r\n                            must be placed there (FHS). Internal binaries are sometimes placed in /usr/libexec instead.\r\n                            See /usr/libexec.\r\n                        </desc>\r\n                        <children>\r\n                        \r\n                            <file><name>X11</name>\r\n                                <summary>Libraries for the X11 window system. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Must be a symlink to /usr/X11R6/lib/X11, if the latter exists (FHS). See /usr/X11R6.\r\n                                </desc>\r\n                            </file>\r\n                        \r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file><name>lib&lt;qual&gt;</name>\r\n                        <summary>Alternate-format shared libraries.</summary>\r\n                        <desc>See /lib&lt;qual&gt; for examples.</desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>libexec</name>\r\n                        <summary>\"Libraries\" that are actually programs. (Linux)</summary>\r\n                        <desc>\r\n                            Some programs employ small helper programs. These have been placed in both bin and lib, but\r\n                            this directory is used instead in some distributions.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>local</name>\r\n                        <summary>Location for \"locally installed\" programs. (standard)</summary>\r\n                        <desc>\r\n                            <p>This directory is for \"local\" or non-essential programs, as opposed to standard programs\r\n                            that might be shared among many computers, or the essential programs that must be there at\r\n                            every boot. It should be empty after the initial installation of the OS and its packages.\r\n                            Programs installed after that should probably be installed here.</p><p>Among other concerns,\r\n                            this directory is designed to be backed up in its entirety to be able to completely restore a\r\n                            given system's local software. It should be safe from being overwritten when\r\n                            the system is updated.</p>\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>bin</name>\r\n                                <summary>Local programs and scripts. (standard)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>etc</name>\r\n                                <summary>Configuration for local programs. (standard)</summary>\r\n                                <desc>\r\n                                    Since /usr/local is designed to be backed up in its entirety, its configuration all\r\n                                    needs to be in one place. Thus, /usr/local gets its own etc configuration directory.\r\n                                    It may instead be a symlink to /etc/local, if the sysadmin prefers all configuration\r\n                                    to be in one place.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>games</name>\r\n                                <summary>Local games or educational programs. (standard)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>include</name>\r\n                                <summary>C/C++ include files for local programs. (standard)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>info</name>\r\n                                <summary>Files for the GNU Info system.</summary>\r\n                                <desc>Info pages for locally installed programs. See /usr/share/info.</desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>lib</name>\r\n                                <summary>Libraries for local programs. (standard)</summary>\r\n                                <desc>See /usr/lib.</desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>lib&lt;qual&gt;</name>\r\n                                <summary>Alternate-format libraries.</summary>\r\n                                <desc>\r\n                                    If any /lib&lt;qual&gt; or /usr/lib&lt;qual&gt; directories exist, then equivalent\r\n                                    directories must exist in /usr/local.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>man</name>\r\n                                <summary>Manual pages. (standard)</summary>\r\n                                <desc>See /usr/local/share/man for details.</desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>sbin</name>\r\n                                <summary>Non-essential locally installed system binaries. (standard)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file> <name>share</name>\r\n                                <summary>Architecture-independent files for local programs.</summary>\r\n                                <desc>See /usr/share for what this usually entails.</desc>\r\n                                <children>\r\n                                \r\n                                    <file><name>man</name>\r\n                                        <summary>Man pages for locally installed programs.</summary>\r\n                                        <desc>\r\n                                            This and /usr/local/man must be synonymous; one must be a hard link or symlink\r\n                                            to the other. See also /usr/share/man, for the way man pages must be organized.\r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>src</name>\r\n                                <summary>Source code for local programs. (standard)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file><!-- local -->\r\n                    \r\n                    <file><name>man</name>\r\n                        <summary>Manual pages. (standard)</summary>\r\n                        <desc>\r\n                            This and /usr/share/man must be synonymous; one must be a symlink to the other (FHS). See\r\n                            /usr/share/man for the way man pages must be organized.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file> <name>sbin</name>\r\n                        <summary>System binaries. (standard)</summary>\r\n                        <desc>\r\n                            Non-essential programs for system administration.\r\n                        </desc>\r\n                        <children>\r\n                        </children>\r\n                    </file>\r\n                    \r\n                    <file> <name>share</name>\r\n                        <summary>Architecture-independent, or shareable, files. (standard)</summary>\r\n                        <desc>\r\n                            Here is the standard location for read-only, architecture-independent files. By\r\n                            \"architecture-independent\" is meant files that can be used on computers with different kinds\r\n                            of hardware. This typically includes things like documentation and data files. A program\r\n                            with static data it wants to store should make a directory for it here.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file> <name>dict</name>\r\n                                <summary>Word lists. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Usually, the only file here is <tt>words</tt>. But any word lists in the system must be here (FHS).\r\n                                </desc>\r\n                                <children>\r\n                                    \r\n                                    <file><name>words</name>\r\n                                        <summary>List of words in English. (standard, optional)</summary>\r\n                                        <desc>\r\n                                            Can use either American or British spelling. Installations that must support both\r\n                                            can have files <tt>american-english</tt> and <tt>british-english</tt> and symlink\r\n                                            <tt>words</tt> to one or the other.\r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>danish</name>\r\n                                        <summary>List of words in Danish.</summary>\r\n                                        <desc>\r\n                                            Word lists for other languages, Danish for example, are also placed in\r\n                                            /usr/share/dict, named with their name in English, lowercased. \r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>doc</name>\r\n                                <summary>Documentation for programs in /usr. (standard, optional)</summary>\r\n                                <desc>\r\n                                    This documentation be more in-depth than that in man-pages. It may be in some TeX-based\r\n                                    format, HTML, or just plain text. It is placed in a directory named after the progra\r\n                                    it pertains to.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>games</name>\r\n                                <summary>Shareable game data. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Game data stored here must be purely static, level files, for example. Things like\r\n                                    high scores should be in /var/games.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>info</name>\r\n                                <summary>Files for the GNU Info system.</summary>\r\n                                <desc>\r\n                                    Info manuals. The <a href=\"http://www.gnu.org/\">GNU project</a>  distributes much of\r\n                                    its documentation in info format, a slightly more flexible format than man pages.\r\n                                    It is used much like man; try typing <tt>info info</tt> at a terminal to find\r\n                                    information about the info reader. Of course you can also use it to read any other\r\n                                    info files installed.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>locale</name>\r\n                                <summary>Locales. (standard)</summary>\r\n                                <desc>\r\n                                    A locale is a collection of settings and translations for programs run in a certain area.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file> <name>man</name>\r\n                                <summary>The preferred place for man pages. (standard).</summary>\r\n                                <desc>\r\n                                    <p>Here is specified the way man pages must be organized wherever they are stored. Any\r\n                                    other place on the system that stores man pages must also organize them like this.</p>\r\n                                    <p>Man pages are organized into categories based on what they are about. Programs and\r\n                                    files in a Linux/Unix system are frequently referenced by their name and section number.\r\n                                    The number is the section number of the man page. The are placed in folders with their\r\n                                    section number appended to 'man', like 'man2'. They are all required, unless they would\r\n                                    be empty. When there are man pages in multiple sections with the same name, they can be\r\n                                    viewed by adding the section number to the <tt>man</tt> command, like this: <tt>man 5 fstab</tt>\r\n                                    </p><p>This and /usr/man must be synonymous; one must be a hard link or symlink\r\n                                    to the other. See also /var/cache/man.</p>\r\n                                </desc>\r\n                                <children>\r\n                                    \r\n                                    <file><name>&lt;locale&gt;</name>\r\n                                        <summary>Man pages for a particular locale. (standard)</summary>\r\n                                        <desc>\r\n                                            Man pages for the locale &lt;locale&gt;. Here, they are divided into categories. \r\n                                            re-formatted man pages may be stored here, in the cat&lt;section&gt; directories.\r\n                                            See /var/cache/man for details on the pre-formatting of man pages.\r\n                                        </desc>\r\n                                        <children>\r\n                                            \r\n                                            <file><name>man1</name>\r\n                                                <summary>Man pages for user programs. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    Most man pages you'll use are here, describing programs you use in your\r\n                                                    daily work with the system.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man2</name>\r\n                                                <summary>Man pages for system calls. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    System calls are operations performed by programs, or rather requests\r\n                                                    made by programs for the kernel to perform an operation. They are\r\n                                                    documented here. For the most part, only programmers will be interested\r\n                                                    in these.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man3</name>\r\n                                                <summary>Man pages for library calls. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    Documentation for functions in libraries. Again, programmers are usually\r\n                                                    the only people interested.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man4</name>\r\n                                                <summary>Man pages for special files. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    Special files, related drivers, and networking support. Usually includes\r\n                                                    the files in /dev.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man5</name>\r\n                                                <summary>Man pages for file formats. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    For instance, the file format of /etc/fstab, ELF binaries, or\r\n                                                    /proc/filesystems. Can be configuration files, output formats of\r\n                                                    programs, files in /proc or /sys, or regular data files like PNG images.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man6</name>\r\n                                                <summary>Man pages for games. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    And other similarly trivial programs, like demos or screensavers.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man7</name>\r\n                                                <summary>Miscellaneous man pages. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    Anything that doesn't fit well into the other categories. For example,\r\n                                                    troff and the other text-macro processing packages, the TCP network\r\n                                                    protocol, and the boot process may be documented here.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>man8</name>\r\n                                                <summary>System administration man pages. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    Documentation for system administration programs and related topics.\r\n                                                    For example, the mount command for mounting filesystems, disk-checking\r\n                                                    programs, and boot loaders are documented in this section.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                            <file><name>cat&lt;section&gt;</name>\r\n                                                <summary>Preformatted man pages. (standard, optional)</summary>\r\n                                                <desc>\r\n                                                    Man pages normally take some time to process from their original form\r\n                                                    to a form easily read by humans. They load faster if there is a pre-processed\r\n                                                    version. These pre-formatted pages can either be stored in\r\n                                                    appropriately-numbered cat directory here or in /var/cache/man.\r\n                                                    See /var/cache/man for the details of where preformatted man pages\r\n                                                    should be stored.\r\n                                                </desc>\r\n                                                <children></children>\r\n                                            </file>\r\n                                            \r\n                                        </children>\r\n                                    </file> <!-- locale -->\r\n                                    \r\n                                </children>\r\n                            </file> <!-- man -->\r\n                            \r\n                            <file><name>nls</name>\r\n                                <summary>Message catalogs for Native language support (standard, optional)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file> <name>misc</name>\r\n                                <summary>Miscellaneous shareable files. (standard)</summary>\r\n                                <children>\r\n                                    \r\n                                    <file><name>acronyms</name>\r\n                                        <summary>Translations of common internet and other acronyms.</summary>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>ascii</name>\r\n                                        <summary>ASCII character set table. (standard, optional)</summary>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>magic</name>\r\n                                        <summary>Magic numbers for the file command. (standard, optional)</summary>\r\n                                        <desc>\r\n                                            Default list of magic numbers for the file command, which is a program that\r\n                                            attempts to guess the type of a file by looking at its contents (magic(5)).\r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>termcap</name>\r\n                                        <summary>Terminal capability database. (standard, optional)</summary>\r\n                                        <desc>\r\n                                            Obsolete method of describing the abilities of terminals connected to the\r\n                                            system (<a href=\"http://linux.die.net/man/5/termcap\">termcap(5)</a>).\r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>termcap.db</name>\r\n                                        <summary>Terminal capability database. (standard, optional)</summary>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file> <!-- misc -->\r\n                            \r\n                            <file> <name>sgml</name>\r\n                                <summary>Data for SGML applications.</summary>\r\n                                <desc>\r\n                                    May include catalogs (not the centralized ones from /etc/sgml), DTD's, entities or\r\n                                    style sheets (FHS).\r\n                                </desc>\r\n                                <children>\r\n                                    \r\n                                    <file><name>docbook</name>\r\n                                        <summary>Docbook DTD. (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>tei</name>\r\n                                        <summary>tei DTD. (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>html</name>\r\n                                        <summary>HTML DTD. (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>mathml</name>\r\n                                        <summary>mathml DTD. (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file> <!-- sgml -->\r\n                            \r\n                            <file> <name>xml</name>\r\n                                <summary>XML data. (standard, optional)</summary>\r\n                                <desc>\r\n                                    May include DTD's ordinary catalogs (not the centralized ones from /etc/xml), DTD's,\r\n                                    entities, or style sheets (FHS).\r\n                                </desc>\r\n                                <children>\r\n                                    \r\n                                    <file><name>docbook</name>\r\n                                        <summary>docbook XML DTD's. (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>xhtml</name>\r\n                                        <summary>XHTML DTD's (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                    <file><name>mathml</name>\r\n                                        <summary>MathML DTD (standard, optional)</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file> <!-- xml -->\r\n                            \r\n                            <file><name>terminfo</name>\r\n                                <summary>Directories for terminfo database (standard, optional subystem).</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>tmac</name>\r\n                                <summary>troff macros not distributed with groff (standard, optional).</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>zoneinfo</name>\r\n                                <summary>Time zone info (standard, optional).</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file><!-- share -->\r\n                    \r\n                    <file><name>src</name>\r\n                        <summary>Source code. (standard)</summary>\r\n                        <desc>\r\n                            Source code placed in this directory should only be for reference purposes, according to the FHS.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>linux</name>\r\n                                <summary>Source for the Linux kernel. (Linux)</summary>\r\n                                <desc>\r\n                                    May be a symlink to a directory with the full release name of the kernel. It's\r\n                                    important that include files used by the kernel be here instead of in /usr/include,\r\n                                    so there are no conflicts when the system administrator tries to upgrade the kernel\r\n                                    (<a href=\"http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSRCSOURCECODE2\">FHS Ch 6</a>).\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- src -->\r\n                    \r\n                    <file><name>spool</name>\r\n                        <summary>Symlink to /var/spool, for programs that still expect it to be in /usr (standard, optional)</summary>\r\n                        <desc>\r\n                            See /var/spool. Can be removed whenever sysadmin deems it is no longer required.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>locks</name>\r\n                                <summary>Symlink to /var/lock for programs that expect lock files here. (standard, optional)</summary>\r\n                                <desc>\r\n                                    /usr/spool/locks is a historical location for lock files. See /var/lock. Can be removed whenever sysadmin deems it is no longer required.\r\n                                </desc>\r\n                           </file>\r\n                           \r\n                        </children>\r\n                    </file> <!-- spool -->\r\n                    \r\n                    <file><name>tmp</name>\r\n                        <summary>Symlink to /var/tmp, for programs that expect it to be here. (standard, optional)</summary>\r\n                        <desc>\r\n                            See /var/tmp. Can be removed whenever sysadmin deems it is no longer required.\r\n                        </desc>\r\n                    </file>\r\n                    \r\n                    <file><name>X11R6</name>\r\n                        <summary>Files for the X11 window system, Release 6. (standard, optional)</summary>\r\n                        <desc>\r\n                            Here are files related to the X11 window system. This directory is an exception to the rule\r\n                            that programs should not carve out their own subdirectories in /usr. It was made based on\r\n                            historical precedent and accepted practice.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>bin</name>\r\n                                <summary>Binaries for the X11 window system.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>include</name>\r\n                                <summary>Include files for C/C++ programs that use X11.</summary>\r\n                                <children>\r\n                                    \r\n                                    <file><name>X11</name>\r\n                                        <summary>Include files for C/C++ programs that use X11.</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                            \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>lib</name>\r\n                                <summary>Libraries for the X11 Window system.</summary>\r\n                                <children>\r\n                                \r\n                                    <file><name>X11</name>\r\n                                        <summary>Libraries for the X11 Window system.</summary>\r\n                                        <children></children>\r\n                                    </file>\r\n                                \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>man</name>\r\n                                <summary>Man pages for X11R6. (standard)</summary>\r\n                                <desc>\r\n                                    Must be organized the same as in /usr/share/man.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file><!-- usr -->\r\n            \r\n            <file> <name>var</name>\r\n                <summary>Variable data for programs. (standard)</summary>\r\n                <desc>\r\n                    <p>That is, data that changes in the daily operation of the system. This includes things like lock\r\n                    files, logs, cached data, etc.. It contains a combination of shareable and non-shareable data.\r\n                    Programs generally should not put new directories in the top level of /var, unless there is a very\r\n                    good reason with system-wide implications.</p>\r\n                    <p>It is designed to be put on a separate partition,\r\n                    and to allow /usr to be a separate filesystem mounted read-only. A lot of data that once resided\r\n                    in /usr is now in /var. If it can't be put on a separate partition, the FHS recommends placing it in\r\n                    the same partition with /usr, as /usr/var, and then symlinking /var to /usr/var,\r\n                    so that programs won't know the difference.</p>\r\n                </desc>\r\n                <children>\r\n                    \r\n                    <file><name>cache</name>\r\n                        <summary>Application cached data. (standard)</summary>\r\n                        <desc>\r\n                            <p>Programs sometimes need to store data that they've calculated by some time-consuming\r\n                            process, or that for some other reason it would be advantageous to keep around. /var/cache\r\n                            is intended for this sort of data. Programs should create their own directory in /var/cache,\r\n                            not just stick files in.</p><p>The program must be able to regenerate the data if necessary;\r\n                            it must be able to tolerate the manual deletion of the files here. Also, it must remain\r\n                            valid between invocations of the program and reboots of the system; so no process-specific\r\n                            stuff. Other than that, no constraints are put on the content of this directory.</p>\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>fonts</name>\r\n                                <summary>Locally-generated fonts. (standard, optional)</summary>\r\n                                <desc>\r\n                                    \"In particular, all of the fonts which are automatically generated by mktexpk must be located in appropriately-named subdirectories of /var/cache/fonts.\" (FHS)\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>man</name>\r\n                                <summary>Locally-formatted man pages. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Sometimes it is desirable to have a place to store pre-formatted man pages. Systems that mount /usr read-write can put them in the cat&lt;section&gt; directories of /usr/share/man or simply store them alongside the originals, but when /usr is read-only, this is the place to put pre-formatted man pages. \"Given an unformatted manual page that normally appears in &lt;path&gt;/man/&lt;locale&gt;/man&lt;section&gt;, the directory to place formatted man pages in is /var/cache/man/&lt;catpath&gt;/&lt;locale&gt;/cat&lt;section&gt;, where &lt;catpath&gt; is derived from &lt;path&gt; by removing any leading 'usr' and/or trailing 'share' pathname components. (Note that the &lt;locale&gt; component may be missing.) \" See /usr/share/man/cat&lt;section&gt; and <a href=\"http://www.pathname.com/fhs/pub/fhs-2.3.html#VARCACHEMANLOCALLYFORMATTEDMANUALPAG\">the /var/cache/man entry in the FHS</a>.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>www</name>\r\n                                <summary>\"WWW proxy or cache data.\" (standard, optional)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- cache -->\r\n                    \r\n                    <file><name>lib</name>\r\n                        <summary>Variable program state information. (standard)</summary>\r\n                        <desc>\r\n                            <p>This directory is for information pertaining to the state of a program, used to preserve\r\n                            its state between invocations. An application, or group of related applications, should use\r\n                            an appropriately named subdirectory of /var/lib for their state. This is a good place for\r\n                            databases.</p>\r\n                            <p>Data here should not be logging information, spooled data (see /var/spool\r\n                            for definition), and should remain valid between reboots. This location is generally for\r\n                            system-wide applications. State data belonging to a user will usually go in their home dir.</p>\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>&lt;editor&gt;</name>\r\n                                <summary>Editor backup files and state. (standard, optional)</summary>\r\n                                <desc>\r\n                                    An editor installed on the system may create a directory named after itself here in\r\n                                    /var/lib. It usually contains saved files generated by the unexpected termination\r\n                                    of an editor (FHS). Some editors may need to put other running information here.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>&lt;pkgtool&gt;</name>\r\n                                <summary>Variable state data for the system's package manager of choice.</summary>\r\n                                <desc>\r\n                                    For example, this might contain the system-wide database of which packages are installed,\r\n                                    their dependencies and which files belong to them.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>hwclock</name>\r\n                                <summary>State for hwclock. (standard, optional).</summary>\r\n                                <desc>\r\n                                    Actually, the only thing here is adjtime, the file hwclock uses to periodically correct\r\n                                    the hardware clock.\r\n                                </desc>\r\n                                <children>\r\n                                    \r\n                                    <file><name>adjtime</name>\r\n                                        <summary>Time-adjustment file. (standard, optional)</summary>\r\n                                        <desc>\r\n                                            File used by the hwclock program to adjust the hardware clock, to correct for\r\n                                            systematic drift (hwclock(8)). It used to be /etc/adjtime, and still is on\r\n                                            many systems, but hwclock modifies this file to keep track of systematic drift,\r\n                                            so it is better placed here in the /var/lib hierarchy (FHS).\r\n                                        </desc>\r\n                                    </file>\r\n                                    \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>misc</name>\r\n                                <summary>Miscellaneous state files. (standard)</summary>\r\n                                <desc>\r\n                                    State files that, for whatever reason, don't need their own directory.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- lib -->\r\n                    \r\n                    <file><name>local</name>\r\n                        <summary>Variable data for programs in /usr/local.</summary>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>lock</name>\r\n                        <summary>Lock files. (standard)</summary>\r\n                        <desc>\r\n                            <p>Lock files are a mechanism for making sure that applications can have exclusive access\r\n                            to a file. A program that wants to lock a file writes a file in /var/lock whose name includes\r\n                            the name of the file they want to lock. Other programs check for the existence of this file\r\n                            before trying to mess with the file. Then the program that holds the lock deletes the lock\r\n                            file, and other programs can  access it.</p>\r\n                            <p>These lock files, once in places like /usr/spool/uucp or /usr/spool/locks, now should all\r\n                            be placed in /var/lock, where they can easily be found by other programs. They should be named\r\n                            like \"LCK..&lt;filename&gt;\" where &lt;filename&gt; is the name of the file to be locked. The contents of\r\n                            the file is basically the PID of the process holding the lock, according to a\r\n                            specific format (FHS).</p>\r\n                            <p>As you may have guessed, this is not a bullet-proof access-control mechanism. It\r\n                            requires cooperation between programs that want to access a given file. This cooperation\r\n                            is only possible when all programs agree on the names, locations and formats of lock files.\r\n                            FHS compliance of the system and the programs running on it help ensure this.</p>\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>log</name>\r\n                        <summary>Log files. (standard)</summary>\r\n                        <desc>\r\n                            Most log files on the system must be written either here or in a subdirectory appropriate\r\n                            to the application writing them.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>lastlog</name>\r\n                                <summary>Record of the last login of each user. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Binary file, read by command lastlog(8).\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                            <file><name>messages</name>\r\n                                <summary>System messages from syslogd. (standard, optional)</summary>\r\n                            </file>\r\n                            \r\n                            <file><name>wtmp</name>\r\n                                <summary>Record of all logins and logouts. (standard, optional)</summary>\r\n                                <desc>\r\n                                    This is a binary file. Use the last(1) command to read it. Since this is a record of\r\n                                    all logins since the file was created, it would be a good idea either to pipe it to\r\n                                    more (<tt>last | more</tt>), or redirect it to a file.\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- log -->\r\n                    \r\n                    <file> <name>opt</name>\r\n                        <summary>Variable data for software in /opt. (standard)</summary>\r\n                        <desc>\r\n                            Variable data for programs in /opt must be placed here, in a subdirectory with the same name as their subdirectory in /opt itself. The program in /opt/foo places its variable files in /var/opt/foo. As with the other /opt related directories, no structure is required of the program's or provider's subdirectory.\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>foo</name>\r\n                                <summary>Example subdirectory for a program in /opt/foo.</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- opt -->\r\n                    \r\n                    <file><name>run</name>\r\n                        <summary>Run-time variable data, only valid for this boot session. (standard)</summary>\r\n                        <desc>\r\n                            <p>This directory contains information generated by programs that is only valid for this boot\r\n                            session. This commonly includes PID files for programs that need other programs to be able to\r\n                            send signals to them. Similarly, sockets used to communicate with programs should be created here.</p>\r\n                            <p>Programs can make a subdirectory of /var/run; this is recommended for programs with more than\r\n                            one file to write. Files in this directory must be cleared (not deleted) in a manner appropriate\r\n                            for the file type during the boot process.</p>\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>utmp</name>\r\n                                <summary>Information about who is using the system at the moment. (standard, optional)</summary>\r\n                                <desc>\r\n                                    This file has a binary format (utmp(5)).\r\n                                </desc>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- run -->\r\n                    \r\n                    <file><name>spool</name>\r\n                        <summary>\"Application spool data.\" (standard)</summary>\r\n                        <desc>\r\n                            Data that is meant to be processed at some later point, by another program or user. It is\r\n                            often deleted once it has been processed. (FHS)\r\n                        </desc>\r\n                        <children>\r\n                            \r\n                            <file><name>cron</name>\r\n                                <summary>Spooled data for cron and at jobs. (standard)</summary>\r\n                                <desc>\r\n                                    Variable data used by the crond(8) and at(1) programs. These perform jobs at specific intervals or times, respectively.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>lpd</name>\r\n                                <summary>Line-printer daemon print queues. (standard, optional)</summary>\r\n                                <desc>\r\n                                    Lock files for each individual printer should be in a subdirectory\r\n                                    named after the printer, and named <tt>lock</tt>.\r\n                                </desc>\r\n                                <children>\r\n                                    \r\n                                    <file><name>lpd.lock</name>\r\n                                        <summary>The lock file for the lpd daemon. (standard)</summary>\r\n                                    </file>\r\n                                \r\n                                </children>\r\n                            </file>\r\n                            \r\n                            <file><name>rwho</name>\r\n                                <summary>\"Holds the <tt>rwhod</tt> information for other systems on the local net\" (standard, optional)</summary>\r\n                                <desc>\r\n                                    <p>The rwhod daemon (rwhod(8)) is a server that broadcasts and accepts information\r\n                                    from other computers on the local network, like uptime and users logged on. It is\r\n                                    accessed by the rwho(1) command.</p>\r\n                                    <p>\"Some BSD releases use /var/rwho for this data; given its historical location in\r\n                                    /var/spool on other systems and its approximate fit to the definition of 'spooled' data,\r\n                                    this location was deemed more appropriate.\" (FHS)</p>\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>mqueue</name>\r\n                                <summary>Queue for outgoing mail. (standard, optional)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>news</name>\r\n                                <summary>News spool. (standard, optional)</summary>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                            <file><name>uucp</name>\r\n                                <summary>Spooled stuff for UUCP. (standard, optional)</summary>\r\n                                <desc>\r\n                                    UUCP, an acronym for 'Unix to Unix CoPy,\" is a suite of programs for communicating electronically between not only Unix-based computers, but many other operating systems as well.\r\n                                </desc>\r\n                                <children></children>\r\n                            </file>\r\n                            \r\n                        </children>\r\n                    </file> <!-- spool -->\r\n                    \r\n                    <file><name>tmp</name>\r\n                        <summary>Temporary files preserved between boots. (standard)</summary>\r\n                        <desc>\r\n                            This is for temporary files that need to be preserved between system reboots (recall that\r\n                            in many cases /tmp is cleared on each boot). All that is recommended by the standard is\r\n                            that deleletions of its contents occurs less frequently than that of /tmp (FHS).\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>account</name>\r\n                        <summary>\"Process accounting logs.\" (standard, optional)</summary>\r\n                        <desc>\r\n                            \"This directory holds the current active process accounting log and the composite process\r\n                            usage data (as used in some UNIX-like systems by lastcomm and sa).\" (FHS)\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>crash</name>\r\n                        <summary>System crash dumps. (standard, optional)</summary>\r\n                        <desc>\r\n                            As of FHS 2.3 (2004), Linux did not support system crash dumps, but other FHS-compliant systems may want a place for them.\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>games</name>\r\n                        <summary>Variable data for games in /usr. (standard, optional)</summary>\r\n                        <desc>\r\n                            This had once simply been merged with /var/lib (in FHS 1.2), but separating it gives more\r\n                            flexibility in managing backups and permissions, reduces clutter in /var/lib, and \"is the\r\n                            path traditionally used by BSD\" (FHS).\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>mail</name>\r\n                        <summary>User email inboxes. (standard, optional)</summary>\r\n                        <desc>\r\n                            User mailboxes must at least be accessible through /var/mail. The FHS once specified them in\r\n                            /var/spool/mail, but most *nixes were using /var/mail anyway, so the standard just went with it.\r\n                            It can be a symink, to /var/spool/mail or whatever the sysadmin desires. (FHS)\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                    <file><name>yp</name>\r\n                        <summary>Network Information Service database files. (standard, optional)</summary>\r\n                        <desc>\r\n                            \"Variable data for the Network Information Service (NIS), formerly known as the Sun Yellow Pages\r\n                            (YP), must be placed in this directory.\" (FHS)\r\n                        </desc>\r\n                        <children></children>\r\n                    </file>\r\n                    \r\n                </children>\r\n            </file> <!-- var -->\r\n            \r\n        </children>        \r\n    </file>\r\n    \r\n    <references>\r\n        <ref>Debian Installer Team. \"Debian GNU/Linux Installation Guide\". 2008. &lt;http://www.debian.org/releases/stable/i386/index.html.en&gt;</ref>\r\n        <ref>\"Filesystem Hierarchy Standard\". Ed. Russel, Paul, Daniel Quinlain, and Christopher Yeoh. Vers. 2.3. 2004 &lt;http://www.pathname.com/fhs/pub/fhs-2.3.html&gt;</ref>\r\n        <ref>L\u00e5ngstedt, Nana. \"How to mount partitions and filesystems in Linux\". 2005. &lt;http://www.tuxfiles.org/linuxhelp/mounting.html&gt;</ref>\r\n        <ref>Mochel, Patrick. \"The sysfs Filesystem\". 2005. &lt;http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf&gt;</ref>\r\n        <ref>Mohr, James. \"Major and Minor Numbers\". 2009. &lt;http://www.linux-tutorial.info/modules.php?name=MContent&amp;pageid=94&gt;</ref>\r\n        <ref>Nguyen, Binh. \"Linux Filesystem Hierarchy\". 2004. &lt;http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/index.html&gt;</ref>\r\n        <ref>Wirzenius, Lars, et al. \"Linux System Administrator's Guide - The /dev directory\" &lt;http://linux.about.com/od/lsa_guide/a/gdelsa18.htm&gt;</ref>\r\n        <ref>Seebach, Peter. \"What you need to know to write manpages.\" 2004. &lt;http://www.linux.com/archive/feed/34212&gt;</ref>\r\n    </references>\r\n    \r\n</filesystem>"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=172800"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "183005"
            }, 
            {
              "name": "content-type", 
              "value": "text/xml"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:54 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"2cadd-489195fd7abc7\""
            }, 
            {
              "name": "expires", 
              "value": "Fri, 30 Jul 2010 03:31:54 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Tue, 15 Jun 2010 22:46:22 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:52.972106Z", 
        "time": 1866, 
        "timings": {
          "blocked": -1, 
          "connect": 66, 
          "dns": -1, 
          "receive": 1680, 
          "send": 0, 
          "wait": 119
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "text/xml,application/xml,application/xhtml+xml,*/*;q=0.1"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xsl"
        }, 
        "response": {
          "bodySize": 6511, 
          "content": {
            "compression": 0, 
            "mimeType": "text/xml", 
            "size": 6511, 
            "text": "<?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>\r\n<xsl:stylesheet version=\"2.0\" xmlns:xsl=\"http://www.w3.org/1999/XSL/Transform\">\r\n\r\n<xsl:output method=\"html\" indent=\"yes\" encoding=\"UTF-8\"/>\r\n\r\n<!-- The main template used for each file or directory (since directories are also files) -->\r\n<!-- THIS IS THE INTERESTING PART -->\r\n<xsl:template match=\"file\" name=\"dir-template\">\r\n    <xsl:param name=\"parent-path\" />     <!-- Must include trailing slash, if not empty -->\r\n    <!-- Parent path parameter allows us to calculate the absolute paths -->\r\n    <!-- absolute-name = parent-path + name + (if directory and name != '/' then add '/')\r\n    It must end with a slash it it's a directory, but not if it's a plain file -->\r\n    <xsl:variable name=\"absolute-name\">  <!-- The absolute name of the current file, all on one line to eliminate whitespace -->\r\n        <xsl:value-of select=\"$parent-path\" /><xsl:value-of select=\"name\" /><xsl:if test=\"children and name != '/'\">/</xsl:if></xsl:variable>\r\n    <!-- XHTML output -->\r\n    <div class=\"file\" >\r\n        <!-- Title/Summmary Line -->\r\n        <span class=\"summary\">\r\n            <!-- onClick attribute depends on whether current file has children... -->\r\n            <xsl:attribute name=\"onClick\">\r\n                <xsl:choose>\r\n                    <!-- if it's a director with non-empty description or children, make it expandable -->\r\n                    <xsl:when test=\"(children and desc) or children/file\">toggleDirExpansion('<xsl:value-of select=\"$absolute-name\" />')</xsl:when>\r\n                    <!-- if it's a directory with nothing in it, make sure onClick is empty -->\r\n                    <xsl:when test=\"children\"></xsl:when>\r\n                    <!-- if it's a file with non-empty desc -->\r\n                    <xsl:when test=\"desc\">toggleFileExpansion('<xsl:value-of select=\"$absolute-name\" />')</xsl:when>\r\n                </xsl:choose>\r\n            </xsl:attribute>\r\n            <!-- ...as does the original source of the image -->\r\n            <img>\r\n                <xsl:attribute name=\"src\">\r\n                    <xsl:choose>\r\n                        <!-- if it's a directory with something to expand, indicate that -->\r\n                        <xsl:when test=\"(children and desc) or children/file\">dir-closed.png</xsl:when>\r\n                        <!-- if it's a directory with nothing in it -->\r\n                        <xsl:when test=\"children\">dir-empty.png</xsl:when>\r\n                        <!-- if it's a file with a description -->\r\n                        <xsl:when test=\"desc\">file-closed.png</xsl:when>\r\n                        <!-- if it's a file with nothing in it it-->\r\n                        <xsl:otherwise>file-empty.png</xsl:otherwise>\r\n                    </xsl:choose>\r\n                </xsl:attribute>\r\n                <xsl:attribute name=\"id\"><xsl:value-of select=\"$absolute-name\" />:img</xsl:attribute>\r\n            </img>\r\n            <!-- Now just do the name and summary -->\r\n            <b><xsl:value-of select=\"name\" /></b>\r\n            (<xsl:value-of select=\"$absolute-name\" />): <xsl:value-of select=\"summary\" />\r\n        </span>\r\n        <!-- This is the collapsible part -->\r\n        <div class=\"innerbox\" style=\"display:none\"> <!--must already have explicit display property for toggleDisplay to work -->\r\n            <!-- Must have appropriate ID attribute to be collapsed -->\r\n            <xsl:attribute name=\"id\">\r\n                <xsl:value-of select=\"$absolute-name\" />:inner</xsl:attribute> <!-- Again, one line to avoid whitespace -->\r\n            <!-- Long description, if it exists -->\r\n            <xsl:if test=\"desc\">\r\n                <div class=\"description\">\r\n                    <!-- if the description does not include a p element, create one >\r\n                    <    I'm not responsible for what happens if p's and unenclosed text are mixed in a description -->\r\n                    <xsl:choose>\r\n                        <xsl:when test=\"desc/p\">\r\n                            <xsl:copy-of select=\"desc/*\"/> <!-- copy all p elements -->\r\n                        </xsl:when>\r\n                        <xsl:otherwise>\r\n                            <p><xsl:value-of select=\"desc\" /></p>\r\n                        </xsl:otherwise>\r\n                    </xsl:choose>\r\n                </div>\r\n            </xsl:if>\r\n            <!-- Recursively apply the template to the child files (assuming they exist), passing this directory as a parameter -->\r\n            <xsl:for-each select=\"children/file\">\r\n                <xsl:call-template name=\"dir-template\">\r\n                    <xsl:with-param name=\"parent-path\" select=\"$absolute-name\" />\r\n                </xsl:call-template>\r\n            </xsl:for-each>\r\n            <!-- Done with content -->\r\n        </div> <!-- class=\"innerbox\" -->\r\n    </div>     <!-- class=\"dir\" -->\r\n</xsl:template>\r\n\r\n<!-- Template for the whole document -->\r\n<xsl:template match=\"/\">\r\n    <html>\r\n    <head>\r\n        <title>Interactive Linux Filesystem Explanation</title>\r\n        <link rel=\"stylesheet\" type=\"text/css\" href=\"fhs.css\" />\r\n        <script type=\"text/javascript\" src=\"fhs.js\"></script>\r\n    </head>\r\n    <body onLoad=\"toggleDirExpansion('/')\">\r\n    \r\n    <!-- The intro and stuff -->\r\n    <div id=\"introduction\" >\r\n        <div style=\"font-size: 180%; text-align: center; width: 100%;\">Interactive Linux Filesystem Explanation</div>\r\n        <div style=\"font-size: 130%; text-align: center; width: 100%;\">Introduction</div>\r\n        <xsl:copy-of select=\"filesystem/intro\" />\r\n    </div>\r\n    \r\n    <!-- the actual filesystem -->\r\n    <div id=\"filesystem\">\r\n        <div style=\"font-size: 130%; text-align: center; width: 100%;\">Explanation</div>\r\n        <xsl:for-each select=\"filesystem/file\">\r\n            <xsl:call-template name=\"dir-template\">\r\n                <xsl:with-param name=\"parent-path\" select=\"''\" />\r\n            </xsl:call-template>\r\n        </xsl:for-each>\r\n    </div>\r\n    \r\n    <!-- MLA references -->\r\n    <div id=\"references\">\r\n        <div style=\"font-size: 150%; text-align: center; width: 100%;\">Works Cited</div>\r\n        <ul>\r\n            <xsl:for-each select=\"filesystem/references/ref\">\r\n                <li><xsl:value-of select=\".\" /></li>\r\n            </xsl:for-each>\r\n        </ul>\r\n    </div>\r\n    \r\n    <!-- copyright notice -->\r\n    <div style=\"text-align: center; width:100%; font-weight: bold; font-size: 11pt;\">\r\n        \u00a9Andrew Fleenor, 2010\r\n    </div>\r\n    \r\n    </body></html>\r\n</xsl:template>\r\n\r\n</xsl:stylesheet>"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=172800"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "6511"
            }, 
            {
              "name": "content-type", 
              "value": "text/xml"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:55 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"196f-48918578e330a\""
            }, 
            {
              "name": "expires", 
              "value": "Fri, 30 Jul 2010 03:31:55 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Tue, 15 Jun 2010 21:32:28 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:53.275921Z", 
        "time": 4065, 
        "timings": {
          "blocked": -1, 
          "connect": 104, 
          "dns": -1, 
          "receive": 3738, 
          "send": 0, 
          "wait": 222
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "text/css,*/*;q=0.1"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.css"
        }, 
        "response": {
          "bodySize": 571, 
          "content": {
            "compression": 0, 
            "mimeType": "text/css", 
            "size": 571, 
            "text": ".file{\r\n    position: relative;\r\n}\r\n\r\n.description{\r\n    display: block;\r\n    background-color: #eeeeee;\r\n    font-size: 12pt;\r\n}\r\n\r\n.summary{\r\n    display:block;\r\n    font-size: 13pt;\r\n}\r\n\r\n.innerbox{\r\n    position:relative;\r\n    margin-left: 20px;\r\n    display: none;\r\n}\r\n\r\n#introduction{\r\n    margin: 4px;\r\n    padding: 4px;\r\n    font-size: 12pt;\r\n}\r\n\r\n#filesystem{\r\n    margin: 4px;\r\n}\r\n\r\n#references{\r\n    font-size: 12pt;\r\n    line-height: 150%;\r\n}\r\n\r\nimg{\r\n    margin: 0;\r\n    border-width: 1px;\r\n}\r\n\r\np{\r\n    margin: 5px;\r\n}\r\n\r\nbody{ font-family: arial, sans; }\r\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=86400"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "571"
            }, 
            {
              "name": "content-type", 
              "value": "text/css"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:58 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"23b-48918138bebc0\""
            }, 
            {
              "name": "expires", 
              "value": "Thu, 29 Jul 2010 03:31:58 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Tue, 15 Jun 2010 21:13:27 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.355689Z", 
        "time": 89, 
        "timings": {
          "blocked": -1, 
          "connect": 0, 
          "dns": -1, 
          "receive": 0, 
          "send": 0, 
          "wait": 89
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "*/*"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.js"
        }, 
        "response": {
          "bodySize": 1774, 
          "content": {
            "compression": 0, 
            "encoding": "base64", 
            "mimeType": "application/x-javascript", 
            "size": 1774, 
            "text": "DQovL29uZSBmdW5jdGlvbiB0byBleHBhbmQgb3IgY2xvc2UgYSBkaXJlY3RvcnkgZW50cnkNCmZ1\nbmN0aW9uIHRvZ2dsZURpckV4cGFuc2lvbihiYXNlX2lkKXsNCiAgICB0b2dnbGVJbWFnZShiYXNl\nX2lkICsgJzppbWcnLCAnZGlyLWNsb3NlZC5wbmcnLCAnZGlyLW9wZW4ucG5nJykNCiAgICB0b2dn\nbGVEaXNwbGF5KGJhc2VfaWQgKyAnOmlubmVyJywgJ2Jsb2NrJykNCn0NCg0KLy9kaXR0bywgYnV0\nIGZvciBwbGFpbiBmaWxlcw0KZnVuY3Rpb24gdG9nZ2xlRmlsZUV4cGFuc2lvbihiYXNlX2lkKXsN\nCiAgICB0b2dnbGVJbWFnZShiYXNlX2lkICsgJzppbWcnLCAnZmlsZS1jbG9zZWQucG5nJywgJ2Zp\nbGUtb3Blbi5wbmcnKQ0KICAgIHRvZ2dsZURpc3BsYXkoYmFzZV9pZCArICc6aW5uZXInLCAnYmxv\nY2snKQ0KfQ0KDQovL3N3aXRjaGVzIHRoZSBzcmMgb2YgYW4gaW1hZ2UgYmV0d2VlbiB0d28gYWx0\nZXJuYXRpdmVzDQpmdW5jdGlvbiB0b2dnbGVJbWFnZShpbWdfaWQsIGltZzEsIGltZzIpew0KICAg\nIGltZyA9IGRvY3VtZW50LmdldEVsZW1lbnRCeUlkKGltZ19pZCkNCiAgICBpZihpbWcuc3JjLmVu\nZHNXaXRoKGltZzEpKXsNCiAgICAgICAgaW1nLnNyYyA9IGltZzIgDQogICAgfSBlbHNlIGlmKGlt\nZy5zcmMuZW5kc1dpdGgoaW1nMikpew0KICAgICAgICBpbWcuc3JjID0gaW1nMQ0KICAgIH0gZWxz\nZSB7DQogICAgICAgIHRocm93ICd0b2dnbGVJbWFnZTogaW52YWxpZCBpbWFnZSBzcmMoXCcnICsg\naW1nLnNyYyArICdcJywgbmVpdGhlciBcJycgKyBpbWcxICsgJ1wnIG5vciBcJycgKyBpbWcyICsg\nJ1wnJw0KICAgIH0NCn0NCg0KLy9zaW1wbGUgZnVuY3Rpb24gdGhhdCBleHBhbmRzIG9yIGNvbGxh\ncHNlcyBhbnkgZWxlbWVudA0KZnVuY3Rpb24gdG9nZ2xlRGlzcGxheShlbGVtZW50X2lkLCBkaXNw\nKXsNCiAgICBlbGVtZW50ID0gZG9jdW1lbnQuZ2V0RWxlbWVudEJ5SWQoZWxlbWVudF9pZCkNCiAg\nICBpZighZWxlbWVudCl7IC8vaWYgdGhlIGVsZW1lbnQgd2FzIG5vdCBmb3VuZA0KICAgICAgICB0\naHJvdyAoInRvZ2dsZURpc3BsYXk6IGZhaWxlZCB0byBmaW5kIGlkOiAnIiArIGVsZW1lbnRfaWQg\nKyAiJyIpDQogICAgfSBlbHNlIGlmKGVsZW1lbnQuc3R5bGUuZGlzcGxheSA9PSAnbm9uZScpew0K\nICAgICAgICBlbGVtZW50LnN0eWxlLmRpc3BsYXkgPSBkaXNwDQogICAgfSBlbHNlIHsgICAvL3Ro\naXMgaW5jbHVkZXMgZWxlbWVudHMgd2l0aCBubyBleHBsaWNpdCBkaXNwbGF5IHByb3AsIHdoaWNo\nIG1lYW5zIHlvdSBjYW4gc2VlIHRoZW0NCiAgICAgICAgZWxlbWVudC5zdHlsZS5kaXNwbGF5ID0g\nJ25vbmUnDQogICAgfQ0KfQ0KDQpmdW5jdGlvbiBoaWRlKGVsZW1lbnQpew0KICAgIGVsZW1lbnQu\nc3R5bGUuZGlzcGxheSA9ICdub25lJw0KfQ0KDQpmdW5jdGlvbiBzaG93KGVsZW1lbnQsIHByb3Ap\new0KICAgIGlmKHByb3AgPT0gJ2Jsb2NrJyB8fCBwcm9wID09ICdpbmxpbmUnKXsNCiAgICAgICAg\nZWxlbWVudC5zdHlsZS5kaXNwbGF5ID0gcHJvcA0KICAgIH0gZWxzZSB7DQogICAgICAgIHRocm93\nICdmdW5jdGlvbiBzaG93OiBpbnZhbGlkIHBhcmFtZXRlcicNCiAgICB9DQp9DQoNClN0cmluZy5w\ncm90b3R5cGUuZW5kc1dpdGggPSBmdW5jdGlvbihzdHIpDQp7DQogICAgdmFyIGxhc3RJbmRleCA9\nIHRoaXMubGFzdEluZGV4T2Yoc3RyKTsNCiAgICByZXR1cm4gdGhpcy5sZW5ndGggPj0gc3RyLmxl\nbmd0aCAmJiB0aGlzLmxhc3RJbmRleE9mKHN0cikgKyBzdHIubGVuZ3RoID09IHRoaXMubGVuZ3Ro\nDQp9DQoNCg==\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=86400"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "1774"
            }, 
            {
              "name": "content-type", 
              "value": "application/x-javascript"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"6ee-488b34af5f842\""
            }, 
            {
              "name": "expires", 
              "value": "Thu, 29 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Thu, 10 Jun 2010 20:59:05 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.359355Z", 
        "time": 112, 
        "timings": {
          "blocked": -1, 
          "connect": 0, 
          "dns": -1, 
          "receive": 4, 
          "send": 0, 
          "wait": 107
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "image/png,image/*;q=0.8,*/*;q=0.5"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/dir-closed.png"
        }, 
        "response": {
          "bodySize": 251, 
          "content": {
            "compression": 0, 
            "encoding": "base64", 
            "mimeType": "image/png", 
            "size": 251, 
            "text": "iVBORw0KGgoAAAANSUhEUgAAAA8AAAAPCAIAAAC0tAIdAAAAAXNSR0IArs4c6QAAAAlwSFlzAAAL\nEwAACxMBAJqcGAAAAAd0SU1FB9oEDRUoHCsqeIoAAAAZdEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRo\nIEdJTVBXgQ4XAAAAaElEQVQoz5WSwQ3AMAgDDQuE/aeECeiDKqqcNC33QooJtkAyEwCAiMALY4wq\nJDNJZ2ZVuDv1KH0zpVQXejBARISig5S5dShxZ6Ao54aek776j5nSCEkpLr02ncwb+GSz+efoNY+0\nbvACVp8376DuttAAAAAASUVORK5CYII=\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=259200"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "251"
            }, 
            {
              "name": "content-type", 
              "value": "image/png"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"fb-488b34ae6b605\""
            }, 
            {
              "name": "expires", 
              "value": "Sat, 31 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Thu, 10 Jun 2010 20:59:04 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.364757Z", 
        "time": 184, 
        "timings": {
          "blocked": -1, 
          "connect": 91, 
          "dns": -1, 
          "receive": 0, 
          "send": 0, 
          "wait": 92
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "image/png,image/*;q=0.8,*/*;q=0.5"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/file-closed.png"
        }, 
        "response": {
          "bodySize": 252, 
          "content": {
            "compression": 0, 
            "encoding": "base64", 
            "mimeType": "image/png", 
            "size": 252, 
            "text": "iVBORw0KGgoAAAANSUhEUgAAAA8AAAAPCAIAAAC0tAIdAAAAAXNSR0IArs4c6QAAAAlwSFlzAAAL\nEwAACxMBAJqcGAAAAAd0SU1FB9oEDRUuJ8x7NigAAAAZdEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRo\nIEdJTVBXgQ4XAAAAaUlEQVQoz42SSw7AIAgFH8Q93P+UeAK6aEMTVISVkhk/ALk7AABzThxCRN4F\nuXvBJYdjo6pXgcws0ZFZg9eUqp7u4dMxW4frhyaHO9UIoUXHv0eTu9DbOo4m99EiEp0vuNz5Gv2n\nqj+DD5h8LXdBt4lUAAAAAElFTkSuQmCC\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=259200"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "252"
            }, 
            {
              "name": "content-type", 
              "value": "image/png"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"fc-488b34b147d08\""
            }, 
            {
              "name": "expires", 
              "value": "Sat, 31 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Thu, 10 Jun 2010 20:59:07 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.368798Z", 
        "time": 206, 
        "timings": {
          "blocked": -1, 
          "connect": 103, 
          "dns": -1, 
          "receive": 0, 
          "send": 0, 
          "wait": 102
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "image/png,image/*;q=0.8,*/*;q=0.5"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/file-empty.png"
        }, 
        "response": {
          "bodySize": 273, 
          "content": {
            "compression": 0, 
            "encoding": "base64", 
            "mimeType": "image/png", 
            "size": 273, 
            "text": "iVBORw0KGgoAAAANSUhEUgAAAA8AAAAPCAIAAAC0tAIdAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A\n/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9oFHBQwCGfsR9MAAAAZdEVYdENv\nbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVBXgQ4XAAAAbElEQVQoz5WSuxEAIQgFH4w55dh/SDdaARd4\nQ6CiSCTOrh+AzAwAgN47ghCRsSAzO3CTw56o6lWg1tpE11ojmtctVY3u4eiYrcPnh04OZ6rhQor2\nf5ckd6G3dSxJ7qdFxDt/4Ebn3+aEnmbwA+7INyTfz+Z3AAAAAElFTkSuQmCC\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=259200"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "273"
            }, 
            {
              "name": "content-type", 
              "value": "image/png"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"111-488b34b23bf04\""
            }, 
            {
              "name": "expires", 
              "value": "Sat, 31 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Thu, 10 Jun 2010 20:59:08 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.382308Z", 
        "time": 287, 
        "timings": {
          "blocked": -1, 
          "connect": 90, 
          "dns": -1, 
          "receive": 0, 
          "send": 0, 
          "wait": 197
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "image/png,image/*;q=0.8,*/*;q=0.5"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/dir-empty.png"
        }, 
        "response": {
          "bodySize": 273, 
          "content": {
            "compression": 0, 
            "encoding": "base64", 
            "mimeType": "image/png", 
            "size": 273, 
            "text": "iVBORw0KGgoAAAANSUhEUgAAAA8AAAAPCAIAAAC0tAIdAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A\n/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9oFHBQwNT+EC8IAAAAZdEVYdENv\nbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVBXgQ4XAAAAbElEQVQoz5WSwRXAIAhDAwswjvsf3UYmoAf6\nfH2p2vJPHCIkiEQEAADujg1mloVEBOl671m01uiNUpsppTrRgwHC3RUVZIyxHEpkBv0jnZqak7qa\n9nrwfafc7ZgaFZ3MG/hk8fPP0e88UrrBC7kzMrHxbHvMAAAAAElFTkSuQmCC\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=259200"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "273"
            }, 
            {
              "name": "content-type", 
              "value": "image/png"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"111-488b34ae6b65f\""
            }, 
            {
              "name": "expires", 
              "value": "Sat, 31 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Thu, 10 Jun 2010 20:59:04 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.388756Z", 
        "time": 224, 
        "timings": {
          "blocked": -1, 
          "connect": 85, 
          "dns": -1, 
          "receive": 0, 
          "send": 0, 
          "wait": 139
        }
      }, 
      {
        "cache": {}, 
        "pageref": "page_0", 
        "request": {
          "bodySize": 0, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept", 
              "value": "image/png,image/*;q=0.8,*/*;q=0.5"
            }, 
            {
              "name": "accept-charset", 
              "value": "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
            }, 
            {
              "name": "accept-language", 
              "value": "en-us,en;q=0.5"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "cookie", 
              "value": "__utma=191645736.1924309581.1277516327.1278893750.1278979018.10; __utmz=191645736.1278979018.10.3.utmcsr=wiki.wireshark.org|utmccn=(referral)|utmcmd=referral|utmcct=/Development/LibpcapFileFormat; __qca=P0-1746884488-1277513743262"
            }, 
            {
              "name": "host", 
              "value": "andrewfleenor.users.sourceforge.net"
            }, 
            {
              "name": "keep-alive", 
              "value": "300"
            }, 
            {
              "name": "referer", 
              "value": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
            }, 
            {
              "name": "user-agent", 
              "value": "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 ( .NET CLR 3.5.30729; .NET4.0E)"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "method": "GET", 
          "queryString": [], 
          "url": "http://andrewfleenor.users.sourceforge.net/fhs/dir-open.png"
        }, 
        "response": {
          "bodySize": 232, 
          "content": {
            "compression": 0, 
            "encoding": "base64", 
            "mimeType": "image/png", 
            "size": 232, 
            "text": "iVBORw0KGgoAAAANSUhEUgAAAA8AAAAPCAIAAAC0tAIdAAAAAXNSR0IArs4c6QAAAAlwSFlzAAAL\nEwAACxMBAJqcGAAAAAd0SU1FB9oEDRUpAVE3JRIAAAAZdEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRo\nIEdJTVBXgQ4XAAAAVUlEQVQoz7WSsQ3AQAgDzSs97D+lmcApiFJEyguKdwPFgSywSQIAIDPxI3ev\nxiRtuM/MwkRGsk/Pdl9VImLPPRb6TkjOnMzpjpliTl5wvRk48PlRBm/H/CZLf1D4lAAAAABJRU5E\nrkJggg==\n"
          }, 
          "cookies": [], 
          "headers": [
            {
              "name": "accept-ranges", 
              "value": "bytes"
            }, 
            {
              "name": "cache-control", 
              "value": "max-age=259200"
            }, 
            {
              "name": "connection", 
              "value": "keep-alive"
            }, 
            {
              "name": "content-length", 
              "value": "232"
            }, 
            {
              "name": "content-type", 
              "value": "image/png"
            }, 
            {
              "name": "date", 
              "value": "Wed, 28 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "etag", 
              "value": "\"e8-488b34ae6b63a\""
            }, 
            {
              "name": "expires", 
              "value": "Sat, 31 Jul 2010 03:31:59 GMT"
            }, 
            {
              "name": "last-modified", 
              "value": "Thu, 10 Jun 2010 20:59:04 GMT"
            }, 
            {
              "name": "server", 
              "value": "nginx/0.7.63"
            }
          ], 
          "headersSize": -1, 
          "httpVersion": "HTTP/1.1", 
          "redirectURL": "", 
          "status": 200, 
          "statusText": "OK"
        }, 
        "startedDateTime": "2010-07-28T03:31:57.882958Z", 
        "time": 86, 
        "timings": {
          "blocked": -1, 
          "connect": 0, 
          "dns": -1, 
          "receive": 0, 
          "send": 0, 
          "wait": 86
        }
      }
    ], 
    "pages": [
      {
        "id": "page_0", 
        "pageTimings": {
          "onContentLoad": -1, 
          "onLoad": -1
        }, 
        "startedDateTime": "2010-07-28T03:31:52.972106Z", 
        "title": "http://andrewfleenor.users.sourceforge.net/fhs/fhs.xml"
      }
    ], 
    "version": "1.1"
  }
}