Modify app-interact chapter #76
Conversation
SorinAlexB
added
the
needs-rendering
github-actions
bot
added
area/content
There was a problem hiding this comment.
The build fails because you made some indentation errors in config.yaml. However, I reckon its format isn't the most user-friendly. I made a comment explaining how to fix them.
I skimmed through the overall structure and pointed out a few things to change. I'll look deeper into the content once the website can be built (I also suggested how to do that). In addition to these changes, modify your commit message to:
chapter/app-interact: Restructure the chapter according to OpenEducationHub methodology
<add a description here>
4fa948e to
a6d7dcf
Compare
There was a problem hiding this comment.
Move the "Practice" sections from the reading/ sections to each task's readme.
SorinAlexB
force-pushed
the
translate_app-interact
branch
from
a6d7dcf to
2f40d33
Compare
…ionHub methodology Add app-interact to OpenEducation methodology Signed-off-by: Sorin Birchi <[email protected]>
SorinAlexB
force-pushed
the
translate_app-interact
branch
from
2f40d33 to
20daa03
Compare
github-actions
bot
added
the
kind/improve
teodutu
added
needs-rendering
|
Published at https://cs-pub-ro.github.io/operating-systems/76/ |
There was a problem hiding this comment.
The lab content looks alright. Perhaps you can rename it to something more accurate such as "Investigate Applications". Also see my suggestions below inline.
- You also need to move the slides from
content/chapters/app-interact/lecturetochapters/app-interact/<inidivual-subchapters>/slides/ - Add the following line to the end of each task's
README.md: "If you're having difficulties solving this task, go through [this](link to the relevant section in reading/) reading material." - Mention the path to the support files in each task so students can get there more easily.
There was a problem hiding this comment.
Move this task to guides/ because there's nothing for students to do individually and the README.md gives a complete rundown of what they're supposed to do.
| Each worker will receive 2 characters instead of one, defining an interval to search. | ||
| For example, the first worker will receive `a` and `f`, meaning it will brute-force passwords starting with `a`, `b`, `c`, `d`, `e`, or `f`, the second `g` - `l`, and so on. | ||
|
|
||
| Check that the `worker` function is indeed called from different worker processes. |
There was a problem hiding this comment.
| Check that the `worker` function is indeed called from different worker processes. | |
| Check that the `worker()` function is indeed called from different worker processes. |
|
|
||
| Check that the `worker` function is indeed called from different worker processes. | ||
| One simple way to do this is to print out the current process ID at the beginning of the function. | ||
| To get the current process ID, use the `getpid` function from the `os` module. |
There was a problem hiding this comment.
| To get the current process ID, use the `getpid` function from the `os` module. | |
| To get the current process ID, use the `getpid()` function from the `os` module. |
Prerequisite Checklist
Description of changes