Lab46 Wiki

To become familiar with the UNIX directory structure as well as file permissions.

In “UNIX for the Beginning Mage”, please read:

• Chapter 4 (pages 37-44).
• Chapter 5 (pages 45-58).

In “Harley Hahn's Guide to UNIX and Linux”, please read:

• Chapter 23 (“The UNIX Filesystem”, pages 627-658).
• Chapter 24 (“Working with Directories”, pages 659-714).
• Chapter 25 (“Working with Files”, pages 715-766).

In “Learning the UNIX Operating System, 5th Edition”, please read:

• Chapter 3 (“Using Your UNIX Account”, pages 42-65).

The UNIX filesystem is built on a hierarchical structure. The base, or root, directory is the starting point of the filesystem. It is identified by the /, which is also used as the directory separator. / is the lowest point on the filesystem- you cannot go beyond it.

From the base of the filesystem are the traditional subdirectories that contain the UNIX system as we know it. While there can be any number of directories, the traditional ones found include: /bin, /etc, /home, /lib, /mnt, /root, /sbin, /tmp, /usr, and /var.

Although many variations can occur, here is an example diagram of the filesystem structure on Lab46 (and with the exception of our /home directory tree, most everything else will be fairly standard across default Linux installs.

Each directory will typically hold certain types of files, as seen below:

Your home directory is the starting point of your login session. It contains customized login files as well as any personal files you have created while on the system. In Lab #0 you used the pwd utility to display the actual location of your home directory.

Your prompt reflects the current working directory. This is the directory you are currently located in on the filesystem. The pwd utility will display the full path of your working directory.

Your book talks about two types of pathnames: absolute and relative.

An absolute pathname is a specific reference to a location on the filesystem. When you issue the pwd command, it returns the absolute pathname of your current location. When an absolute pathname is given, the final destination is immediately known.

For example: If you type “cd /usr/bin” at your prompt, it will take you to the /usr/bin directory, regardless of where you currently are. This is because you are giving a precise destination.

A relative pathname, on the other hand, refers to something reachable from your present location. A relative pathname's final destination isn't as defined. It only makes sense from the particular starting location.

For example: If you are in your home directory and type “cd src” at your prompt, you will be taken into your src/ subdirectory. If you change to the root and again try to “cd src” the system will give you an error because there is no subdirectory in /.

If you give ls the -a option while in any directory, you will notice that any given directory will have the . and .. directories. These files serve a special meaning for directory & pathname navigation.

The . directory always refers to your current directory.

The .. directory, on the other hand, refers to the previous (or parent) directory to your current directory. In Lab #0 you went to the .. directory while in your home directory to end up at /home.

Both . and .. can be used as relative pathnames, as they direct you somewhere from your current position.

Everything you encounter on the UNIX filesystem is a file. There are three types of files in UNIX: regular files, directories, and special files.

regular (or ordinary) files are the text and executable files we've been playing with.

A directory is merely a file that points to other files.

Special files consist of devices, network pipes, and sockets.

In Learning the UNIX Operating System, 5th Edition on page 51, the “Type” column in figure 3-5 gives a clear indication from ls regarding what type of file is being listed. The - and d are the most common. Others seen include l for symbolic link, b for block device, c for character device, p for a pipe, and s for socket.

Going back to page 51, there is reference to a file's access modes. Page 57 also begins a section on File Access Permissions.

File Permissions allow for customized access to the files on a UNIX system, according to three levels of authority- user, group, and other. There are three modes of access for each category- read, write, and execute/search.

Observe the following table:

Looking at the figure 3-5 in the book (or any output of ls -l), the first column of output consists of the file's type and access modes. There are nine places available for the access modes, which corresponds perfectly to the scheme described above. The first 3 places describe the file owner's permissions, the next three describe the file group's permissions, and the remaining three places describe what permissions anyone else on the system has.

File permissions and attributes are dually hierarchial in UNIX. Not only do you have access control with regards to file ownership, there is also access control over file attributes (indicating what actions can be performed on the files).

It is with a combination of these two hierarchies that we get the UNIX file access structure.

Two methods exist for manipulating file access permissions, and both will be described here. The traditional method has involved the use of octal numbers, which as we will see below, nicely works to support the data we are representing.

To appeal to a more “user-friendly” environment, symbolic permissions are also present, which allow us to use specially designated symbols to manipulate the permissions.

Observe the following table:

Be sure you read over the section on “File Attributes” in your text (pages 41-46).

Read access is represented by a 4. Write access is a 2, and Execute access is a 1. To obtain the octal value, you add the necessary access bits together.

For example- if the owner of a text file can read and write it, they have both read (4) + write (2) = read/write (6) access to that file. If both the group and the world can only read (4) that same file, it is said that the file has permissions of 644.

This information is displayed visually for you when using the -l option to the ls utility. A diagram of such appears as follows:

Of course, under each field of “user”, “group”, or “world”, you can have your desired settings of “read”, “write”, and “execute”. Attributes left unset will be represented symbolically as a dash (-), and numerically as 0.

Symbolic permissions in some respects are not as flexible as the octal permissions, but allow for easy changes of individual modes. Your textbooks explain and give examples of how to use the symbolic notation.

The chmod(1) utility is used to change file permissions. It accepts both symbolic and octal permissions. Please be sure to reference its manual page for additional information.

The concepts presented here will be important in your usage of the system throughout the semester. Make sure you understand the material presented here, and to ask questions if something does not make sense.

As we discovered earlier in the lab, the UNIX filesystem is a hierarchical structure, starting at /, the root, and propagating from that point on.

Your home directory exists somewhere within this hierarchy, and so do the files within your home directory.

One thing you may have noticed is that at several different levels of the UNIX filesystem there are directories with identical names, such as ~/bin/, /bin/, /usr/bin/, and /usr/local/bin/.

It is important to make this distinction between the various similarly-named directories located on the system as they reside in a path. Same name but different entities play an important role in many areas.

All questions in this assignment require an action or response. Please organize your responses into an easily readable format and submit the final results to your instructor.

Your assignment is expected to be performed and submitted in a clear and organized fashion- messy or unorganized assignments may have points deducted. Be sure to adhere to the submission policy.

The successful results of the following actions will be considered for evaluation:

• your responses to questions submitted at the following form:

<html><center><a href=“http://lab46.corning-cc.edu/haas/content/unix/submit.php?lab2”>http://lab46.corning-cc.edu/haas/content/unix/submit.php?lab2</a></center></html>

• the response from the form (received via e-mail) saved as lab2.txt to your ~/src/unix/ directory
• addition/commit of ~/src/unix/lab2.txt into your repository (CS 0x0 sets you up to do this).

As always, the class mailing list and class IRC channel are available for assistance, but not answers.