A project for COURSENAME by YOUR NAME during the SEMESTER YEAR.

This project was begun on DATE and is anticipated to take 1 week. (Upon completion you can correct this with the actual length).

State the purpose of this project. What is the point of this project? What do we hope to accomplish by undertaking it?

In order to successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:

• cd command
• ls
• -l argument to ls
• understanding of paths, absolute and relative

State the idea or purpose of the project. What are you attempting to pursue?

Upon approval, you'll want to fill this section out with more detailed background information. DO NOT JUST PROVIDE A LINK.

Providing any links to original source material, such as from a project page, is a good idea.

You'll want to give a general overview of what is going to be accomplished (for example, if your project is about installing a web server, do a little write-up on web servers. What is it, why do we need one, how does it work, etc.)

To get a better understanding of the layout and structure of the UNIX filesystem, an exploration is in order. Using your observation skills and references, explore the various major directories on the system (starting with '/') and describing the intended purpose of each directory:

1. what types of files does it contain (regular, directory, special)
2. what is the organizational value of that directory (config files, basic tools, admin tools, etc.)

Some of the directories you will want to explore are:

• /
• This is the root of the system, and therefore contains primarily directories and symbolic links to give the file system the organizational properties it needs to be used most naturally.
• /bin
• /bin is a directory which holds the majority of the file system's binary files. It's the directory we would reference if we wanted to check out the binary executables the system and user consistently use.
• /dev
• /dev symbolizes our 'device' directory. They're denoted in an “ls -l” by yellow coloration.
• /etc
• “/etc” (et-see) seems to be a directory housing our personally installed programs/applications. I correlate it with what is the Window's equivalent of “C:/Program Files”
• /home
• This is the root of our user's files. /home is the parent directory to my own user account's personal file system, along with all other users of the system.
• /lib (/lib32 vs. /lib64)
• Logically I didn't understand this directory, but it turns out that it is a bunch of files used for booting the system. /lib, lib32, /lib64 would seem to just be different loading methods according to the type of system you're on bit-wise. It contains many directories and links, as well as a good few binary files.
• /mnt
• This is a directory which will allow us to do our own manual mounting of devices or images. It's most likely not going to be used by the OS to auto-mount anything. Those jobs will go to our /media directory under the devices default name. We can mount file systems OR actual files (.iso images) using the mount command. mount -oloop?
• /proc
• This is a directory which manages our processes it seems. There are tons of subdirectories ( one for each process active on the system, it would seem ), and inside the processes directory ( labeled as a PID ), there are many binary files which appear to be pertinent to the function of the process itself.
• /root
• “root's” home directory. Root is the administrator of the system?
• /sbin
• I see, in this directory, “shutdown”, “mkfs”, “ifconfig”, “killall5” (which it turns out isn't great to run when you intend to continue using the system you're on), and I deduce that the name of the directory implies “System Binaries”.
• /tmp
• Temporary files?
• /usr
• The /usr directory seems to be an alternate root, but most likely files for the specific user.
• /var
• It looks like this stores hard copies of variables for applications to reference.
• /var/log
• Most likely some usage information logs to look back on. File types found in this directory are red in color. Not sure what that implies at this time.
• /usr/bin
• Binary files for the specified user. Seems super similar to the root bin directory.
• /usr/sbin
• Hey, looks like the same thing again.
• /usr/src
• The src directory in /home was just for source files of programs that I'm working on. I assume this is again the same thing, but for generalized users, or the specific users. Something of that sort.
• /usr/local
• This is a local storage directory for software generally available on the system to all users (typically). And I'm stating that even though it's an assumption.
• /usr/local/bin
• Same as above, but for the binary files, instead of file structures, and or anything other than binary files (executable, I think).
• /usr/lib
• Some object files and library files. Apparently these aren't able to be executed by the typical user or shell scripts.

This seems like it could be a good reference: http://www.pathname.com/fhs/pub/fhs-2.3.html

State and justify the attributes you'd like to receive upon successful approval and completion of this project.

• files and directories: files and directories are the focus of analysis in this exercise

The actual steps taken to accomplish the project. Include images, code snippets, command-line excerpts; whatever is useful for intuitively communicating important information for accomplishing the project.

Comments/thoughts generated through performing the project, observations made, analysis rendered, conclusions wrought. What did you learn from doing this project?

In performing this project, the following resources were referenced:

• URL1
• URL2
• URL3 (provides useful information on topic)
• URL4

Generally, state where you got informative and useful information to help you accomplish this project when you originally worked on it (from Google, other wiki documents on the Lab46 wiki, etc.)