Operating Systems (Fall 2015) - Revision history

Soma: /* Lectures and Exams */

2015-12-02T20:38:14Z

Lectures and Exams

← Older revision		Revision as of 20:38, 2 December 2015
Line 306:		Line 306:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2015F Lecture 23\|Lecture 23]]: ~~TBA~~		<p>[[Operating Systems 2015F Lecture 23\|Lecture 23]]: Other Operating Systems
	</p>		</p>
	</td>		</td>
Line 316:		Line 316:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2015F Lecture 24\|Lecture 24]]: ~~TBA~~		<p>[[Operating Systems 2015F Lecture 24\|Lecture 24]]: The Future
	</p>		</p>
	</td>		</td>

Soma: /* Lectures and Exams */

2015-11-27T20:40:47Z

Lectures and Exams

← Older revision		Revision as of 20:40, 27 November 2015
Line 296:		Line 296:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2015F Lecture 22\|Lecture 22]]: ~~TBA~~		<p>[[Operating Systems 2015F Lecture 22\|Lecture 22]]: Security and malware
	</p>		</p>
	</td>		</td>

Soma: /* Course Project */

2015-11-27T02:28:20Z

Course Project

← Older revision		Revision as of 02:28, 27 November 2015
Line 47:		Line 47:

	Note that there is no fixed length requirement. However, projects that are less that 5 pages are unlikely to get a high grade as that means that less than a page was spent on each section, on average. The implementation and evaluation sections should be the longest ones in your report. An overly short evaluation section may lead to suspicion that you code does not work.		Note that there is no fixed length requirement. However, projects that are less that 5 pages are unlikely to get a high grade as that means that less than a page was spent on each section, on average. The implementation and evaluation sections should be the longest ones in your report. An overly short evaluation section may lead to suspicion that you code does not work.

			'''In order to get a grade for the final project, you need to pass the oral exam.''' You need to pass the oral exam because otherwise we cannot be sure that you have done the work of the project. If you manage to complete a project successfully, either alone or in a group, the oral exam is very easy.

			If you want to schedule an oral exam and you cannot find a slot, please email Prof. Somayaji and let him know your availability.

	===Generating Patches===		===Generating Patches===

Soma: /* Lectures and Exams */

2015-11-25T21:30:08Z

Lectures and Exams

← Older revision		Revision as of 21:30, 25 November 2015
Line 262:		Line 262:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2015F Lecture 19\|Lecture 19]]: ~~Virtualization~~		<p>[[Operating Systems 2015F Lecture 19\|Lecture 19]]: Cloud Computing
	</p>		</p>
	</td>		</td>

Soma: /* Lectures and Exams */

2015-11-25T21:28:50Z

Lectures and Exams

← Older revision		Revision as of 21:28, 25 November 2015
Line 262:		Line 262:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2015F Lecture 19\|Lecture 19]]		<p>[[Operating Systems 2015F Lecture 19\|Lecture 19]]: Virtualization
	</p>		</p>
	</td>		</td>
Line 282:		Line 282:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2015F Lecture 21\|Lecture 21]]: ~~Virtualization~~		<p>[[Operating Systems 2015F Lecture 21\|Lecture 21]]: Research
	</p>		</p>
	</td>		</td>

Soma: /* Assignments */

2015-11-25T21:23:43Z

Assignments

← Older revision		Revision as of 21:23, 25 November 2015
Line 496:		Line 496:
	</td>		</td>
	</tr>		</tr>
	~~<tr>~~		</table>
	~~<td>~~
	~~<p>Nov. 25~~
	~~</p>~~
	~~</td>~~
	~~<td>~~
	~~<p>[[Operating Systems 2015F: Assignment 6\|Assignment 6]]~~
	~~</p>~~
	~~</td>~~
	~~</tr>~~
	</table>

	==Course Software==		==Course Software==

Soma: /* Tutorials */

2015-11-24T18:58:57Z

Tutorials

← Older revision		Revision as of 18:58, 24 November 2015
Line 430:		Line 430:
	</td>		</td>
	<td>		<td>
	<p>[[Operating Systems 2014F: Tutorial 10\|~~TBA]]~~		<p>[[Operating Systems 2014F: Tutorial 10\|Projects]]
	~~</p>~~
	~~</td>~~
	~~</tr>~~
	~~<tr>~~
	~~<td>~~
	~~<p>Dec. 4, 8~~
	~~</p>~~
	~~</td>~~
	~~<td>~~
	~~<p>[[Operating Systems 2014F: Tutorial 11\|Project help~~]]
	</p>		</p>
	</td>		</td>

Soma: /* What's in your final report? */

2015-11-22T20:35:10Z

What's in your final report?

← Older revision		Revision as of 20:35, 22 November 2015
Line 22:		Line 22:
	** limitations		** limitations
	** future work		** future work
			* Statement of Joint Work
			** If this was a group project, please explain here what role each co-author had in generating the ideas for the project, doing the actual work, and writing the report.
	* References		* References
	** Be sure to cite any resources (including web pages) that significantly helped you in your work. Please do not use footnotes for citations; they should all be endnotes.		** Be sure to cite any resources (including web pages) that significantly helped you in your work. Please do not use footnotes for citations; they should all be endnotes.

Soma: /* What's in your final report? */

2015-11-22T20:34:08Z

What's in your final report?

← Older revision		Revision as of 20:34, 22 November 2015
Line 8:		Line 8:

	If you managed to implement something substantial, your report should be organized as follows:		If you managed to implement something substantial, your report should be organized as follows:
			* Title, Authors, Date, and "Class project for COMP 3000: Operating Systems" (or something like that).
	* The idea (intro)		* The idea (intro)
	* Design/high level implementation		* Design/high level implementation

Soma: /* Course Project */

2015-11-22T20:24:37Z

Course Project

← Older revision		Revision as of 20:24, 22 November 2015
Line 5:		Line 5:
	==Course Project==		==Course Project==

	'~~''Under construction'''~~		===What's in your final report?===

	~~What's in~~ your ~~final~~ report?		If you managed to implement something substantial, your report should be organized as follows:
	* The idea (intro)		* The idea (intro)
	* Design/high level implementation		* Design/high level implementation
	* implementation (problems ~~encountered)~~		* implementation
	* Evaluation ~~(does~~ it work ~~and how~~ do you know)		** What problems did you encounter?
			** How did you overcome them?
			* Evaluation
			** Does it work?
			** How do you know it works? Explain how you tested your work.
			** In particular, make sure you test your code with some significant load (e.g., building a kernel) so that you have some evidence that your modifications didn't make the kernel unstable.
	* Conclusion		* Conclusion
	** contributions		** contributions
	** limitations		** limitations
	** future work		** future work
	* ~~appendix~~: code (~~potentially~~ in patch form)		* References
			** Be sure to cite any resources (including web pages) that significantly helped you in your work. Please do not use footnotes for citations; they should all be endnotes.
			* Appendix: code (generally in patch form)
			** Please also include code inline if it makes sense as part of the implementation and evaluation sections.

	Grading Criteria		If, in the end, you more learned about how various parts of the kernel worked but you didn't managed to accomplish most of your goals, you should instead organize your report around what you learned about the kernel and how you learned it. Thus, the "design" and "implementation" portions are more about the small experiments you designed and implemented to test how the kernel works, with the evaluation part saying what results you got and what that taught you. In this case you'll in effect have multiple design, implementation, and evaluation sections, so instead organize your paper around each experiment, i.e., make a section for each experiment which describes what you did and what you learned.
	* Technical accomplishment
	* Creativity		It will be much easier to get a good grade with the first strategy (implementing and documenting a single project) rather than the second. However, if through your experiments you have learned a substantial amount about the kernel, writing up what you have learned and how you learned it can potentially result in a high grade.
	* Writing quality
			===Grading Criteria===

			Marks for projects will be given in the following categories:

			* Technical accomplishment (40%)
			* Creativity (20%)
			* Writing quality (40%)
	** Grammar, spelling		** Grammar, spelling
	** Organization		** Organization
	** Clarity/Understandability		** Clarity/Understandability

			A technically competent, well-written report will receive approximately a B grade. Exceptional projects will receive A's. Lower graded reports will have some clear faults in terms of writing, technical accomplishment, or creativity.

			Note that there is no fixed length requirement. However, projects that are less that 5 pages are unlikely to get a high grade as that means that less than a page was spent on each section, on average. The implementation and evaluation sections should be the longest ones in your report. An overly short evaluation section may lead to suspicion that you code does not work.

			===Generating Patches===

			Given the size of the Linux kernel, even at the level of individual files, you do not want to include most of that code in your report. Instead, in general you should generate a patch using the diff command:

			diff -u <old file/directory> <new file/directory>

			diff can compare files or entire directories. Feel free to edit the output of diff in order to make your code changes easy to understand. Alternately, you can just include code snippets by hand and mark your changes in a way that should be clear to any reader. Whatever you do, it should be crystal clear the difference between '''code that you wrote, code that you found on the Internet/by your peers, and code that was already in the Linux kernel'''.

			(We call the output of the diff command patch files because they can be used to [https://en.wikipedia.org/wiki/Patch_%28Unix%29 automatically make changes to source code].)

			===Formatting your report===

			You are welcome to use Microsoft Word or Libreoffice to write your report. You may find it easier to generate an aesthetically pleasing report, however, if you use LaTeX or a front end for LaTeX such as [http://pandoc.org/ pandoc]. While I will not be grading based on appearance, nicely formatted documents are always appreciated.

			In general I prefer larger text, e.g., 12 point text with one inch margins; however, if your report looks "good" I won't care. If you use LaTeX, though, please don't use the default Computer Modern fonts.

			Please submit a PDF document or a very nicely formatted plain text file. Please, please do not submit a paper in MS Word, LibreOffice, or other format.

	==Lectures and Exams==		==Lectures and Exams==