

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Main points of this exam paper are: Machine Malfunctioning, Traditional Memory, Memory Object, Modern Memory, Traditional Approach, Access a File, Parameter to Subsequent
Typology: Exams
1 / 2
This page cannot be seen from the preview
Don't miss anything!


There are five questions on this exam. Please answer all five questions. You have 90 minutes to complete this exam. Good luck!
Briefly describe two advantages and one disadvantage of the modern memory object approach to virtual address spaces compared with the traditional approach.
Describe as many advantages or disadvantages to the alternative scheme. Why do most file systems require files to be opened before being read and written? What is the purpose of the CLOSE system call?
Alice: "I learned from the Lampson paper that protection mechanisms are just different ways of expression a sparse access control matrix."
Bob: "Really? I just took an algorithms class where we studied and implemented sparse matrices. You're implementing a free Linux-like operating system ( Alix ), so why don't you use my code? It has a very compact representation of sparse matrices, with a default value of 0.0, and while you won't need the other efficient operations such as matrix add, multiply etc, This code has been proven correct!"
If Alice were to take Bob's code and plug it into Alix , would it probably satisfy all of the needs of an access control system? Give reasons why or why not.
As captain of the crew I had had extensive experience (dating back to 1958) in making basic software dealing with real-time interrupts, and I knew by bitter experience that as a result of the irreproducibility of the interrupt moments a program error could present itself misleadingly like an occasional machine malfunctioning. As a result I was terribly afraid. Having fears regarding the possibility of debugging, we decided to be as careful as possible and, prevention being better than cure, to try to prevent nasty bugs from entering the construction.
What do we now call such a bug that "could present itself misleadingly like an occasional machine malfunctioning"? How did the layered architecture approach help prevent such bugs from entering the construction?