Project 1, Command Shell CS-502 (EMC) Fall 20091 Programming Project #1 Command Shell CS-502, Operating Systems EMC, Fall 2009 (Slides include materials.

Slides:



Advertisements
Similar presentations
Shell Script Assignment 1.
Advertisements

1 CS345 Operating Systems Φροντιστήριο Άσκησης 1.
Grid Computing, Barry Wilkinson, 2004A3.1 Assignment 3 Simple Job Submission Using GRAM.
Last Lab: Writing a shell
CSE 451: Operating Systems Section 2 Shells and System Calls.
Processes CSCI 444/544 Operating Systems Fall 2008.
1 CSE 451 Section Autumn 2004 Alex Moshchuk Office hours: Tue 1-2, Thu 4:30-5:30 Allen 218 (or lab)
CSE 451 Section Autumn 2005 Richard Dunn Office hours: WTh 3:30-4:20 Allen 216 (or lab)
CS-502 Fall 2006Project 1, Fork1 Programming Project 1 – Fork.
Project 1CS-3013 A-term Programming Project #1 Forking Processes Due Tuesday, September 8, 11:59 PM.
Programming Project #3CS-4513, D-Term Programming Project #3 Simple Web Server CS-4513 D-Term 2007 (Slides include materials from Operating System.
Process in Unix, Linux and Windows CS-3013 C-term Processes in Unix, Linux, and Windows CS-3013 Operating Systems (Slides include materials from.
CS-502 Fall 2006Processes in Unix, Linux, & Windows 1 Processes in Unix, Linux, and Windows CS502 Operating Systems.
CS-3103 & CS-502, Summer 2006 Programming Project #31 Programming Project #3 Web Server CS-3103 & CS-502 Operating Systems.
IntroductionCS-3013 C-term Programming Project #1 Forking Processes Due Thursday, January 24, 6:00 PM.
Processes in Unix, Linux, and Windows CS-502 Fall Processes in Unix, Linux, and Windows CS502 Operating Systems (Slides include materials from Operating.
Programming project #1 1 CS502 Spring 2006 Programming Project #1 CS-502 Operating Systems Spring 2006.
Introduction to Linux and Shell Scripting Jacob Chan.
1 SEEM3460 Tutorial Unix Introduction. 2 Introduction What is Unix? An operation system (OS), similar to Windows, MacOS X Why learn Unix? Greatest Software.
Unix Processes Slides are based upon IBM technical library, Speaking Unix, Part 8: Unix processes Extended System Programming Laboratory (ESPL) CS Department.
Chapter 9 Part II Linux Command Line Access to Linux Authenticated login using a Linux account is required to access a Linux system. The Linux prompt will.
Process in Unix, Linux, and Windows CS-3013 A-term Processes in Unix, Linux, and Windows CS-3013 Operating Systems (Slides include materials from.
UNIX and Shell Programming (06CS36) Unit 1 Continued… Shrinivas R. Mangalwede Department of Computer Science and Engineering K.L.S. Gogte Institute of.
Linux+ Guide to Linux Certification, Third Edition
Additional UNIX Commands. 222 Lecture Overview  Multiple commands and job control  More useful UNIX utilities.
Shell Scripting AFNOG IX Rabat, Morocco May 2008.
UNIX Commands. Why UNIX Commands Are Noninteractive Command may take input from the output of another command (filters). May be scheduled to run at specific.
1 Week 2 The Crunchy Shell to the Soft and Chewy Kernel… Sarah Diesburg 8/3/2010 COP4610 / CGS5765.
1 CSE 451 Section 2: Interrupts, Syscalls, Virtual Machines, and Project 1.
Unix/Linux cs3353. The Shell The shell is a program that acts as the interface between the user and the kernel. –The shell is fully programmable and will.
Lecture 24CS311 – Operating Systems 1 1 CS311 – Lecture 24 Outline Final Exam Study Guide Note: These lecture notes are not intended replace your notes.
System calls for Process management
4.1 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Project1: Unix Shell with History Feature Goals Descriptions Methodology Submission.
Operating Systems Process Creation
Fall 2002 CS 325 Class Notes Page 1 Lecture 25 Today –exec() in Unix –CreateProcess in Windows Announcements.
Week Two Agenda Announcements Link of the week Use of Virtual Machine Review week one lab assignment This week’s expected outcomes Next lab assignments.
Lesson 3-Touring Utilities and System Features. Overview Employing fundamental utilities. Linux terminal sessions. Managing input and output. Using special.
Linux Commands C151 Multi-User Operating Systems.
The Process CIS 370, Fall 2009 CIS UMassD. The notion of a process In UNIX a process is an instance of a program in execution A job or a task Each process.
1 CSE 451 Section 2: Processes, the shell, and system calls.
Agenda The Bourne Shell – Part I Redirection ( >, >>,
CS241 Systems Programming Discussion Section Week 2 Original slides by: Stephen Kloder.
CS 403: Programming Languages Lecture 20 Fall 2003 Department of Computer Science University of Alabama Joel Jones.
CS241 Systems Programming Discussion Section Week 2 Original slides by: Stephen Kloder.
Linux Tutorial Lesson Two *Getting Help in Linux *Data movement and manipulation *Relative and Absolute path *Processes Note: see chapter 1,2,3 from Linux.
CSE 451 Section Autumn 2004 Alex Moshchuk Office hours: Tue 2-3, Thu 4:30-5:30 Allen 216 (or lab)
1 Intro to the Shell with Fork, Exec, Wait Sarah Diesburg Operating Systems CS 3430.
The Shell What does a shell do? - execute commands, programs - but how? For built in commands run some code to do the command For other commands find program.
CSE 451 Section #3 Project 0 Recap Project 1 Overview
Implementation of a simple shell, xssh
Implementation of a simple shell, xssh (Section 1 version)
CSE 451 Section 2: Processes, the shell, and system calls
Implementation of a simple shell, xssh
Shell Script Assignment 1.
Processes in Unix, Linux, and Windows
INTRODUCTION TO UNIX: The Shell Command Interface
Basic UNIX OLC Training.
Processes in Unix, Linux, and Windows
CS-3013 & CS-502 Operating Systems Summer 2006
Processes in Unix, Linux, and Windows
Programming Project #1 Command Shell
Programming Project #1 Fork and Command Shell
Alternate Project #4 Process and Thread Performance
Lecture 6: Multiprogramming and Context Switching
Processes in Unix, Linux, and Windows
Processes in Unix and Windows
EECE.4810/EECE.5730 Operating Systems
EECE.4810/EECE.5730 Operating Systems
Intro to the Shell with Fork, Exec, Wait
Presentation transcript:

Project 1, Command Shell CS-502 (EMC) Fall Programming Project #1 Command Shell CS-502, Operating Systems EMC, Fall 2009 (Slides include materials from Modern Operating Systems, 3 rd ed., by Andrew Tanenbaum and from Operating System Concepts, 7 th ed., by Silbershatz, Galvin, & Gagne)

Project 1, Command Shell CS-502 (EMC) Fall Purpose To practice using the fork and exec facilities of Unix/Linux To learn how to find and use on-line documentation about system calls and system facilities. man pages To become accustomed to speaking directly with the operating system

Project 1, Command Shell CS-502 (EMC) Fall Programming Assignment Build a command shell capable of running commands in the background:– 1.Write a command called doit to execute another command and print out statistics 2.Adapt doit to become a basic shell that prompts for and executes commands 3.Modify your shell to become shell2 to execute commands in the background

Project 1, Command Shell CS-502 (EMC) Fall Part 1: doit doit command:– Take another command line as argument Execute that command Print out statistics about command Must compile and execute on your virtual machine Likely to be compatible with most modern Linux systems Useful system calls and functions:– fork(), execvp(), wait() getrusage(), gettimeofday() May not use system() system call Use execvp(), not execve()

Project 1, Command Shell CS-502 (EMC) Fall Part 1 (sample output) %./doit cat /etc/motd /* print the current message of the day */ /* statistics about the cat command */ %./doit ls –l /usr/src /* list contents of the /usr/src directory */ /* statistics of the ls command */ %./doit cp –al /usr/src/linux kernelSrc /* output of the cp command (if any) */ /* statistics of the cp command */

Project 1, Command Shell CS-502 (EMC) Fall doit Implementation Hint Command line is already tokenized in argv Strip off the 0 th element of argv vector Pass the remainder of argv to exec() for arguments of command

Project 1, Command Shell CS-502 (EMC) Fall Part 2: shell Repeatedly prompt for command lines Execute each command and print out statistics, as in doit Implement special “built-in” commands exit cd dir Special conditions Input from stdin Exit on end of file Complain about illegal commands Check for line length, number of arguments

Project 1, Command Shell CS-502 (EMC) Fall Part 2 output % shell ==>cat /etc/motd /* print the current message of the day */ /* statistics about the cat command */ ==>cd dir /* current directory is changed to dir */ ==>ls –l /boot /* listing of files in /boot directory */ /* statistics about this ls command */ ==>exit %/* back to your previous Linux prompt */ % shell < filename.txt /* reads, echoes, and executes each command/* /* statistics about each command */ /* exits after last command is completed */

Project 1, Command Shell CS-502 (EMC) Fall shell Implementation Hints Input command line May limit to 128 characters, 32 arguments Must tokenize — use strtok() function Built-in commands are not handled by fork and exec Must be executed “in-line” in shell getrusage() returns cumulative statistics For all children of this process Must remember and subtract previous values to get statistics for most process most recently waited for

Project 1, Command Shell CS-502 (EMC) Fall Part 3: Background Execution ( shell2 ) Modify shell to allow commands to execute in background, indicated by ‘&’ character Causes shell to prompt for next command before previous command is complete jobs built-in command lists background tasks in progress Modified wait() call Returns immediately if nothing has terminated Returns PID if any process has terminated Report completion of command at next opportunity –I.e., the next time user types a command, or whenever wait() returns PID of the command

Project 1, Command Shell CS-502 (EMC) Fall Part 3 output % shell2 ==>make –j4 O=~/kernelDst & [1] /* indicate background task #1, process id */ ==>jobs [1] make /* print process id and command name for tasks */ ==>ls /* listing of files in the current directory */ /* statistics about this ls command */ ==>cat /etc/motd [1] make Completed /* statistics about background job */ /* print the current message of the day */ /* statistics about this cat command */ ==>exit %/* back to your previous Linux prompt */

Project 1, Command Shell CS-502 (EMC) Fall shell2 Implementation Hints Use wait3() to Wait for any process Wait without blocking – WNOHANG option Get usage information directly After fork(), shell2 does while (pid = wait3(WNOHANG)) { print msg & statistics of pid update list of outstanding tasks } if (latest not background && latest not done) wait3(latest_pid);

Project 1, Command Shell CS-502 (EMC) Fall Work environment Program in C Even though it could easily be done in C++ You may work on any Linux system E.g., your own or corporate environment We will grade it on openSUSE 11.1 I.e., your virtual machine environment Note: –Linux systems are often compatible with each other –However, not all C/C++ compilers and Linux kernels are alike –Some may produce or ignore compiler warnings –Your virtual machine is the one that counts

Project 1, Command Shell CS-502 (EMC) Fall Project submission Due Monday, October 5, 11:59 PM Submit via web-based myWPI Project name = Project 1 Put your name at top of every file! (You would be surprised how many students forget!)

Project 1, Command Shell CS-502 (EMC) Fall Project Submission (continued) Code of your solution A single Makefile make clean make all make doit make shell make shell2 Test cases for each part Write-up explaining everything Especially how you keep track of outstanding processes in shell2 Do –Zip everything together DO NOT –Put different parts of project in separate folders –Create different Makefiles for different parts

Project 1, Command Shell CS-502 (EMC) Fall Grading Ten point project Three points for each part Point allocation per part Correct compilation and build; no warnings! – 1 pt. Correct execution of graders’ test cases – 1 pt. Submission and correct execution of own test cases – 1 pt Write-up explaining what you did and your results 1 pt MS Word or PDF No credit for a part if it fails to build

Project 1, Command Shell CS-502 (EMC) Fall Not a team project! Each student must submit own solution Encouraged to discuss general approach, meaning of system calls, etc., with friends Encouraged to seek help if puzzled by some concept, system call, etc. Distill all discussions into your own work!