course site:
https://omscs.gatech.edu/cs-6210-advanced-operating-systems

-------------------------------------------------------------------------------
The test is all Y/N questions:

1. Do you know the conditions under which a process/thread may join the
ready queue and leave the ready queue?

2. Can you name all the steps that happen during a context switch?

3. Can you name at least three different types of interprocess
communication?

4. Do you know what is meant by Data Race in a parallel program?

5. In a preemptive scheduler, do you understand what the word
“preemptive” refers to?

6. Do you understand the difference between “round robin”,
“shortest-job-first”, and “priority scheduling”?

7. Do you know the name for a section of code that accesses variables or
resources that are shared between multiple threads of execution?

8. Do you know the necessary and sufficient conditions for deadlock to
occur?

9. Do you understand why, when, and how to use mutual exclusion?

10. Can you describe the role the translation look-aside buffer (TLB)
plays in a virtual memory system?

11. Do you understand the difference between a “segment” and a “page” in
a memory hierarchy?

12. Do you know the difference between a “page” and a “frame” in a
virtual memory system?

13. Do you know the difference between “first-in, first-out”,
“leastrecently-used”, and “least-frequently-used” replacement policies?

14. Do you know what it means for a process to “trap” to the kernel?

15. Can you name the mechanism by which asynchronous hardware events may
notify the CPU (and thus the kernel) of an event?

16. Can you explain why “ports” are necessary in network communication?

17. Do you know what processor cache (e.g. L1, L2) has to do with
context switches?

18. Have you written a substantial (i.e. not “Hello World”) program in C
or C++?

19. Have you written a multi-threaded program?

20. Have you written a networked program using a sockets API (e.g.
Linux/POSIX sockets or winsock)?

21. Have you written a program that handles one or more signals in
Linux/POSIX?

22. Do you know how to take timing measurements of a program?
-------------------------------------------------------------------------------

https://omscs.gatech.edu/sites/default/files/documents/2023/CS%206210-Diagnostic%20Preparedness%20Test.pdf

Aceing that course would be no problem for some of the delusional
blowhards here on cola.

PhysFitFreak: "It's a piece of cake to write an operating system."
Feeb : "Very nicely stated."

LMAO!

On Thu, 5 Sep 2024 19:27:59 -0400, DFS wrote:

> 3. Can you name at least three different types of interprocess
> communication?

You'd better leave out shared memory and message queues on Windows...
There may be things called that in the Microsoft world but they're far
from POSIX.

20. Have you written a networked program using a sockets API (e.g.
Linux/POSIX sockets or winsock)?

WSASockets is sort of like POSIX sockets with gotchas.

21. Have you written a program that handles one or more signals in
Linux/POSIX?

Good luck with that. That can be limited form of IPC. Process A signals
Process B to tell it the laundry is ready.

On 6 Sep 2024 00:59:31 GMT, rbowman <bowman@montana.com> wrote in
<ljv2fjFha5aU3@mid.individual.net>:

> On Thu, 5 Sep 2024 19:27:59 -0400, DFS wrote:
>
>> 3. Can you name at least three different types of interprocess
>> communication?
>
> You'd better leave out shared memory and message queues on Windows...
> There may be things called that in the Microsoft world but they're far
> from POSIX.
>
> 20. Have you written a networked program using a sockets API (e.g.
> Linux/POSIX sockets or winsock)?
>
> WSASockets is sort of like POSIX sockets with gotchas.
>
> 21. Have you written a program that handles one or more signals in
> Linux/POSIX?
>
> Good luck with that. That can be limited form of IPC. Process A signals
> Process B to tell it the laundry is ready.

Should mention that in the man page section of fcntl(2) dealing with
signals, it adds a short paragraph:

"Using these mechanisms, a program can implement fully asynchronous I/O
without using select(2) or poll(2) most of the time."

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
OS: Linux 6.11.0-rc6 Release: Mint 21.3 Mem: 258G
"For large values of 1, 1 equals 2, for small values of 2."

rbowman wrote this copyrighted missive and expects royalties:

> On Thu, 5 Sep 2024 19:27:59 -0400, DFS wrote:
>
>> 3. Can you name at least three different types of interprocess
>> communication?
>
> You'd better leave out shared memory and message queues on Windows...
> There may be things called that in the Microsoft world but they're far
> from POSIX.
>
> 20. Have you written a networked program using a sockets API (e.g.
> Linux/POSIX sockets or winsock)?
>
> WSASockets is sort of like POSIX sockets with gotchas.
>
> 21. Have you written a program that handles one or more signals in
> Linux/POSIX?
>
> Good luck with that. That can be limited form of IPC. Process A signals
> Process B to tell it the laundry is ready.

poll(3P) is interesting. Used in JACK and gettext(), for example.

signal(3P) is also heavily used, if my grep of all the 3rd-party projects I've
downloaded serves me well.

(Didn't bother to see what Doof posted).

--
Emerson's Law of Contrariness:
Our chief want in life is somebody who shall make us do what we
can. Having found them, we shall then hate them for it.

vallor wrote this copyrighted missive and expects royalties:

> On 6 Sep 2024 00:59:31 GMT, rbowman <bowman@montana.com> wrote in
> <ljv2fjFha5aU3@mid.individual.net>:
>
>> On Thu, 5 Sep 2024 19:27:59 -0400, DFS wrote:
>>
>>> 3. Can you name at least three different types of interprocess
>>> communication?
>>
>> You'd better leave out shared memory and message queues on Windows...
>> There may be things called that in the Microsoft world but they're far
>> from POSIX.
>>
>> 20. Have you written a networked program using a sockets API (e.g.
>> Linux/POSIX sockets or winsock)?
>>
>> WSASockets is sort of like POSIX sockets with gotchas.
>>
>> 21. Have you written a program that handles one or more signals in
>> Linux/POSIX?
>>
>> Good luck with that. That can be limited form of IPC. Process A signals
>> Process B to tell it the laundry is ready.
>
> Should mention that in the man page section of fcntl(2) dealing with
> signals, it adds a short paragraph:
>
> "Using these mechanisms, a program can implement fully asynchronous I/O
> without using select(2) or poll(2) most of the time."

Used in some of Python's C code.

--
In recognizing AT&T Bell Laboratories for corporate innovation, for its
invention of cellular mobile communications, IEEE President Russell C. Drew
referred to the cellular telephone as a "basic necessity." How times have
changed, one observer remarked: many in the room recalled the advent of
direct dialing.
-- The Institute, July 1988, pg. 11