EECE7376_Project

.pdf

School

Northeastern University *

*We aren’t endorsed by this school

Course

7376

Subject

Electrical Engineering

Date

Apr 3, 2024

Type

pdf

Pages

Uploaded by ChancellorSealMaster948

EECE7376 – Course Project 1 / 3 Northeastern University College of Engineering Department of Electrical & Computer Engineering EECE7376: Operating Systems: Interface and Implementation Course Project Instructions In this project you can work in a group of at most 2 students. If you work in a group, only one member must submit to the project assignment on Canvas the following: 1. Your project report developed by a word processor (e.g., Microsoft Word) and submitted as one PDF file. The report cover page must include your group details (full names and student IDs), course/section/semester information. For contents that require drawing and if it is difficult on you to use a drawing application, which is preferred, you can neatly hand draw “only” these diagrams, scan them, and insert the scanned images in your report document. The report includes the following:  Summaries of your approach to solving the programming part.  Screen shots of sample runs of your project programs. The sample runs must cover all scenarios of the project requirements.  An extended summary of your selected topic in part 2 of the project and the link to your YouTube lecture. 2. The well-commented source code files (i.e., the .c or .h files) that you add or modify. At the beginning of your source code files write your group details (full names and student IDs) and any special compiling/running instruction (if any). For the xv6 programs that you only make changes in them, only add comments to the parts you change/add and no need to add any names at the beginning of these programs. Do not submit any compiled object or executable files. 3. The project part 2 PowerPoint slides file. Do NOT submit any files (e.g., the PDF report file, the source code files, and the slides file) as a compressed (zipped) package. Rather, upload each file individually. Note: You can submit multiple attempts for this project, however, only what you submit in the last attempt will be graded. This means all required files must be included in this last submission attempt.

EECE7376 – Course Project 2 / 3 Part 1 - Shell The goal of this part of the project is implementing your own shell program on a Linux environment (not xv6). The shell program repeatedly reads commands from the user, interprets them, and translates them into a sequence of actions that likely involve an interaction with the operating system through system calls. Your code can rely on the string manipulation routines implemented throughout our previous homework assignments. The shell must include the following set of required features: 1. The shell should print a $ prompt symbol followed by a space when it is ready to receive a new command from the user. 2. When a command is launched in the foreground, the shell should wait until the last of its subcommands finishes before it prints the prompt again. A command is considered to be running in the foreground when operator & is not included at the end of the command line. 3. When a command is launched in the background using suffix & , the shell should print the pid of the process corresponding to the last sub-command. The pid should be printed in square brackets. It should then immediately display the prompt and accept new commands, even if any of the child processes are still running. For example: $ ls ‐ l | wc & [3256] $ 4. When a sub-command is not found, a proper error message should be displayed, immediately followed by the next prompt. Example: $ hello hello: Command not found $ 5. The input redirection operator < should redirect the standard input of the first sub-command of a command. If the input file is not found, a proper message should be displayed. Example: $ wc < valid_file.txt 223 551 5288 $ wc < invalid_file invalid_file: File not found 6. The output redirection operator > should redirect the standard output of the last sub-command of a command. If the output file cannot be created, a proper message should be displayed. Example: $ ls ‐ l > invalid/path invalid/path: Cannot create file $ ls ‐ l > hello $ cat hello < Contents of “hello” displayed here >

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version