Click here to see a PREVIEW of important rules that was posted before the semester started.

This is an undergraduate course on computer operating systems. (But only graduate students are permitted to be in this class. USC undergraduate students must take CS 350 in order to get credit for OS. If you are an undergraduate student, you cannnot be in this class and you cannot get credit for Operating System if you take this class. Please check with your adviser to see which Operating System class you need to take!) In addition to exploring concepts such as synchronization, virtual memory, processes, file systems and virtualization, students will develop elements of a fairly complete operating system during the course of the semester.
 

General Information
Instructor Bill Cheng (click to see office hours)
E-mail: <bill.cheng@usc.edu>.  (Please do not send HTML-only e-mails. They will not be read.)
  DEN Section (29945D+29946D) TT Section (30331D)
Time MW 9:30am - 10:50am  TT 9:30am - 10:50am 
Location OHE 100D  WPH B27 
TA Zhuojin Li, E-mail: <zhuojinl@usc.edu>
Office Hours: Wed 4:00pm-5:00pm and Fri 10:50am-11:50am on Zoom 		Jianfeng Wang, E-mail: <jianfenw@usc.edu>
Office Hours: Fri 1:50pm-2:50pm on Zoom
Graders
Anish Deshmukh, E-mail: <anishdes@usc.edu>
Vasudha Bhanudas Mahajan, E-mail: <vasudhab@usc.edu>
(If needed, the grader will hold office hours the week after the announcement of each assignment's grades.)
Midterm Exam (NEW) [9:30:00am-10:10:00am), Wed, 3/22/2023 (firm) (NEW) [9:30:00am-10:10:00am), Thu, 3/23/2023 (firm)
Final Exam (NEW) [9:00:00am-9:40:00am), Fri, 5/5/2023 (firm) (NEW) [9:00:00am-9:40:00am), Tue, 5/9/2023 (firm)
Class Resources
Description   :   textbooks, topics covered, grading policies, additional resources, etc.
Lectures   :   information about lectures (and lectures slides in PDF format).
Videos   :   information about lectures and discussion sections videos on D2L.
Discussions   :   information about discussion sections.
Projects   :   programming assignments (please also see important information about the class projects below.)
Forum   :   Google Group online forum for discussing course materials and programming assignments. All important announcements will be made using this online forum. Therefore, you are required to be a member of this group. (This group is by invitation only and you need to make sure that you are a member.) Please do not send request to join this group until after Lecture 1.
News
(in reversed chronological order)
  • 5/6/2023:
    • Below is the grade normalization information for kernel3. Please note that this only applies to the grader-dependent part of your grade. If you are graded by Anish Deshmukh <anishdes@usc.edu>, his kernel3 average was 94.31 with a standard deviation of 13.74. If you are graded by Vasudha Bhanudas Mahajan <vasudhab@usc.edu>, her kernel3 average was 94.27 with a standard deviation of 15.33. The overall class average for kernel3 was 94.29 with a standard deviation of 14.52.

      To figure out your normalized score for kernel3, here's what you can do. If your grader-dependent part of your grade is X and your grader's average is A, your normalized grader-dependent part of your grade would be X+(94.29-A). Your minimum score is still one point if you have submitted something for grading.

      As I have mentioned in Lecture 1, although we assume that we have a bell-shaped curve, when your score is normalized, linear interpolation is used. It's clearly not perfect since the actual curve will never be bell-shaped and linear interpolation is not the same as bell-shaped-curve interpolation. But this is what was announced, and therefore, we will stick to this particular way of normailzation for all the programming assignments for the rest of the semester, knowing that it's not perfect.

  • 5/1/2023: Below are the links for starting the final exams. These links will become active approximately 3 minutes before the respective exam start time and you can start working on the exam as soon as you have downloaded the exam.

    Plesae make sure you have done the following:

  • 4/26/2023: The final exam will be a 40-minute long take-home exam (open book and open notes), and it will be conducted in the same manner as the midterm exam (please refer to the 3/17/2023 news item for the basic procedure and replace the date and time with what's appropriate for your final exam, e.g., X in the image is now 9). No matter how late you start your exam, your exam must end at the same time as everyone else who is taking the same exam.

    The final exam will cover everything from slide 30 of the 2nd part of Lecture 13 to slide 53 of the 2nd part of Lecture 15, PLUS, from slide 43 of the 2nd part of Lecture 17 to the last slide of Lecture 29. Also included are discussion section materials from Week 8 through Week 13.

    Since the 2nd part of the course depends on stuff covered by the midterm, I cannot say that I will not ask anything covered by the midterm and you do need to know the material covered by the midterm. Therefore, it would be more appropriate to say that the final exam will focus on the material not covered by the midterm.

    Regarding what types of questions will be on the exam, please see the Exams section of the course description web page. Regarding regrade policy, please see the Regrade section of the course description web page.

    Please note that if you are asked to run the Stride Scheduling algorithm, to get any credit, you must run the algorithm described in Lecture 28 (and not the one in the textbook).

    Here is a quick summary of the final exam topics (not all topics covered may be listed):

    • Ch 3 - Basic Concepts
      • shared libraries
    • Ch 4 - Operating-System Design
      • devices
      • virtual machines, microkernels
    • Ch 5 - Processor Management
      • threads implementation strategies
      • threads implementations
      • interrupts
      • scheduler activations model
      • scheduling
    • Ch 6 - File Systems
      • the basics of file systems
      • performance improvements
      • crash resiliency
      • directories and naming
      • RAID, flash memory, case studies
    • Ch 7 - Memory Management
      • virtual memory
      • OS issues
    • Kernel assignments 2 & 3
      • discussion section slides
      • spec
      • FAQ
      • my posts to class Google Group
  • 4/25/2023: Please download, fill out, sign, and submit the Final Exam Academic Integrity Honor Code Pledge as soon as possible. Please understand that if I don't get a signed pledge from you, I will not send a final exam to you because I need you to promise me that you won't cheat before I can send you an exam.
  • 4/20/2023:
    • Below is the grade normalization information for kernel2. Please note that this only applies to the grader-dependent part of your grade. If you are graded by Anish Deshmukh <anishdes@usc.edu>, his kernel2 average was 97.13 with a standard deviation of 4.12. If you are graded by Vasudha Bhanudas Mahajan <vasudhab@usc.edu>, her kernel2 average was 96.32 with a standard deviation of 8.38. The overall class average for kernel2 was 96.75 with a standard deviation of 6.49.

      To figure out your normalized score for kernel2, here's what you can do. If your grader-dependent part of your grade is X and your grader's average is A, your normalized grader-dependent part of your grade would be X+(96.75-A). Your minimum score is still one point if you have submitted something for grading.

      As I have mentioned in Lecture 1, although we assume that we have a bell-shaped curve, when your score is normalized, linear interpolation is used. It's clearly not perfect since the actual curve will never be bell-shaped and linear interpolation is not the same as bell-shaped-curve interpolation. But this is what was announced, and therefore, we will stick to this particular way of normailzation for all the programming assignments for the rest of the semester, knowing that it's not perfect.

  • 4/17/2023: Office hour tomorrow (Tue, 4/18) is moved to 2:30-3:30pm. Sorry about the inconvenience and short notice.
  • 4/11/2023: Zhuojoin will be out of town between 4/13 and 4/20. So, he is moving his office hour this Friday (4/14) to 4-6pm tomorrow (4/12). He is also moving his office hour next Wednesday (4/19) to 11am-1pm next Friday (4/21). This Friday's discussion section at 10am in OHE 136 will be lead by Jianfeng (and Jianfeng Wang's 1pm discussion is canceled). Sorry about the inconvenience and short notice.
  • 3/30/2023: Today's TT section primary live lecture is cancelled. Please watch today's DEN section video. We will go straight into the secondary live lecture today. Please see my post in the class Google Group. Sorry about the inconvenience and short notice.
  • 3/23/2023:
    • Below is the grade normalization information for kernel1. Please note that this only applies to the grader-dependent part of your grade. If you are graded by Anish Deshmukh <anishdes@usc.edu>, his kernel1 average was 93.66 with a standard deviation of 5.70. If you are graded by Vasudha Bhanudas Mahajan <vasudhab@usc.edu>, her kernel1 average was 94.02 with a standard deviation of 8.15. The overall class average for kernel1 was 93.87 with a standard deviation of 7.24.

      If your grader-dependent part of your grade is X and your grader's average is A, your normalized grader-dependent part of your grade would be X+(93.87-A). Your minimum score is still one point if you have submitted something for grading.

      As I have mentioned in Lecture 1, although we assume that we have a bell-shaped curve, when your score is normalized, linear interpolation is used. It's clearly not perfect since the actual curve will never be bell-shaped and linear interpolation is not the same as bell-shaped-curve interpolation. But this is what was announced, and therefore, we will stick to this particular way of normailzation for all the programming assignments for the rest of the semester, knowing that it's not perfect.

  • 3/22/2023: Something came up and I have to move my office today to 9-10pm tonight. Very sorry about the inconvenience and short notice.
  • 3/21/2023: As mentioned in my post to the class Google Group yesterday, today's primary live lecture has been cancelled. Please watch the recording of yesterday's DEN section live lecture for the administrative information and recap of lecture videos. We will go straight into the secondary live lecture today.
  • 3/20/2023: Below are the links for starting the midterm exams. Currently, they are inactive/invalid. They will become valid and active approximately 3 minutes before the respective exam start time and you can start working on the exam as soon as you have downloaded your exam.

    Plesae make sure you have done the following:

    No matter how late you start your exam, your exam must end at the same time as everyone else who is taking the same exam.

  • 3/19/2023: I won't be able to hold tomorrow's office hour at 3pm. Therefore, I'm moving tomorrow's office hour to 9:00-10:00pm. Sorry about the short notice and inconvenience.
  • 3/17/2023: Midterm rehearsal will be on Monday, 3/20/2023 at 10:30am (i.e., rehearsal start time is 10:30:00) USC time. The starting point of your midterm rehearsal is at:

    Currently, the above link is inactive/invalid. It will become valid and active about 3 minutes before the rehearsal start time.

    Below is the instructions for the midterm rehearsal (this will also be the instructions for your midterm exam, with a different start time and start page). I have gone over all the information below during live DEN section Lecture 18 on 3/8/2023.

    Below, we will use the notation that the midterm rehearsal starts at X:30:00 and ends at (X+1):10:00 (for the midterm rehearsal, X = 10; for the actual midterm, X = 9 for both sections). As mentioned in live DEN section Lecture 18 on 3/8/2023, the left side of a time interval is "closed" (i.e., including the left timestamp) and the right side of a time interval is "open" (i.e., up to but not including the right timestamp). If your exam time is different, please make adjustments accordingly.

    • Make sure you have setup an e-mail filter to never miss an e-mail from <bill.cheng@usc.edu> (and never have it go into your spam folder).

    • To get ready, please do the following 5 minutes BEFORE X:30:00.
      • Display a clock app and a web browser as shown.
      • Make sure you have downloaded and installed the Panopto Recorder. If you have an offline desktop recorder that can record your desktop into an MP4 file, you can use that instead of the Panopto Recorder.
      • Start the Panopto Recorder just in case you may lose Internet connection later. Make sure Panopto is configured correctly (see the Checklist). Don't start recording your desktop yet.
      • Have your submission PIN handy because you will need it later. (Your submission PIN is the same for all programming assignments and exams.)
      • Set an alarm for (X+1):09:00 to remind yourself that the exam is about to end soon (and make sure the time on your alarm clock is correct).
      • If your machine is known to crash from time to time, you should reboot your machine and don’t run anything you don’t need for your exam.

    • About 3 minutes before X:30:00, click on the midterm rehearsal start page mentioned above to start your midterm rehearsal.
      • Follow the instruction and enter your USC Net ID and your submission PIN and click on submit. Please remember that your submission PIN is the same as your programming assignments submission PIN.
      • In the next page, there are 2 links:
        • The first link is for downloading a ZIP file which contains the exam questions (PDF file) and an answers text file. Click on it to download the ZIP file and then open it. (With some browsers, you will have to copy the link and paste it into a new browser tab in order for download to be successful; with some other browsers, they will simply save all your downloads in a default folder, such as the Downloads folder, so you should also check there.) Save the answers text file on your desktop for easy access (don't make a copy of it, just work on this copy so you won't end up submitting the wrong file).
        • The second link is for submitting your answers text file when you are done. You should click on it immediately to open a new tab in your browser and look at the submission web page. Right above the submission web form, you should see the current time on the submission server. If that time does not correspond to your desktop clock app, you need to figure out how to fix your desktop clock app to sync your desktop clock with a recommended clock server for your computer.
      • You will get a backup e-mail with the same content as the web page mentioned above. It's just a backup, so don't wait for it.
      • You can work on your exam as soon as you got the ZIP file
      • If something is not working correctly, please send me an e-mail to as soon as possible (but please keep in mind that e-mail can take a very very long time to get delivered).

    • Go to your desktop and click open the answers text file and work on your exam and save your modified answers text file regularly. Feel free to make submissions if you are done early. Again, it's not a good idea to work on a copy of the answers text file because you may end up submitting the wrong answers text file and there's nothing I can do if that happens! You are responsible for making sure that you submit the correct file.

    • When your alarm goes off at (X+1):09:00, you need to wrap things up and get ready to submit your exam answers text file.

    • At (X+1):10:00, you must stop working on your answers. Save your answers text file and go to the submission web page. (Of course, if you have already made a successful submission and have saved a copy of the ticket you got and you haven't changed your answers, you are done and you can stop right here. But if you want to continue to work on your exam, that's fine too as long as you have made at least one submission before (X+1):13:00.)

    • To make a submission, first reload/refresh the submission web page and make sure that you are seeing the current time on the submission server right above the submission web form. If reloading the web page failed, you should check to see if you can reach other websites. If you cannot reach other websites, then you don't have a Internet connection and you must follow the instructions to use Panopto to record your desktop and your exam answers and take photos of your answers and e-mail photos of your exam answers to me. If you can reach other websites, then you should continue to try to access the submission web page.

      If reloading the web page was successful, you must fill out the submission web form and click on the Choose File button and select the answers text file that you have filled out and saved. Click on the Upload button. If you get any popup messages, please read them carefully and follow the suggestions there (there is nothing I can do if you submit the wrong file). If the submission server is busy, you should not be surprised because many students are making submissions simultaneously. So, all you have to do is to keep submitting your answers text file repeatedly until you can make a successful submission (i.e., you are presented with a submission ticket and the ticket looks right). You should save a copy of that ticket by saving the web page you see as a PDF file. It's your responsibility that you have submitted the correct answers text file.

      If you cannot reach the submission server after many tries, but still have Internet connectivity, it is possible (although unlikely) that the server is down or unresponsive. In this case, you should follow the instructions to use Panopto to record your desktop and your exam answers and take photos of your answers and e-mail photos of your exam answers to me. (Of course, for the rehearsal, you probably shouldn't just click Send since the e-mail will go to me. You can change the recipient e-mail address to yourself and then click Send.) Then go back and continue to make a submission using the web form and maybe you will be able to connection to the submission server this time around.

      The current item is summarized in the flowchart below.

    Since this is a rehearsal, I would strongly recommand and everyone try out the procedure to use the Panopto Recorder to record your desktop and your exam answers and take photos of your exam answers (and you can e-mail the photos to yourself as a test) and try it for a few times until you feel comfortable with the procedure just in case you may lose your Internet connection when you are submitting the exam answers during the real exam. Also, try out different scenarios such as disabling wifi on your laptop to simulate the loss of Internet connectivity so you know what to expect.

    Please understand that if you submit late (i.e., any time at or after (X+1):13:00), I have to follow the rules I mentioned in class and deduct 5% for every late minute. For example:

    • If your submission timestamp is ≥ X:13:00 and ≤ X:13:59, 5% will be deducted.
    • If your submission timestamp is ≥ X:14:00 and ≤ X:14:59, 10% will be deducted.
    • If your submission timestamp is ≥ X:15:00 and ≤ X:15:59, 15% will be deducted.
    • If your submission timestamp is ≥ X:16:00 and ≤ X:16:59, 20% will be deducted.
    • ...

    I cannot make an exception for any student. If you are not familiar with all the rules, please watch the recorded live DEN section Lecture 18 on 3/8/2023.

    VERY IMPORTANT: As mentioned in live DEN section Lecture 18 on 3/8/2023, I cannot accept "my machine crashed when I was making a submission" as an excuse for late submission unless you have a video to prove it (please see slide 30 of the live DEN section Lecture 18 on 3/8/2023 slides for instructions). If you know that your machine is prone to crashing or random rebooting (only you would know that), you should do a complete shutdown of your machine and reboot your machine into a clean state at least 5 minutes before the start of the exam and don't run anything on your machine other than what's required to take the exam. (It's a good idea to do that even if your machine is not prone to random crashes or reboots.)  And most importantly, when you have finished your first pass through the exam, make a submission right away! Then every time you make a change in your answers, make another submission. Remember, you can make as many submissions as you'd like and by default, we will grade your last submission. If you are still working on your first pass at (X+1):10:00, you must stop working on your exam and make a submission immediately! After you have made an on-time submission, you can continue to work on your exam and if you make changes, make another submission. This way, you can avoid late penalty because you would always have a submission that was on time. If you are not familiar with the procedure of making an exam submission, you should practice by going through the midterm exam rehearsal procedure as many times as you'd like. If you have lost the midterm rehearsal link, please send me e-mail.

    If anything is not clear, please feel free to ask me.

  • 3/16/2023: Please download, fill out, sign, and submit the Midterm Exam Academic Integrity Honor Code Pledge as soon as possible. (Please note that submitting a signed pledge doesn't mean that you cannot decide to opt out of the exam later.) Please understand that if I don't get a signed pledge from you, you will not be able to download your midterm exam this coming Tuesday because I need you to promise me that you won't cheat before you can download your exam.
  • 3/15/2023: If you have a Macbook with a non-Intel/AMD CPU, you now have a new option! You can now set up a standard (although "headless") 32-bit Ubuntu 16.04 system in AWS Free Tier! In a way, this is a better option than the MyDesktop option, because this system has a real Internet connection. The down side is that it doesn't have a desktop user interface. So, if you need to run anything, you have to ssh over to the AWS VM and use a commandline user interface. Program with a graphical user interface can run very slow because the AWS servers can be very far away. The only software that has a GUI that you must run in this class is the weenix console (which is pretty light in terms of graphics), so this system is actually quite usable.

    There is one issue with the AWS system where you cannot run weenix under gdb the usual way! Therefore, you need an updated weenix program and a new weenix-tmux-debug program to run weenix under gdb. After you have downloaded these 2 programs, please do 

        chmod 755 weenix 
    chmod 755 weenix-tmux-debug
    The updated weenix program is completely backwards-compatible with the weenix program in the prestine kernel source.

    To use the new weenix-tmux-debug program, you need to set GDBWAIT=1 in Config.mk and recompile your kernel. Please also make a one-line modification to "kernel/main/kmain.c". Please find the following line of code inside the kmain() function: 

        while (gdb_wait) ;
    and add a line above it and the resuling code would looke like: 
        if (gdb_wait) dbg_print("Waiting for gdb to start ...\n");
    while (gdb_wait) ;
    To run it, just do (and you don't have to specify how many seconds to wait any more): 
        ./weenix-tmux-debug
    This program uses tmux to create two panes. The left pane is running gdb and the right pane is displaying the content of the old qemu-system-i386 window. When you see the right pane prints "Waiting for gdb to start ...", you should press <Ctrl+b> followed by <Left> to move the cursor into the left pane then press <Ctrl+d> in the left pane to start gdb. When you are done debugging weenix, press <Ctrl+b>, followed by <Down> to move the cursor into the bottom pane and type the following command to kill the tmux session: 
        killtmux

    If you hare not familiar with tmux, please see the the kernel FAQ items on tmux. One down side of running things in tmux is that you cannot use the "layout" gdb command. Therefore, if you need to use the "layout" gdb command, you have to debug weenix the old way (i.e., type "./weenix -n -d gdb -w 10").

    Even if you are not running in AWS, you can also use these two new scripts/programs.

  • 3/9/2023:  The midterm exam will be a 40-minute long take-home exam (open book and open notes).

    The midterm exam will cover everything from the beginning of the semester to slide 21 of Lecture 17 on 3/6,7/2023, MINUS Chapter 5 (i.e., material in Ch 5 is excluded from the midterm, i.e., slides 30 through 60 of Lecture 13, all slides in Lecture 14, and slides 4 through 53 of Lecture 15 are excluded from the midterm coverage). Also included are discussion section slides from Week 1 through Week 7.

    Regarding what types of questions will be on the midterm, please see the Exams section of the course description web page.

    Here is a quick summary of the midterm exam topics (not all topics covered may be listed):

    • Ch 1 - Introduction
      • introduction
      • a simple OS
      • files
    • Ch 2 - Multithreaded Programming
      • thread creation, termination
      • thread synchronization
      • thread safety, deviations
    • Ch 3 - Basic Concepts
      • context switching, I/O
      • dynamic storage allocation
      • static linking and loading
      • booting
    • Ch 4 - Operating-System Design
      • a simple system
      • storage management
    • Warmup assignments 1 & 2
      • discussion section slides
      • specs
      • FAQs
      • my posts to class Google Group
    • Kernel assignment 1
      • discussion section slides
      • spec
      • FAQ
      • my posts to class Google Group

    Please note that kernel 1 is included in the midterm coverage but Chaper 5 is not. This mean that I can ask weenix-specific questions in the midterm exam.

  • 3/9/2023: As mentioned in the Tuesday live lecture, today's primary live lecture has been cancelled. Please watch the recording of yesterday's DEN section live lecture for midterm logistics. We will go straight into the secondary live lecture starting at 9:30am.
  • 3/4/2023:
    • Below is the grade normalization information for warmup2. Please note that this only applies to the grader-dependent part of your grade. If you are graded by Anish Deshmukh <anishdes@usc.edu>, his warmup2 average was 85.79 with a standard deviation of 21.64. If you are graded by Vasudha Bhanudas Mahajan <vasudhab@usc.edu>, her warmup2 average was 89.10 with a standard deviation of 17.87. The overall class average for warmup2 was 87.45 with a standard deviation of 19.91.

      If your grader-dependent part of your grade is X and your grader's average is A, your normalized grader-dependent part of your grade would be X+(87.45-A). Your minimum score is still one point if you have submitted something for grading.

      As I have mentioned in Lecture 1, although we assume that we have a bell-shaped curve, when your score is normalized, linear interpolation is used. It's clearly not perfect since the actual curve will never be bell-shaped and linear interpolation is not the same as bell-shaped-curve interpolation. But this is what was announced, and therefore, we will stick to this particular way of normailzation for all the programming assignments for the rest of the semester, knowing that it's not perfect.

  • 2/28/2023: I won't be able to come to campus this morning. Therefore, today's TT section live lecture will be on Zoom only. Sorry about the short notice and inconvenience.
  • 2/13/2023: Something just came up and I won't be able to start today's office hour at 3pm. Therefore, I'm moving today's office hour to 3:30-4:30pm. Sorry about the short notice and inconvenience.
  • 2/8/2023:
    • Below is the grade normalization information for warmup1. Please note that this only applies to the grader-dependent part of your grade. If you are graded by Anish Deshmukh <anishdes@usc.edu>, his warmup1 average was 92.87 with a standard deviation of 12.66. If you are graded by Vasudha Bhanudas Mahajan <vasudhab@usc.edu>, her warmup1 average was 91.15 with a standard deviation of 19.57. The overall class average for warmup1 was 92.01 with a standard deviation of 16.51.

      If your grader-dependent part of your grade is X and your grader's average is A, your normalized grader-dependent part of your grade would be X+(92.01-A). Your minimum score is still one point if you have submitted something for grading.

      As I have mentioned in Lecture 1, although we assume that we have a bell-shaped curve, when your score is normalized, linear interpolation is used. It's clearly not perfect since the actual curve will never be bell-shaped and linear interpolation is not the same as bell-shaped-curve interpolation. But this is what was announced, and therefore, we will stick to this particular way of normailzation for all the programming assignments for the rest of the semester, knowing that it's not perfect.

  • 2/6/2023: I have an urgent family matter that needs my attention and I will not be able to hold office hour at 2-3pm today. I'm moving today's office hour to 9-10pm tonight. Sorry about the short notice and inconvenience.
  • 1/23/2023: I have an urgent family matter that needs my attention and I will not be able to hold office hour today. I'm moving today's office hour to 2-3pm tomorrow. Therefore, tomorrow's office hour will go from 2pm to 4pm. Sorry about the short notice and inconvenience.
  • 1/10/2023: I have sent a post to the class Google Group to cancel Today's TT section live lecture. Please watch the recorded "DEN section live Lecture 1 video" (and the "pre-recorded video part 2 of Lecture 1" there as well). Sorry about the short notice and inconvenience.
  • 1/6/2023:
    • Watch this area for important announcements.

    • To get username and password for accessing protected area of this web site, please visit the request access page after semester starts and submit the requested information. (You do not have to be registered for the course to get the password. You just need to have an USC e-mail address.)

    • Due to security concerns, we cannot post Zoom meeting IDs in public area of the class website. A summary of Zoom meeting IDs and links are provided here (password protected).

    • Please do not send request to join the class Google Group until after the Lecture 1.
Prerequisites
Some people mistakenly think that this is an introductory CS class! This class has CS prerequisites! In the official syllabus, it is listed that the prerequisites are:
(CSCI 201L or CSCI 455x) and (EE 357 or EE 352L)

Please see:

Apparently, they are the prerequisites for undergraduate students only. The CS department would waive these prerequisites for graduate students. Since undergraduate students are required to take CS 350 for OS credit, there should only be graduate students enrolled in CS 402. Therefore, these prerequisites are really not prerequisites. They should be considered recommended preparation for graduate students. The basic idea behind these prerequisites is that you are expected to know how to program and you are expected to know something about computer architecture (such as what a CPU does).
 
Important Information about Programming Assignments
The programming assignments of this class will be very demanding. You will be required to write C code. Since C is a proper subset of C++, knowing C++ well would give you enough background. However, some of the things that available in C++, such as strings and streams, are not be available in C. So, you need to know how to do things such as manipulating null-terminated array of characters (using functions such as strchr, strrchr, strlen, strcmp, strncpy, etc.) and performing console and file I/O (using functions such as printf/snprintf, fread/fwrite, read/write, fgets, etc.) in C. No other programming language will be accepted. We will not teach C in this class. You are expected to pick up C on your own if you are not familiar with it.

You should also get familiar with the Unix/Linux development environment (vi/pico/emacs, cc/gcc, make, etc.) You are expected to know how to use Unix/Linux. If you are not familiar with Unix/Linux, please read Unix for the Beginning Mage, a tutorial written by Joe Topjian. Unfortunately, looks like this book has just disappeared from the web. You can also visit UNIX Tutorial for Beginners or Learn tcsh in Y Minutes. If you already know how to use Unix/Linux before and just need a refresher, please review my summary of some commonly used Unix commands and my tcsh scripting tutorial. If you knew how to use Unix/Linux before and just need a refresher, please review a summary of some commonly used Unix/Linux commands.

All programming assignments must run on 32-bit Ubuntu 16.04. The kernel programming assignments will only work on a 32-bit Ubuntu 16.04 system. Therefore, you should install a 32-bit Ubuntu 16.04 on your laptop or desktop as soon as possible and start using it right away. If you do not have a personal laptop or desktop that runs Windows or Mac OS X, please contact the instructor as soon as possible. If you are considering buying a laptop, please buy an Intel-based laptop that runs Windows or Mac OS X.

If the only computer you have access to is the new Mac running on a non-Intel/AMD CPU, then it may not be possible to install VirtualBox into your machine. If that's the case, please read here.

If a student registered late for this class or could not be present at the beginning of the semester, the student is still required to turn all projects and homeworks on time or the student will receive a score of 0 for these assignments. No exceptions!