Chapter 4 The Filesystem

a. milk_co simple pathname b. correspond/business/milk_co c. relative pathname c. /home/max absolute pathname d. /home/max/literature/promo absolute pathname e. etter.0210 simple filename.

a. cd b. pwd

To make a subdirectory in max you would ~/literature, to make a subdirectory in literature you could mkdir literature/promo with a relative pathname or mkdir /home/mac/literature/promo with an absolute pathname. To do both at once use mkdir -p literature/promo or mkdir -p literature/promo

a. How many filesystems are mounted on the local system. idk b. idk c. ln -f file1 file2. It didn't send an error message it just brought file over from one file to another. For a sym link ls -s path/to/file path/to/symlink ls -sf path/to/file path/to/symlink to update the symlink

You can use permissions to change who can read, write and execute the file.

a. They seem to be separated with _. b. One field per user? c. Not sure d. eh e.maybe

$ chmod u+rwx jobs_list

Yes, there are root privileges that non root privilege people don't have

a. When you run cd to milk_co the user can go there and the group and own can go but can't write. b. For business neither the user, group or own can read, write or execute. c. Everyone can read cheese_co

The inode is a data structure in a Unix-style file system that describes a filesystem object such as a file or a directory. Each inode stores the attributes and disk block location(s) of the object's data. ... A directory contains an entry for itself, its parent, and each of its children. The inode is updated with the new location of the file.

The .. entry is a link to the parent directory. In the case of the root directory, there is no parent, so the .. entry is a link to the root directory itself.

You can't create a file named -i because ls -i file_a file_b file_c is used to find out which files are linked.

It says rename andor to and/or: There's no such file or directory. The circumstance would be that the file/directory would have to exist.

idk right now

Normally, the system administrator cannot decode user passwords. The administrator can assign a new password to a user. Passwords are generally encrypted by a one-way hash so that the system can tell when the correct password is entered, but it cannot regenerate the cleartext password. Fundamentally the system applies the hash algorithm to the entered password and checks whether the result matches the stored, encrypted password. A match means the correct password was entered. However, if a user has a weak password, the system administrator can use a program such as crack or John the ripper to decode a password. You can download either of these utilities using yum. The packages are named crack and john.

idk

There is a file whose name begins with a period (a hidden file) in the dirtmp directory. Use ls with the -a option to list the file. Remove the file, and then you will be able to remove the directory.