Unix Progamming Lab Schedule for III MCA Odd Semester 2011

14. Create a file and read, write operations using different child process
20Aug

15. Demonstrate data sharing between process using Files 16. Implement sorting using pipes

3Sep

17. Demonstrate FIFOs 18. Implement Message Queues

Date
25Jun

Program
10. Write a Shell Script to check whether the given number is odd or even and whether is +ve, -ve or zero. 2. Write a script to find the number of unique words in a list of words stored in a file. 3. Write a script function that displays all shell default parameters.
10Sep

19. Demonstrate Semaphores 20. Demonstrate Threads

12/09/11 - Report Submission

Students 1-10 11-20

Lecturer-in-charge Chandra.J Dr.Nachamai.M

9-Jul

4. Write a script to convert a decimal number to its binary equivalent and vice-versa. 8. Write a script to check your home directory to display how many files, directories, and sub-directories are there and display it. 5. Write a script to encode and decode a text file. 6. Write a script to compute the factorial value with and without using recursive functions.

Programs: 80% Exercises/ Tests: 20%

23-Jul

7. Write a script to send a text file to group of users. 9. Write a Shell Script to prepare and display the Electricity bill with significant considerations. 1. Write a script to find the number of days between two given dates using functions.

Each Program is for 5 marks Timely Completion: 1 Mark Complexity of Program: 2 Mark Good Understanding: 1 Mark Observation Book: 1 Mark.

30-Jul

11. Demonstrate fork(), kill(), sleep() system calls 12. Demonstrate explicit locking and unlocking on a file using lockf()

13Aug

13. Demonstrate process synchronization

Observation Book: This book is meant for planning what will be done in the lab. Each program should have Date of writing, Date of coding, Date

of completion. Write Pseudo Code. Syntax of commands relevant for the script/code. There should be sections marked for observation and testing strategy (N.B) If code is written in this book it should not be used while implementation in class (N.B) Zero out of five if delayed by more than a month Guidelines y Use of VI editor is encouraged. Please get use to the same before Mid Sem Exams. y Use Good Naming Conventions y Indent Programs y Add appropriate comments y Copying code from each other is strictly discouraged y Use of Internet Resources is encouraged but cut copy will be counter productive. y Think First Google Later y Use Sumitabha Das or Kernigan & Pike , Wikipedia y Help each other in coding in terms of debugging, understanding, teaching is the best way to learn y Any technical doubts please do not hesitate to ask the Unix Theory Teacher or Lab In Charges. y Students who are good in coding are encouraged to code much before schedule and move on to advanced coding in August y Get comfortable using different shell commands like grep, cut, diff, wc , date, find, awk and sed