No errors were found in the text 54046

Name: no errors were found in the text 54046
Uploaded: 2023-11-13T01:01:53-08:00
Duration: 2 min 7 s
Channel: Akash M
Description: no errors were found in the text 54046

Labs

Want to see this concept in action?

NEW

Explore this concept interactively to see how it behaves as you change inputs.

View Labs

Recommended Videos

purpose-this-assignment-should-give-you-experience-in-using-file-descriptors-open-close-write-stat-and-chmod-perror-and-command-line-arguments-program-write-a-program-that-will-allow-you-to-17325

Text: Purpose This assignment should give you experience in using file descriptors, open(), close(), write(), stat() and chmod(), perror(), and command line arguments. Program Write a program that will allow you to add messages to a file that has NO permissions for any user. A Unix system has many files that have sensitive information in them. Permissions help keep these files secure. Some files can be publicly read, but cannot be altered by a regular user (e.g., /etc/passwd). Other files cannot be read at all by a regular user (e.g., /etc/shadow). The program you develop should take a message given as a command line argument and append it to a file (also specified on the command line). The file should have no permissions, both before and after the message is appended. Of course, the file should be owned by you. Your program should also have a -c option that will clear the file before the message is appended. Algorithm Check to see if the output file exists. If it doesn't, create it. Life is simpler if a newly created file is closed at the end of this step. Check the permissions of the output file. If any permissions exist, print a useful error message and exit. Change the permissions on the file to allow writing by the user. Open the file for output. If the "-c" command line option is present, make sure the file is truncated. Write the message from the command line to the output file. Write an additional newline character so that the output has a nicer format. Clear the permissions and close the file. (These two operations can be performed in either order, but the implementation is slightly different.) Useful Hints Don't use the command line arguments directly. Their position in the argument list may change depending on options. Create meaningful char* variables and fill these with the appropriate entries from the argument list. Check for error values after nearly every system function call. It's a pain to set up, but it saves time in the long run. Input None, really. Just command line arguments. Error Checking If the log file cannot be opened, an appropriate error message should be printed and the program should exit. If the file has any permissions at all, the file should be rejected as insecure, and the program should exit.

Akash M.

linux-bash-shell-script-lab9-instructions-open-the-terminal-and-using-vivim-create-a-new-script-and-name-it-lab9-insert-at-the-top-of-your-file-a-comment-with-your-nameclass-and-section-numb-14236

Lab 9 Instructions: Open the terminal and using vi/vim create a new script and name it lab9 Insert at the top of your file a comment with your name, class and section number (e.g. #John Doe, EMT 2390L - ABC123). This lab will help a user determine the permissions in a user-friendly way. In your script named lab9 do the following: Show the user the following questions to get the right permissions for the owner, the group, and the world: - Do you want to grant read permissions? - Do you want to grant write permissions? - Do you want to grant execute permissions? Show the appropriate permission in Octal notation according to the following table: Octal Binary File Mode 0 000 --- 1 001 --x 2 010 -w- 3 011 -wx 4 100 r-- 5 101 r-x 6 110 rw- 7 111 rwx Your script should then display to the user the appropriate octal number permission based on the user selection. - e.g. if the user chose read, write and execute for the owner; read and execute for the group; read and execute for the world; your script will show: 755 - e.g. if the user chose read, write and execute for the owner; read and write for the group; read only for the world; your script will show: 764 Save the script and make it executable (HINT: use the chmod command with mode 755). Execute the script (HINT: use dot slash ./ combination, followed by your script name) and fix any errors.

Akash M.

1instructions-this-assignment-deals-with-unix-file-protections-set-the-protections-on-the-directories-and-files-that-you-created-for-the-earlier-files-and-directories-assignment-as-follows-u-54624

This assignment deals with Unix file protections. Set the protections on the directories and files that you created for the earlier "Files and Directories" assignment as follows: ~/UnixCourse: You should be able to add and remove files from the directory, access files within the directory whose names you already know, and look through the directory via "ls" to see what files are in there. No one else should be able to do any of these things. (This is a good setting for directories where you will keep assignments for various courses. After this assignment, your ~/UnixCourse directory should always be set this way.) ~/UnixCourse/fileAsst: You should be able to add and remove files from the directory, access files within the directory whose names you already know, and look through the directory via "ls" to see what files are in there. People in your group should be able to do "ls" and to access files, but not add/remove files from the directory. People outside your group should be able to do none of these things. Actually, no one but you will really have access to this directory because it's inside ~/UnixCourse and, if you've done the prior step correctly, they can't get inside there to get to fileAsst. But, for the sake of this exercise, we'll ignore that fact. ~/UnixCourse/fileAsst/Earth: You should be able to add and remove files from the directory, access files within the directory whose names you already know, and look through the directory via "ls". Everyone else should be able to use "ls" but have no other privileges. ~/UnixCourse/fileAsst/Galaxy: You should be able to add and remove files from the directory, access files within the directory whose names you already know, and look through the directory via "ls". Everyone else should be able to access files in the directory for which they already know the names, but have no other privileges. ~/UnixCourse/fileAsst/Earth/zaphod.txt: Everyone should be able to read and write to this file. ~/UnixCourse/fileAsst/Galaxy/trillian.txt: We will pretend, for the sake of this assignment, that this file contains an executable program. You should be able to read and write to this file. You and members of your group should be able to execute it. People other than you have no other privileges. When you have set all these file permissions, give the command: ~cs252/bin/fileprotAsst to check your work.

Akash M.

Transcript

00:01 Hello, here we are with the answers to the given question.

00:02 Let's start the discussion.

00:04 In this context, we first of all deal with the purpose of the assignment.

00:12 We are coming to the purpose of assignment.

00:14 This involves gaining experience in using descriptors and also consider for descriptions.

00:29 And here we have to consider the role of paracord also.

00:37 Secondly, it's all about the program.

00:42 The program will take into consideration certain steps like checking to see if output file exists.

00:50 So, first see the case of output file, then you check for the permission, from there you check for the message and then you clear the permission.

01:11 This is how it goes...

Question

No errors were found in the text.

Question

No errors were found in the text.

Please give Ace some feedback