CS 324: Introduction to Operating System

Course Information and Syllabus

Class Meetings

Instructor

Class web site

Prerequisites

CS 216

Gettysburg Curricular Goals

Text

Operating Systems: Three Easy Pieces by Remzi H. Arpaci-Dusseau ,Andrea C. Arpaci-Dusseau, and Peter Reiher. Available free online.

Topics

Learning Outcomes

• Be able to trace a process through its life cycle in a computer.
• Be able to explain the objectives and functions of an operating system.
• Be able to explain fundamental OS related algorithms and data structures.
• Be able to describe the effects and demands concurrency places on an operating systems.
• Be able to identify and trace through scheduling algorithms.
• Be able to describe the functionality of various components of an OS.
• Be able to write code with thread synchronization constructs.
• Be able to write utilities with bash scripts.
• Be able to decode memory addresses using paging and segmentation.

Course Credit

The federal government defines a credit hour as the equivalent amount of work as 50 minutes in class and two hours out of class for one semester.

Therefore, this course should be the equivalent work of three hours and twenty minutes in class and 8 hours outside of class. Since the course meets two and a half hours per week, the assignments include a "fourth hour" item each week.

Attendance Policy

Grading Policy

Assignments

Homework will be due at the beginning of class. Late work will be graded with a 20% deduction. Homework turned one week after the deadline will receive no credit. Homework will be graded by the second class meeting or one week after they are submitted, whichever is later. Otherwise, all students who have turned the assignment in on time will receive a 10% bonus.

Unless otherwise specified, all assignments are weighted equally. Some assignments may count double. Such changes will be noted on the assignment specifications.

Classwork

From time to time you will be asked to write programs, complete worksheets, take quizzes, give short presentations, or answer questions in class.

Fourth Hour

Fourth Hour assignments require an additional exercise outside of class meeting times.

Colloquium Attendance

Each student is required to attend at least two Computer Science Colloquia during the semester. If your schedule does not permit you to attend one or more, please see me to discuss an alternative.

Tests

There will be 2 tests during the semester, their dates are given in the schedule below. Make-up tests will only be given under special circumstances. The final exam is cumulative. The date is determined by the registrar.

The tests and the final will be proctored in the classroom.

Grade Distribution

Grade Ranges

Honor Code and Honor Code Violations

Guidelines for following the honor code:

• Do not represent anyone else's work as your own.
• Do not search the Internet (or any other source) for solutions to the assignments unless told to do so.
• When an assignment requires that you search for an answer, provide references to your sources.
• Do not share your work with other students, unless you are working on a group project.
• You may ask a fellow student for help if you get stuck, and they may provide advice, but they may not provide a complete or partial solution.
• Tests and the final exam will taken in class and will be proctored.

Generative AI Tools

Generative AI tools such as ChatGPT can be powerful aids to completing a variety of work. You will undoubtedly use them in your careers. They will likely become the de-facto standard for building computer applications in the future.

In this course, we may employ these tools from time to time, both in class and work you do alone. However, you may not use them for any submitted work unless there are specific instructions to do so. Using these tools on assignments without permission is a violation of the Honor Code.

You should aim to be more than just a communication device between your professor and ChatGPT. You improve your problem solving ability by thinking (practice makes perfect).

You may use AI to...

• search for information.
• summarize information.
• check writing style and grammar.
• create examples and practice problem.
• generate data sets for program testing.
• create study materials.
• assist in compose emails.
• plan and organize.

You may not use AI to...

• search for answers on tests or assignments.
• generate answers for you, unless specifically told to do so.
• generate data which you are assigned to collect.
• analyze private or personally identifiable information.
• analyze copyrighted information.
• avoid putting in an effort.
• replace your own thought processes.
• remove yourself from your education.

I may use AI to...

• generate problems.
• generate examples.
• generate sample data sets.
• produce or enhance class materials.
• organize/facilitate grading.

I will not use AI to...

• grade or assess your work.
• analyze private or personally identifiable information.
• analyze copyrighted information.
• replace my expertise as your teacher.
• remove myself from your education.

We are responsible for...

• knowing when and if generative AI is applicable, appropriate, and acceptable. Some classes or employers may forbid, limit, or encourage its use.
• understanding programs generated by AI. If you can't read it, you don't know what it does.
• documenting our development process.
• testing our programs in a safe environment.
• the efficiency and security of the programs we specify. AI generators may not always choose the best or safest algorithms and data structures.
• adhering to required coding standards which includes naming conventions and formatting among other things.
• protecting private or proprietary information. Unless there is a reason to believe otherwise, assume any information sent to an LLM is exposed to the public.

If we generate a program using AI tools which contains bugs and errors, they are OUR bugs and errors. If the program infringes a copyright or patent, that is our violation. We are responsible for the consequences that follow.