Nov-05: It is noon, and so Project-6 is due and I am about to collect it. And with that, Project-7 is posted, so go to the Assignments page and check it out.
Oct-19: With apologies to Section 2, I am cancelling the usual Zoom lecture for this evening. You should go to the Google Drive and watch the Section 1 lecture that is posted there. (I know I said I wouldn't do this again, but unexpected circumstances...)
Oct-09: In quick succession, your graded Project-3 has been pushed into a branch of your sysproj-3 repository on GitLab. It is structured just like with Project-2, so go and check it out.
Oct-05: Your graded Project-2 has been returned. As with Project-1, the results are in your GitLab repository. The code files themselves may have some comments, and graded/feedback.txt will contain your grade and some overall comments.
Notice that there is one critical difference in how these results were returned to you: they are committed to your repository in a new branch. git allows the sequence of commit/push operations to follow multiple paths. To avoid conflicts with any additional commit/push operations you did on your own work, I created a branch named graded that contains all of the above additional files.
To see this branch, login to GitLab and go to your sysproj-2 repository. Just under the name of the project, you will see a little pictogram labeled 2 Branches. Click on that, and you will see a listing of the branches: graded and master. Click on graded. You will see all of your files, plus the graded/ directory with the results.
Oct-02: There is a bug in bf-alloc.c! Specifically, the code that I distributed contains, in malloc(), you will find this block of code:
if (best->prev == NULL) { free_list_head = best->next; } else { best->prev->next = best->next; best->prev = NULL; } if (best->next != NULL) { best->next->prev = best->prev; best->next = NULL; }
These lines should be slightly refactored, moving the nullifying of the next and prev fields in the block being removed from the list to the end of the code block:
if (best->prev == NULL) { free_list_head = best->next; } else { best->prev->next = best->next; } if (best->next != NULL) { best->next->prev = best->prev; } best->prev = NULL; best->next = NULL;
Sep-17: Your graded Project-1 submissions have now been returned. Specifically, you should git pull the most updated copy of your repository. Within that repository you will find:
Sep-08: As I thought, I made a mistake in Project-1 when I asked y'all to submit your work by adding me as a Guest to your sysproj-1 repository. Indeed, I do need to be a Developer to be able to clone your repository and then add new files (graded work) that I will then commit/push. Some of you added me as a Developer from the get-go, but if you did not, here are the steps to change me designation:
Also, I need to change how you submit questions. While office hours will continue as usual, and TA help hours will remain on Wednesdays at 7 pm, many of you are also making wonderful use of the ability to ask questions on Slack. This is a good thing, but it also produces a volume of questions with which I cannot keep up.
So, for all questions/problems relating to the projects and the course material, we are going to use the following, new approach:
Where to ask your question: Post your questions to the #cosc-171 channel on Slack.
Asking anonymously: If you are at all inhibited about posting, under your name, a question that everyone can see, then you should post your question anonymously. Specifically, prefix you question with /abot #cosc-171, which would look like this:
/abot #cosc-171 I don't think I understand the difference between using "rsi" and "[rsi]" as an operand...
Seeing the answers: If the question is one for which we think everyone would benefit from seeing the answer, we will simply reply in a thread. If the question is really specific to you (i.e., to your code), then we may reply directly to you. This reply will appear (I think) in a new App channel in Slack named abot_anonymous_poll_a.
Please do give this a try. I am hopeful that, with the help of our TA's, you will get answers more quickly, we will all see more of one another's questions, and I will hold onto a little more sanity.
Aug-31: No class today. An urgent family matter is going to have me occupied all of today.
Aug-30: Regarding office hours: I have scheduled some office hours over four days this week...
For the by appointment hours, sign up via the sign up sheet). For open hours, I will be available on Slack, where you can post to the course channel or direct-message me. If a question is best answered with a conversation, we will jump into Zoom.
Aug-26 (part B): There will be a Zoom-based TA help session tonight, and every Wednesday night, at 7 pm. You can find the Zoom link on the Moodle page for the course (see link below).
Aug-26: And we are now rolling! Be sure to prepare your computer for this course by following the instructions in the Tools document.
Also, the office-hours sign up is now live and usable. I have some hours this week, and will have more next week, perhaps at different times. I'm still figuring out how best to schedule things in this completely new arrangement.
Jul-21: Welcome to Computer Systems! There are a few key pieces of information that you should know before classes begin:
Our first class meeting will be on Monday, Aug-24 on Zoom. Section-01 meets from 12:40 pm to 1:30 pm; Section-02 meets from 5:10 pm to 6:00 pm. To find the links to the Zoom meetings, go to the course Moodle page, which is where any restricted-access content will be posted.
During this first lecture, we will spend some time discussing an overview of the class, but we will quickly dive into the beginning, detailed material, so it is critical that you are present from the very beginning.
Before our first class meeting, read the Course Information. This document covers the course topics, expectations, structure, grading, etc. You are expected to have reviewed this document thoroughly.