Tomorrow is the final lecture. The majority of the time will be given over to a review of the material we've covered so far. If you have questions about anything we've seen already, or would like us to focus on a part you feel you understand less well, mention this on the lecture forum post.

Tomorrow is also the final help session. If you're interested in turning up, react, so I know if we need to recruit an additional tutor to be there.

The submission system for assignment 3 is now on-line. Students with extensions should be able to see them via "give". If something seems to be wrong with it, let us know on the forum.

Assignment 2 submissions are coming in, with a few extensions remaining. Good work everyone!

The assignment 3 spec is pre-released, see the menu bar. There is also an "assignment 3 intro" mini-lecture, which we've covered most of on Wednesday. You can look at the spec, think through your approach, and go looking for the address space interface in your existing OS/161 checkouts.

The starting codebase you should work from will be released to gitlab on Friday.

Assignment 1 marks are out. Marks for the advanced component are still being finalised. There has been some discussion about this already; see the forum note on the auto-marking approach to assignment 1.

We're now close to the deadline for assignment 2. I see on the forum that people are working away and bug-hunting, good luck with it.

There have been quite a few questions about the assignment 2 "part 3" document. I've added even more FAQ entries to the spec. If you're really not sure how to approach it, or pick a bit of the git diff, have a look there.

The T2 provisional exam schedule has been posted. We have provisionally been given the morning slot of Wednesday the 27th, the second-last day of the exam period. This may be updated. I am going to request an earlier time. The exam will be organised using CSE facilities, which is why the UNSW central information is vague. More updates on that to come.

Assignment 1 marks will be released soon, and some commentary will be added on Monday. The auto-mark spread was good, and the vast majority of students will get their auto-mark score. Reminder: make sure what you submit passes the simple test done by "give". Don't ignore that error message if you see it, it can mean you miss out on a lot of marks.

Assignment 1: Auto-marking has run, and assignment results are mostly ready to be released. We're waiting on a small number of students who can still theoretically submit for marks thanks to medium-long extensions. We hope to release the results on Friday or the weekend.

Assignment 2: We're still setting up some technology, expect to see the submission mechanism, extensions etc set up real soon now.

Help Session: We have a help session today at 2-4pm. There was a bit of interest in help sessions on the forum, but not a lot of responses to the help session post. Come along if you're interested, online or in person. We'll be running until 4pm. See the forum for join links etc. There may be an online overflow session later in the week if we don't get to everyone today.

Good luck with it!

• The "give" setup for assignment 1 and the advanced version should now work. There are some challenges in configuring "give", especially the auto-test mechanisms. Bear with us if there are outages.
• The "give" system should now know about ELS/ELP extensions. It should be possible to query your deadline using "give". You might need to provide a dummy file with the correct name (which the auto-test should then reject). If something seems to be wrong with the deadline you are told, please contact us via email.
• Our script for creating gitlab repositories fails and skips students who don't seem to have accounts on the gitlab instance. If you've never logged in to it, please log in to the gitlaand check if your repository exists. We are a little surprised how many students don't seem to have done this yet.
• We have tweaked the assignment spec a few times. For instance, if you couldn't get the sources via gitlab and fetched from the website, the kernel build might fail (because you have the Part 5 adjustments already). There are some new hints in the assignment spec how to proceed.
• There was an issue with the secret messages for advanced part 2. If you've done that already, check the website and see if your secret message has changed.
• We've been asked repeatedly about assig codes). The key is to match expectations. If you want to pair up with an existing contact, make sure they plan on doing roughly the same amount of advanced parts as you. Note that students in Ext-OS have constraints on this, and pairs are meant to work together on every submission. There is a process for managing uneven contributions and pair splits, but we don't want to apply that process unless we really have to.