Professional Documents
Culture Documents
LECTURE 1: INTRODUCTION
Instructors
Introduction
4 August 2012
Policies to Follow
Class Room LT4 No entry after 10:05 A.M (No excuses Please) No entry after 8:05 A.M (For tutorials) No mark for attendance (Attend if and only if you are really interested!!) Not allowed to leave in between the class All tutorials are converted to lecture sessions
4 August 2012
Tests
Course Administration
Test 1
Day,Date & Time: Thursday, 16 09 2012 Weightage: 15% Mode: Closed Book Day,Date & Time: Thursday, 29 10 2012 Weightage: 15% Mode: Closed Book Medical certificate from the doctor (Dr. Ragvendra) Photocopy of the medical reports & Bills
Test 2
Make-up Policy
4 August 2012
Course Administration
No Surprise Quizzes
No Marks for attending classes Attend the Lectures and Tutorials only if
You are motivated enough You can enter the class before 10:05 / 8:05 and You can dress decently
Assignment(s) / Online(s)
Programming in Nature with 35% weightage All deadlines are hard deadlines
Late submission is same as NO submission No submission is OK & is advisable over MALPRACTICE MALPRACTICE regulations strictly apply [See Handout]
Biju K Raveendran@BITS Pilani. 5
4 August 2012
Course Administration
Comprehensive Examination
Day, Date & Time: 10 12 2012 (AN) Weightage: 35% Mode: Closed Book
4 August 2012
Course Administration
Material:
http://10.1.1.242/moodle/
Text Book:
Abraham Silberschatz, Peter Baer Galvin & Greg Gagne Operating System Concepts, 8th edition, John Wesley & Sons, 2008.
Reference Book:
William Stallings, Operating Systems Internals and Design Principles, 6th edition, Pearson Edition, 2009. Maurice J. Bach, The Design of the Unix Operating System, PHI, 1993.
Note: Make it a habit to visit photon. The course page will be updated on a daily basis
Biju K Raveendran@BITS Pilani. 7
4 August 2012
Introduction
Single most complex and essential software you run on your machine Interface between the user and the computer hardware Helps user programmer by making the system easier (convenient) to use Helps the programs run by providing resources and protecting them Helps the system by keeping things running smoothly Helps the user programmer to do his job efficiently (use computer hardware efficiently)
Biju K Raveendran@BITS Pilani. 8
4 August 2012
4 August 2012
Manage/coordinate hardware resources so that the system operates smoothly, efficiently, reliably and securely Present abstract system model to programmer that promotes simple and convenient access and control of resources Maximize resource utilization Operating system must contain functions needed by many programs
I/O device control, memory allocation etc. Selection of function must be in such a way that maximum number of programs must get the benefit at the same time operating system must not become bulky
4 August 2012
10
Load the program into memory Run the program in processor Store the result in persistent storage and Unload the program to release memory [for the next program to use]
For doing all these functions we need at least a minimal OS It must be the resident code that run by default Allow us to load program and run by allotting necessary resources After completion of the user program control must come back to the operating system
Biju K Raveendran@BITS Pilani. 11
4 August 2012