Term
| A way to establish a connection between the file to be shared and the directory of the users who want to have access to this file. |
|
Definition
|
|
Term
| A pointer to the inode of a file |
|
Definition
|
|
Term
| Create a hard link to existing-file and name it new-file |
|
Definition
ln [options] existing-file new file
note: user must have execute privileges for all the directories in the path leading to the file. |
|
|
Term
| Create hard links to the ordinary files in existing-file-list in 'directory'; links have the same name as the original file |
|
Definition
| ln [options] existing-file-list directory |
|
|
Term
| If hard link is created to a file and the file is then removed is the file still accessible on disk? Explain. |
|
Definition
| Yes, it is still accessible. The hard link had the inode number and file attributes that the original file had, except that the link count is decremented by 1. |
|
|
Term
| Create hard links to all the files to all nondirectory files in the ~/unixbook/examples/dir1 and have the hard links reside in ~/unixbook/examples/dir2 |
|
Definition
ln -f ~/unixbook/examples/dir1/* ~unixbook/examples/dir2
note: You must have execute permission for the directories in the pathname |
|
|
Term
| Hard links cannot be established between files that are on different __ __ |
|
Definition
|
|
Term
| When a file is with multiple hard links is moved to another file system which is a different file system than the one the file currently resides in what is the result. Be specific. |
|
Definition
| The link count for the file and hard link is decremented by one. The files have different inodes. The ln command cannot link the file to the hard link because the two files are in different file systems. |
|
|
Term
| Only a ___ can create a hard link to a directory |
|
Definition
|
|
Term
| Command used to create a symbolic link to a file |
|
Definition
|
|
Term
| Describe the attributes of a soft link that are different than a hard link |
|
Definition
1. the original file and the link file have different inode numbers.
2. The original file is of ordinary file type (-) and the link file is of link type (l).
3. The link count is 1 for both files.
4. the file sizes are different.
5. The name of the link is is followed by ->original_file |
|
|
Term
| What is the content of a soft link file |
|
Definition
| the pathname of the existing file |
|
|
Term
| command to create a soft link to a file |
|
Definition
|
|
Term
| Create soft links to all nondirectory files in the ~/unixbook/examples/dir1 and have the hard links reside in ~/unixbook/examples/dir2; links have the same name as the original file |
|
Definition
| ln -sf d~/unixbook/examples/dir1/* ~/unixbook/examples/dir2 |
|
|
Term
| Can you create a soft link to a directory. Give an example and put the soft link in the home directory. |
|
Definition
|
|
Term
| Create a soft link called demo1 in a directory in bob's home direct that points to directory dir1 in your home directory |
|
Definition
ln -sf ~/dir1 /users/bob/dir1
note; you must have execute permission for bob's home directory, and execute and write permission for dir1. The user bob must have proper access permissions for dir1 in your directory structure to access this file. |
|
|
Term
| Give one weakness of soft links |
|
Definition
| If the file that the link points to is moved from one directory to another, it no longer be accessed via the link, which is a pathname to the file. |
|
|
