Operating Systems (Lab) — What This Subject Is About
Twelve experiments, one per idea in the theory paper — that is what this lab is. Operating Systems (Lab) is the practical companion to Operating Systems (subject 3.1): you write the programs that simulate what the theory describes — CPU scheduling, deadlock, page replacement, disk scheduling — and you run them yourself. There is no theory paper: your marks come from practical work, 60 internal and 40 external.
The lab has 2 practical periods a week and 1 credit. The experiments run in the same order as the theory units: Linux commands and Windows installation first, then process management, then memory management, then the I/O system, then file systems. The lab only makes sense alongside the theory — read the unit first, then simulate it.
Subject 3.5 (Practical) • Total 100 Marks • 1 Credit • L 0 – P 2 • 3rd Semester — Information Technology • Session 2026–27

What You Will Do
List of Experiments — 12 Experiments
| S.No. | Name of Experiment |
|---|---|
| 1 | Practice of various Linux/Unix commands like man, cp, mv, ln, rm, unlink, mkdir, rmdir, etc. |
| 2 | Format and install Windows Operating System. |
| 3 | Use Task Manager to monitor and terminate processes. Understand process priorities. |
| 4 | Simulate the following CPU scheduling algorithms: (a) FCFS (b) SJF (c) Round Robin (d) Priority. |
| 5 | Simulate the concept of Dining Philosophers problem. |
| 6 | Simulate Bankers Algorithm for Deadlock Avoidance. |
| 7 | Simulate Bankers Algorithm for Deadlock Prevention. |
| 8 | Write a program to simulate the following contiguous memory allocation techniques: (a) Worst Fit (b) Best Fit (c) First Fit. |
| 9 | Simulate all page replacement algorithms: (a) FIFO (b) LRU (c) OPTIMAL. |
| 10 | Write a program to simulate disk scheduling algorithms: (a) FCFS (b) SCAN (c) C-SCAN. |
| 11 | Simulate all file organization techniques: (a) Single level directory (b) Two level directory. |
| 12 | Simulate all file allocation strategies: (a) Sequential (b) Indexed (c) Linked. |
Experiments 6 and 7 both name the Bankers Algorithm; the syllabus lists avoidance and prevention as two separate experiments, reproduced as printed.
Complete Syllabus
The full examination scheme, the course outcomes and the reference books from the official syllabus. The experiments are in the “What You Will Do” section above.
Examination Scheme
| Code | Paper | Type | L – P | Credits | Internal | External | Total |
|---|---|---|---|---|---|---|---|
| 3.5 | Operating Systems (Lab) | Practical | 0 – 2 | 1 | Practical 60 | Practical 40 (3 hrs) | 100 |
| Operating Systems (Lab) Total | 1 | 60 | 40 | 100 | |||
Course Outcomes
- CO1: Understand installation of operating system.
- CO2: Understand process management and distinguish CPU scheduling algorithms.
- CO3: Understand the concept of memory management.
- CO4: Understand I/O System and distinguish Disk scheduling algorithms.
- CO5: Classify File System and directory implementations.
Reference Books
The official syllabus lists no reference books for this laboratory. Use the reference books of the matching theory subject, Operating Systems (subject 3.1).
How to Prepare for Operating Systems (Lab)
Learn the Linux commands by using them daily. Experiment 1 is a list of commands — man, cp, mv, ln, rm, unlink, mkdir, rmdir — and the only way to learn them is to use them. Do your file work in the terminal for a week and the commands become automatic. A command you have used fifty times needs no revision.
Work the algorithm by hand before you code it. For every simulation experiment, first work a small example on paper: a scheduling table, a page reference string, a disk queue. Then write the program, and check its output against your hand calculation. If the two disagree, the hand calculation is usually right and the program has the bug.
Keep one tested program per experiment. Write each simulation as its own program, test it on the example from the theory, and save it with a clear name. A folder of twelve working programs is your lab record in its most useful form — and the best revision for the external practical examination.
Keep the record complete and up to date. Write up each experiment in the week you do it: the aim, the algorithm, the program, the output, and one line on what you learned. The 60 internal marks rest on your practical work through the semester, and a record written in the last week is obvious to any examiner.
Practise the viva, not just the code. The external practical includes questions about your programs: what FCFS does differently from SJF, why Bankers Algorithm is safe-state checking, what a page fault costs. Be able to explain every program you submit in two or three sentences.
Practical Exam Tips
- Run every program once more the day before the exam. A program that worked last month may not compile today if a file moved. Test all twelve before the examination, not during it.
- Know your code well enough to rewrite it. The external practical may ask you to write a simulation from scratch. If you understand the algorithm, the code follows; if you only memorised the code, one forgotten line stops you.
- Show your hand calculation with the output. In the viva, a hand-worked example beside the program output proves you understand the algorithm, not just the code.
- Keep your files organised. One folder per experiment, named clearly. In a 3-hour practical examination, the student who can find their programs finishes; the student who cannot, does not.
- Save your work as you go. Save after every change that works. A power cut or a crash in the last half hour should cost you minutes, not the whole examination.
Frequently Asked Questions
How many marks is Operating Systems (Lab) worth in the 3rd semester?
100 marks in total and 1 credit: internal assessment 60 marks (practical) and external practical examination 40 marks in 3 hours. There is no theory paper.
How is the lab related to the Operating Systems theory subject?
It is the practical companion to subject 3.1 Operating Systems. The experiments follow the theory units in order: Linux and Windows (Unit 1), CPU scheduling and deadlock (Unit 2), memory allocation and page replacement (Unit 3), disk scheduling (Unit 4), and file organization and allocation (Unit 5).
How many experiments are there in the OS Lab?
Twelve, listed in full in the “What You Will Do” section above and in the free syllabus PDF below.
Which experiments matter most?
The simulation experiments carry the most weight in the viva and the external practical: CPU scheduling (experiment 4), Bankers Algorithm (experiments 6 and 7), page replacement (experiment 9) and disk scheduling (experiment 10). But all twelve experiments are in the syllabus, and the record should be complete.
Which books should I refer to for the OS Lab?
The official syllabus lists no reference books for the laboratory. Use the reference books of the matching theory subject, Operating Systems (subject 3.1) — including Operating System Concepts by Silberschatz and Galvin.
How can I download the OS Lab syllabus PDF?
The PDF is free to download — use the download link in the Download section below. It is prepared by KAMALDNP from the official BTEUP syllabus.
Related Syllabus Posts
- Operating Systems — BTEUP IT 3rd Semester Syllabus 2026-27
- Database Management System — BTEUP IT 3rd Semester Syllabus 2026-27
- Software Engineering — BTEUP IT 3rd Semester Syllabus 2026-27
- Web Technologies — BTEUP IT 3rd Semester Syllabus 2026-27
- Computer Programming Using C — BTEUP IT 3rd Semester Syllabus 2026-27
- Database Management System (Lab) — BTEUP IT 3rd Semester Syllabus 2026-27
- Summer Internship-I — BTEUP IT 3rd Semester Syllabus 2026-27
- All BTEUP Syllabus Posts — kamaldnp.com Blog
- KAMALDNP Books — Short Notes, Question Banks & Practice Sets
Notes, Question Bank & Practice Sets
There are no Short Notes, Question Bank or Practice Sets for this subject — it is a practical subject with no theory paper, so that kind of study material does not apply. The complete syllabus PDF below is free, and it is everything you need to know what to practise.
Download the Operating Systems (Lab) Syllabus PDF
Download the complete Operating Systems (Lab) syllabus PDF below — prepared by KAMALDNP, with the full topic list, examination scheme and reference books.
Download the Operating Systems (Lab) Syllabus PDF
Source: BTEUP IRDT Kanpur NEP-2020 curriculum for Diploma in Information Technology, effective session 2026-27 (urise.up.gov.in). Topic lists follow the official syllabus; short explanations are the author's own plain-English summaries, not syllabus text. Please confirm with your own polytechnic for any local changes.
Comments (0)
Share your question or experience about this syllabus. Your comment will appear after review.
No comments yet — be the first to share your thoughts!