COMP3000 Operating Systems 2024W: Difference between revisions
Lianyingzhao (talk | contribs) mNo edit summary |
Lianyingzhao (talk | contribs) |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''Note: this page's purpose is to host publicly available material linked from Brightspace. Please use Brightspace as the primary source of information to stay updated.''' | '''Note: this page's purpose is to host publicly available material linked from Brightspace. Please use Brightspace as the primary source of information to stay updated.''' | ||
==Course Outline== | ==Course Outline and Office Hours== | ||
Aside from in Brightspace, you can also find it [https://outline.scs.carleton.ca/media/2024/W/COMP3000AW2024/COMP-3000-A-W-2024.pdf here]. | Aside from the updated version in Brightspace, you can also find it [https://outline.scs.carleton.ca/media/2024/W/COMP3000AW2024/COMP-3000-A-W-2024.pdf here]. Note that only the Brightspace version will contain the up-to-date information about TAs and office hours. | ||
Follow the office hours schedule to meet a TA in the corresponding room. Alternatively, if you can't make it, you may also contact the instructor or TAs by email, on MS Teams or booking an appointment for online office hours over Zoom. | |||
Follow the office hours schedule in | |||
==Tutorial Instructions== | ==Tutorial Instructions== | ||
Submit the work by the deadline indicated in Brightspace. You can work on the tutorial until the deadline. What is submitted is not graded for correctness but effort showing your attempts and thinking. After the submission, you should continue to study it if there is still anything you do not understand well, for the assignments and exams. | Submit the work by the deadline indicated in Brightspace. You can work on the tutorial until the deadline. What is submitted is not graded for correctness but effort showing your attempts and thinking. After the submission, you should continue to study it if there is still anything you do not understand well, for the assignments and exams. | ||
===[[COMP3000 Operating Systems | ===[[COMP3000 Operating Systems W24: Openstack Instructions | Instructions for setting up an Openstack instance]]=== | ||
===Various ways of [[COMP3000 Operating Systems | ===Various ways of [[COMP3000 Operating Systems W24: Connecting to SCS Openstack | connecting to SCS Openstack]]=== | ||
===[[COMP3000 Operating Systems | ===[[COMP3000 Operating Systems W24: Downloading files from your Openstack VM | Downloading files from your Openstack VM]]=== | ||
===Tutorial 1=== | ===Tutorial 1=== | ||
Jan 11 | Jan 11 and Jan 12, 2024: [[COMP3000 Operating Systems W24: Tutorial 1 | Instructions]] | ||
===Tutorial 2=== | ===Tutorial 2=== | ||
Jan 18 | Jan 18 and Jan 19, 2024: [[COMP3000 Operating Systems W24: Tutorial 2 | Instructions]] | ||
===Tutorial 3=== | ===Tutorial 3=== | ||
Jan 25 | Jan 25 and Jan 26, 2024: [[COMP3000 Operating Systems W24: Tutorial 3 | Instructions]] | ||
===Tutorial 4=== | ===Tutorial 4=== | ||
Feb 1 | Feb 1 and Feb 2, 2024: [[COMP3000 Operating Systems W24: Tutorial 4 | Instructions]] | ||
===Tutorial 5=== | ===Tutorial 5=== | ||
Feb 8 and Feb 9, 2024: [[COMP3000 Operating Systems W24: Tutorial 5 | Instructions]] | |||
===Tutorial 6=== | ===Tutorial 6=== | ||
Mar | Feb 29 and Mar 1, 2024: [[COMP3000 Operating Systems W24: Tutorial 6 | Instructions]] | ||
===Tutorial 7=== | ===Tutorial 7=== | ||
Mar | Mar 7 and Mar 8, 2024: [[COMP3000 Operating Systems W24: Tutorial 7 | Instructions]] | ||
===Tutorial 8=== | ===Tutorial 8=== | ||
Mar | Mar 14 and Mar 15, 2024: [[COMP3000 Operating Systems W24: Tutorial 8 | Instructions]] | ||
===Tutorial 9=== | ===Tutorial 9=== | ||
Mar | Mar 21 and Mar 22, 2024: [[COMP3000 Operating Systems W24: Tutorial 9 | Instructions]] | ||
==How to Do Well in This Course== | ==How to Do Well in This Course== | ||
The goal here is to establish a <u>conceptual model</u> to understand how operating systems work to serve applications. It is not a course like math or data structures. '''To succeed, you need to be more hands-on and focus on figuring out how to find the answers (like learning to fish) instead of the answers alone (like being given a fish)'''. | The goal here is to establish a <u>conceptual model</u> to understand how operating systems work to serve applications. It is not a course like math or data structures. '''To succeed, you need to be more hands-on and focus on figuring out how to find the answers (like learning to fish) instead of the answers alone (like being given a fish)'''. You can NOT expect to do well only by reading course material. You must work with a real OS, with the course material as guidelines. As you progress, you should be gradually able to imagine how various pieces of the OS fit together to function, which will be very useful in your everyday work/life with computers. | ||
If you are asking a lot of "why"s, you are on the right track. Use all available resources (including the course material) as references, like a dictionary, to help answer your "why"s. For example, when you are asked about some information, based on your knowledge, think: 1) which part of the OS should have this information? 2) is it supposed to be available at the point in question? 3) then how do you retrieve that information? e.g., any tool/command/funcion call? | If you are asking a lot of "why"s, you are on the right track. Use all available resources (including the course material) as references, like a dictionary, to help answer your "why"s. For example, when you are asked about some information, based on your knowledge, think: 1) which part of the OS should have this information? 2) is it supposed to be available at the point in question? 3) then how do you retrieve that information? e.g., any tool/command/funcion call? | ||
For sure, this would not be possible if you are just getting started, so a bit of confusion at the beginning is normal. As you move on, the conceptual model will become clearer as the basis for your thinking. | For sure, this would not be possible if you are just getting started, so a bit of confusion at the beginning is normal. As you move on, the conceptual model will become clearer as the basis for your thinking. | ||
Mandatory textbook reading will be posted in Brightspace, and thus not all of the textbook will be covered. The exams and assignments are based on lectures, tutorials and designated textbook chapters. | |||
==Course Delivery Method== | ==Course Delivery Method== | ||
Lectures will be in person | Lectures will be in person. Course discussions will be on [https://teams.microsoft.com/ Microsoft Teams]. Such discussions may include but are not limited to assignment clarifications, pre-class polls, ad-hoc announcements, and tutorial discussions. | ||
All work submissions ( | All work submissions (excluding exams), as well as important (e.g., grading-related) announcements, course material and grade posting, will be through Brightspace. | ||
==Online Submission of Course Work== | ==Online Submission of Course Work== | ||
Assignments/tutorials submissions are handled electronically (i.e., through Brightspace) and there is no "grace period" with respect to a deadline - an assignment submitted even one minute after the deadline is late and will not be accepted by the system. Technical problems do <b>not</b> exempt you from this requirement, so if you <u>wait until the last minute</u> and then have issues with your connection, you will still receive a mark of zero. Consequently, you are advised | Assignments/tutorials submissions are handled electronically (i.e., through Brightspace) and there is no "grace period" with respect to a deadline - an assignment submitted even one minute after the deadline is late and will not be accepted by the system. Any extenuating situation or academic accommodation request must be received by the instructor <u>up to 24 hours following the due time</u>, and will be considered on a case-by-case basis. Technical problems do <b>not</b> exempt you from this requirement, so if you <u>wait until the last minute</u> and then have issues with your connection, you will still receive a mark of zero. Consequently, you are advised to submit your work at least several hours in advance of the due date and time. Contact the TAs/instructor in case of any problems. | ||
Format errors, missing files, and other technical/non-technical upload issues will not constitute the justification for another attempt. Only what has been uploaded by the due date and time will be graded. After you upload your submission to Brightspace you should re-download it immediately for verification and ensure that all needed files are there in the right format. | |||
⚠️ For all submissions (regardless of whether collaboration is allowed), the answers must be your own words. Any answers copy-pasted or rephrased from someone else with high resemblance are identified in your submission, you are subject to being reported to the Dean for plagiarism. | |||
==Collaboration== | ==Collaboration== | ||
Latest revision as of 00:29, 7 January 2024
Note: this page's purpose is to host publicly available material linked from Brightspace. Please use Brightspace as the primary source of information to stay updated.
Course Outline and Office Hours
Aside from the updated version in Brightspace, you can also find it here. Note that only the Brightspace version will contain the up-to-date information about TAs and office hours.
Follow the office hours schedule to meet a TA in the corresponding room. Alternatively, if you can't make it, you may also contact the instructor or TAs by email, on MS Teams or booking an appointment for online office hours over Zoom.
Tutorial Instructions
Submit the work by the deadline indicated in Brightspace. You can work on the tutorial until the deadline. What is submitted is not graded for correctness but effort showing your attempts and thinking. After the submission, you should continue to study it if there is still anything you do not understand well, for the assignments and exams.
Instructions for setting up an Openstack instance
Various ways of connecting to SCS Openstack
Downloading files from your Openstack VM
Tutorial 1
Jan 11 and Jan 12, 2024: Instructions
Tutorial 2
Jan 18 and Jan 19, 2024: Instructions
Tutorial 3
Jan 25 and Jan 26, 2024: Instructions
Tutorial 4
Feb 1 and Feb 2, 2024: Instructions
Tutorial 5
Feb 8 and Feb 9, 2024: Instructions
Tutorial 6
Feb 29 and Mar 1, 2024: Instructions
Tutorial 7
Mar 7 and Mar 8, 2024: Instructions
Tutorial 8
Mar 14 and Mar 15, 2024: Instructions
Tutorial 9
Mar 21 and Mar 22, 2024: Instructions
How to Do Well in This Course
The goal here is to establish a conceptual model to understand how operating systems work to serve applications. It is not a course like math or data structures. To succeed, you need to be more hands-on and focus on figuring out how to find the answers (like learning to fish) instead of the answers alone (like being given a fish). You can NOT expect to do well only by reading course material. You must work with a real OS, with the course material as guidelines. As you progress, you should be gradually able to imagine how various pieces of the OS fit together to function, which will be very useful in your everyday work/life with computers.
If you are asking a lot of "why"s, you are on the right track. Use all available resources (including the course material) as references, like a dictionary, to help answer your "why"s. For example, when you are asked about some information, based on your knowledge, think: 1) which part of the OS should have this information? 2) is it supposed to be available at the point in question? 3) then how do you retrieve that information? e.g., any tool/command/funcion call? For sure, this would not be possible if you are just getting started, so a bit of confusion at the beginning is normal. As you move on, the conceptual model will become clearer as the basis for your thinking.
Mandatory textbook reading will be posted in Brightspace, and thus not all of the textbook will be covered. The exams and assignments are based on lectures, tutorials and designated textbook chapters.
Course Delivery Method
Lectures will be in person. Course discussions will be on Microsoft Teams. Such discussions may include but are not limited to assignment clarifications, pre-class polls, ad-hoc announcements, and tutorial discussions. All work submissions (excluding exams), as well as important (e.g., grading-related) announcements, course material and grade posting, will be through Brightspace.
Online Submission of Course Work
Assignments/tutorials submissions are handled electronically (i.e., through Brightspace) and there is no "grace period" with respect to a deadline - an assignment submitted even one minute after the deadline is late and will not be accepted by the system. Any extenuating situation or academic accommodation request must be received by the instructor up to 24 hours following the due time, and will be considered on a case-by-case basis. Technical problems do not exempt you from this requirement, so if you wait until the last minute and then have issues with your connection, you will still receive a mark of zero. Consequently, you are advised to submit your work at least several hours in advance of the due date and time. Contact the TAs/instructor in case of any problems.
Format errors, missing files, and other technical/non-technical upload issues will not constitute the justification for another attempt. Only what has been uploaded by the due date and time will be graded. After you upload your submission to Brightspace you should re-download it immediately for verification and ensure that all needed files are there in the right format.
⚠️ For all submissions (regardless of whether collaboration is allowed), the answers must be your own words. Any answers copy-pasted or rephrased from someone else with high resemblance are identified in your submission, you are subject to being reported to the Dean for plagiarism.
Collaboration
Collaboration on all work is allowed except for the midterm and the final exams. Collaboration, however, should be clearly acknowledged.
For assignments, while you may get help from others and even collaboratively solve technical problems, the code and answers submitted should all be your own work. For example, you may not divide an assignment into parts, give a part to another student or anyone else to solve, and then submit that work as your own. You have to have participated in the creation of every part of your submitted work. An easy way to make sure this happens is to never share files regarding coursework or copy and paste answers. Instead, only meet together (virtually) to work on an assignment (e.g., to discuss your understanding/confusion) and then separate to write up your own solutions.
Similarity between submitted assignments that has not been appropriately documented will be treated as plagiarism - the same as copying on a midterm or a final - and will be submitted to the Dean for disciplinary action.
Sharing assignment or exam specifications or posting them online (to sites like Chegg, CourseHero, OneClass, etc.) is considered academic misconduct. You are never permitted to post, share, or upload course materials without explicit permission from your instructor. Academic integrity offences are reported to the office of the Dean of Science. Penalties for such offences can be found on the ODS webpage: https://science.carleton.ca/academic-integrity/.