Problem / Exercise For this lab, you will implement your own version of the rm systems program, a standard Unix utility that attempts to remove files or directory files using the unlink(2) and...


Need help in making this in C++


Problem / Exercise<br>For this lab, you will implement your own version of the rm systems program, a standard Unix utility that attempts to remove<br>files or directory files using the unlink(2) and rmdir(2) system calls. If the permissions of the file do not permit writing,<br>and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation. The<br>command-syntax is:<br>$ . /rm [-rf] file...<br>Your implementation should match the output of the existing rm utility. The -r option causes rm to attempt to recursively<br>remove the file hierarchy rooted in each file argument (see opendir(3), readdir(3), and closedir(3)). If the user does not<br>respond affirmatively, the file hierarchy rooted in that directory is skipped. The -f option causes rm to assume affirmative<br>responses from the user, foregoing any prompting.<br>Take special precautions NOT to recurse on the .. directory entry. Also think carefully on what you want to do with the<br>directory entry. If you are concerned, backing up important files on your odin account before testing your code may be a<br>good idea.<br>You are NOT allowed to use the exec, system, popen, and pclose system calls or functions in your implementation. You<br>are not allowed to call the existing rm implementation. You must supply your own implementation that uses low-level file<br>I/O (APUE Ch. 3), if needed.<br>The system calls and C library functions needed to complete this lab may not be explicitly discussed in class. You may need<br>to read the manual pages or look up in the textbook/online on how to use certain system calls and C library functions.<br>

Extracted text: Problem / Exercise For this lab, you will implement your own version of the rm systems program, a standard Unix utility that attempts to remove files or directory files using the unlink(2) and rmdir(2) system calls. If the permissions of the file do not permit writing, and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation. The command-syntax is: $ . /rm [-rf] file... Your implementation should match the output of the existing rm utility. The -r option causes rm to attempt to recursively remove the file hierarchy rooted in each file argument (see opendir(3), readdir(3), and closedir(3)). If the user does not respond affirmatively, the file hierarchy rooted in that directory is skipped. The -f option causes rm to assume affirmative responses from the user, foregoing any prompting. Take special precautions NOT to recurse on the .. directory entry. Also think carefully on what you want to do with the directory entry. If you are concerned, backing up important files on your odin account before testing your code may be a good idea. You are NOT allowed to use the exec, system, popen, and pclose system calls or functions in your implementation. You are not allowed to call the existing rm implementation. You must supply your own implementation that uses low-level file I/O (APUE Ch. 3), if needed. The system calls and C library functions needed to complete this lab may not be explicitly discussed in class. You may need to read the manual pages or look up in the textbook/online on how to use certain system calls and C library functions.
Jun 06, 2022
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here