• The labs 2024 are slightly reworked compared to 2023 and you need to demonstrade the new version.
• Attending the lab sessions and demonstrating to the lab assistants can be done based on availability. First-time students have first priority.
• Regarding webreg, you should register in the group "Returning students". Previous results can be accounted for by mailing your course assistant.
• TDDE47 students: If you only wish to demonstrate your labs (or take the exam), there is no need to do a formal course registration, your old registration is sufficient. However, if you need to attend lectures/lessons and go to more than just a couple of lab sessions, you should re-register to the course to be ensured a seat.
• TDDB68 students: You do not have to register to TDDE68 nor re-register to TDDB68. Just finish up your labs according to TDDE68 instruction and we'll handle the rest. Your previous registration to TDDB68 is sufficient for both labs and exam.

The course was given for the last time spring 2023. From spring 2024 the course TDDE68 is given instead.

If you encounter any problems with signing up for labs, please contact your course assistant.

The assignments are done in pairs, but the examination is individual. This means that it may happen that only one student in a pair recieves the passing grade. If the lab groups are not filled up, you may do the labs alone, but this is not recommended.

Beyond the scheduled lab sessions you also have to spend a significant amount of non-scheduled time on these laborations.

The main deadlines are found in your timeedit schedule. The deadline appear at 08:00 in the morning to give you a heads-up and expires at 23:59 the same day.

Note that the entire lab series (labs 0-6) must have been approved by the lab assistant by the time of the final deadline. This means that if you demonstrate on the last day and have flaws in the solution, then you will not make the deadline.

If you pass the demonstration, meaning you code seem to work sufficiently good and you seem knowledgeable, you may still be asked to fix something after our inspection of your code. In this case you have 7 days and one shot at submitting the rectified code and still retain the bonus. The clock start ticking once you are notified of the issues.

If you haven't passed the labs by the time of the final deadline, you will have to wait until the retake period in June or August do demonstrate your solution. After August, the next time to demonstrate will be during the next instance of the course next year. Demonstrations in June or August must be scheduled with the course assistant well in advance.

• The most important piece of documentation is the original pintos documentation [stanford.edu]. Or if you prefer it, as pdf. - The projects referred to in this document are not the same as our laboration assignments!
• See the slides from the lessons from the lectures and lessons page.
• A Frequently Asked Questions page is being created.

There are three options for running the labs:

• Preferred option: Use the Linux computer lab environment provided by LiU. You can use any of the SU*-rooms in the B-building, but also any other Linux lab room (there are some at ISY and MAI). You can also access the environment remotely by accessing a dedicated machine using RDP or through ThinLinc, more information here.
• Install the Xubuntu VM provided here and run it on VirtualBox on your own machine.
• Setup on your own Linux machine or a self-installed VM. We do not provide any support for this option, but there are some instructions that might be helpful.

Note: Only lab 2, 5, and 6 should be handed in
In order to ensure that the code being examined by the lab assistant has been submitted by both students in the lab group the following process should be followed.

1. The code is submitted to the lab assistant by creating a branch in your git repository (to which you should have invited your assistant). The name of the branch should be "Lab X submission". A link to the branch should be sent by email.
2. Always send email from your LiU student account.
3. Always include the course code in the subject of your email and also information about whether you want to submit a solution or ask a question. Do not mix the two.
4. When submitting a solution, include your lab partner in the list of recipients.
5. Include the following text in your submission:

   We hereby submit this program code as part of the examination for the programming labs in TDDE68/TDDE47 Concurrent programming and operating systems. We guarantee that all submitted code except for parts included from the lab skeleton has been written entirely by us.
   your names

6. The student not sending the email should reply to all and state: I confirm the contents of the email to which this is a reply.

In general we will assess your solution based on the following points:

• Correct memory management
• No undefined behaviour
• No synchronization errors

Breaking one or more of the above may result in complementary work.
As long as your solution solves the assignment and passes the given requirements, you will not be given complementary work based on efficiency, how "clean", or readable your code is. You may however get feedback on those points, in order to help you improve on those areas.

Lab instructions from 2023:

• Lab0: Lists and setup PDF
• Lab1: Basic system calls PDF
• Lab2: Basic Synchronization PDF
• Lab3: exec and exit PDF
• Lab4: Command line PDF
• Lab5: wait PDF
• Lab6: File system PDF