=====unix Keyword 1=====
Identification of chosen keyword.

====Definition====
Definition (in your own words) of the chosen keyword.

====References====
List any sites, books, or sources utilized when researching information on this topic. (Remove any filler text).

  * Reference 1
  * Reference 2
  * Reference 3



=====File Types Phase 2=====
//The Regular, Directory, and Special File Types//

====Definition====
Unlike most keywords, this one isn't just one simple keyword. A file type is a vague term that represents files, and in order to really know what one is, they should be defined, SUCH AS:

  - A **regular** file type: A regular file is the most common file type there is, this file type represents the text files, compressed files, binary files,and "file files."(not a real file, I just like the word. Basically any file that you would send as an email attachment is considered a regular file, within reason.
  - A **directory** file type: A directory file isn't commonly known as a file, but it is. The common folk would call this a "folder". You put all types of files within a directory file, even another directory file. What a directory file does is points you in the direction of more files, usually more than one. A symbolic link(which is a file) would fall into this category for that reason, which could point to a specific file or a directory. (A file that points to a directory; which points to more files.)
  - A **special** file type: A special file is the most uncommon file type. These files define the system devices and temporary files created by processes. There are 4 basic types of files that are considered "special" and they are FIFO (First in, first out) which are also known as pipes, which allow communication between processes temporarily, then there's block and character devices which define devices.

An important consideration when we're talking files is that each file has permissions for them that determine which users can Read, Write, or Execute a file. These are formally known as access  modes. These access modes are often represented in this format: Eg. drwxrwxr-- or srwxr-----
====References====

  * In Class Gathering September 5th, 2012
  * [[http://pic.dhe.ibm.com/infocenter/aix/v6r1/index.jsp?topic=%2Fcom.ibm.aix.baseadmn%2Fdoc%2Fbaseadmndita%2Ffiletypes.htm|IBM File Types]]

=====ls Phase 2=====
====Definition====
**ls** is a command for directory listing. What this mean is it lists all the contents of the directory in a curt manner. Usually just the names of the directories, files, and their file types by color coordination.
  * **-l** changes how ls operates and causes the command to do a **long/detailed listing**, revealing the file type and permissions.
  * **-al** causes a formatted listing with hidden files.

====References====
  * From the LAIR computer desktop.
====Demonstration====
Demonstration of the indicated keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>

Alternatively (or additionally), if you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>