Please write the program and explain-line-by-line. Thank you! A shell interface gives the user a prompt, after which the next command is entered. The example below illustrates the prompt osh> and the user's next command: cat prog.c. (This command displays the file prog.c on the terminal using the UNIX cat command.) osh>cat prog.c One technique for implementing a shell interface is to have the parent process first read what the user enters on the command line (in this case, cat prog.c) and then create a separate child process that performs the command. Unless otherwise specified, the parent process waits for the child to exit before continuing. This is similar in functionality to the new process creation illustrated in Figure 3.9. However, UNIX shells typically also allow the child process to run in the background, or concurrently. To accomplish this, we add an ampersand (&) at the end of the command. Thus, if we rewrite the above command as osh>cat prog.c & the parent and child processes will run concurrently. The separate child process is created using the fork() system call, and the user's command is executed using one of the system calls in the exec() family A C program that provides the general operations of a command-line shell is supplied in Figure 3.32. The main() function presents the prompt osh-> and outlines the steps to be taken after input from the user has been read. The main() function continually loops as long as should_run equals 1; when the user enters exit at the prompt, your program will set should_run to 0 and terminate. #include #include #define MAX_LINE 80 /* The maximum length command */ 2 int main(void) { char *args[MAX_LINE/2 + 1]; /* command line arguments */ int should_run = 1; /* flag to determine when to exit program */ while (should_run) { printf("osh>"); fflush(stdout); /** * After reading user input, the steps are: * (1) fork a child process using fork() * (2) the child process will invoke execvp() * (3) parent will invoke wait() unless command included & */ } return 0; } Figure 3.32 Outline of simple shell. This project is organized into several parts: 1. Creating the child process and executing the command in the child 2. Providing a history feature II. Executing Command in a Child Process The first task is to modify the main() function in Figure 3.32 so that a child process is forked and executes the command specified by the user. This will require parsing what the user has entered into separate tokens and storing the tokens in an array of character strings (args in Figure 3.32). For example, if the user enters the command ps -ael at the osh> prompt, the values stored in the args array are: args[0] = "ps" args[1] = "-ael" args[2] = NULL This args array will be passed to the execvp() function, which has the following prototype: execvp(char *command, char *params[]) Here, command represents the command to be performed and params stores the parameters to this command. For this project, the execvp() function should be invoked as execvp(args[0], args). Be sure to check whether the user included & to determine whether or not the parent process is to wait for the child to exit.
Please write the
A shell interface gives the user a prompt, after which the next command is entered. The example below illustrates the prompt osh> and the user's next command: cat prog.c. (This command displays the file prog.c on the terminal using the UNIX cat command.)
osh>cat prog.c
One technique for implementing a shell interface is to have the parent process first read what the user enters on the command line (in this case, cat prog.c) and then create a separate child process that performs the command. Unless otherwise specified, the parent process waits for the child to exit before continuing. This is similar in functionality to the new process creation illustrated in Figure 3.9. However, UNIX shells typically also allow the child process to run in the background, or concurrently. To accomplish this, we add an ampersand (&) at the end of the command. Thus, if we rewrite the above command as
osh>cat prog.c &
the parent and child processes will run concurrently.
The separate child process is created using the fork() system call, and the user's command is executed using one of the system calls in the exec() family
A C program that provides the general operations of a command-line shell is supplied in Figure 3.32. The main() function presents the prompt osh-> and outlines the steps to be taken after input from the user has been read. The main() function continually loops as long as should_run equals 1; when the user enters exit at the prompt, your program will set should_run to 0 and terminate.
#include <stdio.h> #include <unistd.h>
#define MAX_LINE 80 /* The maximum length command */ 2
int main(void) {
char *args[MAX_LINE/2 + 1]; /* command line arguments */ int should_run = 1; /* flag to determine when to exit program */
while (should_run) { printf("osh>");
fflush(stdout);
/**
* After reading user input, the steps are:
* (1) fork a child process using fork()
* (2) the child process will invoke execvp()
* (3) parent will invoke wait() unless command included & */
}
return 0; }
Figure 3.32 Outline of simple shell. This project is organized into several parts:
-
1. Creating the child process and executing the command in the child
-
2. Providing a history feature
II. Executing Command in a Child Process
The first task is to modify the main() function in Figure 3.32 so that a child process is forked and executes the command specified by the user. This will require parsing what the user has entered into separate tokens and storing the tokens in an array of character strings (args in Figure 3.32). For example, if the user enters the command ps -ael at the osh> prompt, the values stored in
the args array are: args[0] = "ps"
args[1] = "-ael"
args[2] = NULL
This args array will be passed to the execvp() function, which has the following prototype:execvp(char *command, char *params[])
Here, command represents the command to be performed and params stores the parameters to this command. For this project, the execvp() function should be invoked as execvp(args[0], args). Be sure to check whether the user included & to determine whether or not the parent process is to wait for the child to exit.
III. Creating a History Feature
The next task is to modify the shell interface program so that it provides a history feature to allow a user to execute the most recent command by entering !!. For example, if a user enters the command ls −l, she can then execute that command again by entering !! at the prompt. Any command executed in this fashion should be echoed on the user's screen, and the command should also be placed in the history buffer as the next command.
Your program should also manage basic error handling. If there is no recent command in the history, entering !! should result in a message “No commands in history.”
In addition, using up/down arrow keys on keyboard, your program should navigate through the list of previously used commands. When an up arrow is pressed, one previous command in the history buffer will be displayed on the console prompt. If down arrow is pressed, one next command in the history buffer will be displayed in the console prompt. To understand the behavior, try it in a normal Linux shell.
Use the history buffer size five, meaning we save five previous commands. The buffer does not “circulate,” which means, when you reached the oldest/newest command, and then pressed up/down, respectively, nothing will happen (or you can play beep sound).
To implement the arrow key feature, you will need to investigate the concept of canonical vs. non-canonical input processing.
Trending now
This is a popular solution!
Step by step
Solved in 2 steps
