ln (hard and symbolic links) in Linux CLI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a hard link named 'linkfile' to 'originalfile'.

Linux CLI

ln [1] originalfile linkfile

Drag options to blanks, or click blank then click option'

A-s

B(no option)

C-h

D-f

Attempts:

3 left

💡 Hint

Common Mistakes

Using -s option creates a symbolic link instead of a hard link.

Using -h is not a valid option for ln.

To create a hard link, you use ln without any options. The -s option is for symbolic links.

2fill in blank

medium

Complete the code to create a symbolic link named 'symblink' to 'targetfile'.

Linux CLI

ln [1] targetfile symblink

Drag options to blanks, or click blank then click option'

A-s

B-f

C-h

D-l

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the -s option creates a hard link instead.

Using -l is not a valid option for ln.

The -s option tells ln to create a symbolic (soft) link.

3fill in blank

hard

Fix the error in the command to create a symbolic link named 'link' to 'file.txt'.

Linux CLI

ln [1] file.txt link

Drag options to blanks, or click blank then click option'

A-s

B-h

C-f

D--symbolic

Attempts:

3 left

💡 Hint

Common Mistakes

Using -h instead of -s.

Omitting the option creates a hard link.

The correct option for symbolic links is -s. Using -h is invalid.

4fill in blank

hard

Fill both blanks to create a symbolic link named 'link' pointing to 'file.txt' and force overwrite if 'link' exists.

Linux CLI

ln [1] [2] file.txt link

Drag options to blanks, or click blank then click option'

A-s

B-f

C-h

D-l

Attempts:

3 left

💡 Hint

Common Mistakes

Using -h which is invalid.

Forgetting to use -f to overwrite existing links.

Use -s for symbolic link and -f to force overwrite existing links.

5fill in blank

hard

Fill all three blanks to create a hard link named 'hardlink' to 'data.txt' and then list the links with inode numbers.

Linux CLI

ln [1] data.txt hardlink && ls -i [2] [3]

Drag options to blanks, or click blank then click option'

A(no option)

Bdata.txt

Chardlink

D-s

Attempts:

3 left

💡 Hint

Common Mistakes

Using -s option creates symbolic link instead of hard link.

Listing only one file does not show inode comparison.

Hard links are created without options (empty string). Then ls -i lists inode numbers of both files to verify they share the same inode.

Practice

1. What is the main difference between a hard link and a symbolic link in Linux?

easy

A. A hard link can only link to directories; a symbolic link can only link to files.

B. A hard link is a shortcut to a directory; a symbolic link is a shortcut to a file.

C. A hard link points directly to the file's data, sharing the inode; a symbolic link points to the file name.

D. A hard link uses ln -s; a symbolic link uses ln.

Solution

1. Step 1: Understand hard link behavior

   Hard links share the same inode number and point directly to the file data, making them indistinguishable from the original file.

2. Step 2: Understand symbolic link behavior

   Symbolic links are special files that contain a path to another file or directory, acting like shortcuts pointing to file names.

3. Final Answer:

   A hard link points directly to the file's data, sharing the inode; a symbolic link points to the file name. -> Option C

4. Quick Check:

   Hard link = inode sharing, Symbolic link = filename pointer [OK]

Hint: Hard links share inode; symbolic links point to names [OK]

Common Mistakes:

• Confusing which link shares inode
• Thinking symbolic links share file data
• Mixing up commands for creating links

2. Which command correctly creates a symbolic link named linkfile pointing to originalfile?

easy

A. ln -s originalfile linkfile

B. ln linkfile originalfile

C. ln -s linkfile originalfile

D. ln originalfile linkfile

Solution

1. Step 1: Recall symbolic link syntax

   The syntax for creating a symbolic link is ln -s <target> <link_name>.

2. Step 2: Match command to syntax

   ln -s originalfile linkfile uses ln -s originalfile linkfile, which correctly creates a symbolic link named linkfile pointing to originalfile.

3. Final Answer:

   ln -s originalfile linkfile -> Option A

4. Quick Check:

   ln -s target link_name [OK]

Hint: Use ln -s target link_name for symbolic links [OK]

Common Mistakes:

• Swapping target and link name order
• Omitting -s for symbolic links
• Using ln -s with wrong argument order

3. Given the commands:

echo "Hello" > file1
ln file1 file2
ln -s file1 file3
rm file1

What will be the output of cat file2 and cat file3?

medium

A. file2: Hellofile3: Hello

B. file2: cat: file2: No such file or directoryfile3: cat: file3: No such file or directory

C. file2: cat: file2: No such file or directoryfile3: Hello

D. file2: Hellofile3: cat: file3: No such file or directory

Solution

1. Step 1: Understand hard link behavior after deleting original

   Hard link file2 points to the same inode as file1. Removing file1 does not delete the data because file2 still references it. So cat file2 outputs "Hello".

2. Step 2: Understand symbolic link behavior after deleting original

   Symbolic link file3 points to the name file1. After deleting file1, file3 points to a non-existent file, so cat file3 gives an error.

3. Final Answer:

   file2: Hello
   file3: cat: file3: No such file or directory -> Option D

4. Quick Check:

   Hard link survives deletion; symbolic link breaks [OK]

Hint: Hard links keep data after original deleted; symbolic links break [OK]

Common Mistakes:

• Assuming symbolic link still works after target deletion
• Thinking hard link deletes data with original
• Confusing link types' behavior on file removal

4. You run the command ln -s /path/to/file linkname but get an error: ln: failed to create symbolic link 'linkname': File exists. What is the best way to fix this?

medium

A. Delete the target file and rerun the command.

B. Use ln -sf /path/to/file linkname to force overwrite the existing link.

C. Use ln /path/to/file linkname without -s.

D. Rename the target file before creating the link.

Solution

1. Step 1: Understand the error cause

   The error occurs because linkname already exists, and ln refuses to overwrite existing files or links by default.

2. Step 2: Use force option to overwrite

   Using ln -sf forces the symbolic link creation by overwriting the existing linkname safely.

3. Final Answer:

   Use ln -sf /path/to/file linkname to force overwrite the existing link. -> Option B

4. Quick Check:

   ln -sf overwrites existing links safely [OK]

Hint: Use -sf to force overwrite existing symbolic links [OK]

Common Mistakes:

• Deleting the target file instead of the link
• Omitting -s and creating hard link by mistake
• Renaming target unnecessarily

5. You want to create a backup system where multiple filenames point to the same file data without duplicating storage. Which command and link type should you use, and why?

hard

A. Use ln to create hard links because they share the same inode and save space.

B. Use ln -s to create symbolic links because they are easier to manage.

C. Copy the file multiple times to ensure backups are independent.

D. Use ln -s with absolute paths to avoid broken links.

Solution

1. Step 1: Identify storage-saving method

   Hard links share the same inode and file data, so multiple filenames point to the same data without duplicating storage.

2. Step 2: Compare with symbolic links and copies

   Symbolic links only point to filenames and do not save storage if the original is deleted. Copying duplicates data, using more space.

3. Final Answer:

   Use ln to create hard links because they share the same inode and save space. -> Option A

4. Quick Check:

   Hard links save space by sharing inode [OK]

Hint: Hard links share data, saving space for backups [OK]

Common Mistakes:

• Choosing symbolic links for storage saving
• Copying files instead of linking
• Ignoring inode sharing concept