This programming assignment is related with writing a simple shell by considering the outline program given in the lab sessions.

The main() function of your program presents the command line prompt myshell: and then invokes setup() function which waits for the user to enter a command. The setup function (given in the outline program of your textbook) reads the users next command and parses it into separate tokens that are used to fill the argument vector for the command to be executed. It can also detect background processes. This program is terminated when the user enters ^D (<CONTROL><D>); and setup function then invokes exit. The contents of the command entered by the user is loaded into the args array. You may assume that a line of input will contain no more than 128 characters or more than 32 distinct arguments.

Necessary functionalities and components of your shell is listed below:

1. It will take the command as input and will execute that in a new process. When your program gets the program name, it will create a new process using fork() system call, and the new process (child) will execute the program. The child will use the execl() function in the below to execute a new program.

• Use execv() instead of execvp(), which means that you will have to read the PATH environment variable, then search each directory in the PATH for the command file name that appears on the command line.
• Important Notes:
  1. Using the system() function is not allowed for part A!
  2. In the project, you need to handle foreground and background processes. When a process run in foreground, your shell should wait for the task to complete, then immediately prompt the user for another command.

myshell: gedit

A background process is indicated by placing an ampersand (&) character at the end of an input line. When a process run in background, your shell should not wait for the task to complete, but immediately prompt the user for another command.

myshell: gedit &

With background processes, you will need to modify your use of the wait() system call so that you check the process id that it returns.

1. It must support the following internal (built-in) commands. Note that an internal command is the one for which no new process is created but instead the functionality is built directly into the shell itself.
   • history seethe list of and execute the last 10 commands. See the following example for the use of these commands.

Example:

myshell> history

• ps
• ls
• ls -l
• who
• ps -a
• chmod 777 a.txt
• ls | wc
• ps ef
• ps
• ls -almyshell> ls /bin myshell> history
• ls /bin
• ps
• ls
• ls -l
• who
• ps -a
• chmod 777 a.txt
• ls | wc
• ps ef
• psmyshell> history -i 9

PID TTY TIME CMD 6052 pts/0 00:00:00 ps myshell> history

• ps
• ls /bin
• ps
• ls
• ls -l
• who
• ps -a
• chmod 777 a.txt
• ls | wc
• ps ef

In the first line, after issuing history command, the lastly executed 10 commands are printed on th screen. After executing ls /bin, you can see that the history is updated. With history -i num, we can execute the command at num index. After executing the command at some index, the history table is updated again.

To implement this part, you cannot use history command of Linux. You have to implement the functionality by yourself, creating data structures to store commands as necessary. When we want to execute a command at an index, execute it using the A part of the homework.

• ^Z Stop the currently running foreground process, as well as any descendants of that process (e.g., any child processes that it forked). If there is no foreground process, then the signal should have no effect.
• path path is a command not only to show the current pathname list, but also to append or remove several pathnames. In your shell implementation, you may keep a variable or data structure to deal with pathname list (referred to as path variable below). This list helps searching for executables when users enter specific commands.
  • path (without arguments) displays the pathnames currently set. It should show pathnames separated by colons. ex) /bin:/usr/bin
  • path + /foo/bar appends the pathname to the path variable. Only one pathname will be given to each invocation of the path command. Its okay to add a pathname to the path variable even if it already contains the same pathname, i.e., duplicates in the path variable are fine.
  • path /foo/bar removes the pathname from the path variable. It should remove all duplicates of the given pathname. Only one pathname will be given to each invocation of the path command.
• fg %num Move the background process with process id num to the background.. Note that for this, you have to keep track of all the background processes.
• exit Terminate your shell process. If the user chooses to exit while there are background processes, notify the user that there are background processes still running and do not terminate the shell process unless the user terminates all background processes.

1. I/O Redirection

The shell must support I/O-redirection on either or both stdin and/or stdout and it can include arguments as well. For example, if you have the following commands at the command line:

• myshell: myprog [args] > file.out

Writes the standard output of myprog to the file file.out. file.out is created if it does not exist and truncated if it does.

• myshell: myprog [args] >> file.out

Appends the standard output of myprog to the file file.out. file.out is created if it does not exist and appended to if it does.

• myshell: myprog [args] < file.in

Uses the contents of the file file.in as the standard input to program myprog.

• myshell: myprog [args] 2> file.out

Writes the standard error of myprog to the file file.out.

• myshell: myprog [args] < file.in > file.out

Executes the command myprog which will read input from file.in and stdout of the command is directed to the file file.out

Bonus (10%): You will get extra credit if your shell supports multiple commands at once. After entering a command sequence like command1 ; command2 if your shell execute command1 and than command2, you will get 10% extra points.