The old links didn't point to valid locations.
Replace the old links with the new links and test those changes with a
small script: https://github.com/initBasti/markdown_link_check .
______________________________________________________________
In order to find and replace the links, I used the following commands:
grep -rwohP '.' -e "\(https\:\/\/0xax.gitbooks.io\/\S*\)" > links.txt
(Find all links recursivly in the project directories and print out the
only the matches links)
Within links.txt:
Remove the '(' & ')' => :%s/\(//g and :%s/\)//g
Remove duplicates => :sort u
Test if the links work with:
python3 md_link_check.py --pattern 0xax.gitbook --output-file bad.txt
(https://github.com/initBasti/markdown_link_check)
Create replace commands:
:%s/.*/grep -rl & '.' | xargs sed -i 's#&##g'
Enter replacement URL between the 2nd & 3rd '#'
Execute commands: :w !sh
Signed-off-by: Sebastian Fricke <sebastian.fricke.linux@gmail.com>
This chapter is no longer last one from syscalls. Currently "Limits on
resources in Linux" is the last chapter.
Signed-off-by: Radek Dostál <rd@radekdostal.com>
Change is partly a verbatim copy of https://www.kernel.org/doc/Documentation/ABI/stable/vdso
Quote: "Programs that dynamically link to glibc will use the vDSO automatically. Otherwise, you can use the reference parser in tools/testing/selftests/vDSO/parse_vdso.c."
The old version of the book was slightly imprecise. It was unclear to me whether this is an optional or a default behavior.
There are multiple different system calls. Starting the introduction in plural gives a better bridge to the examples "like to read or to write to a file, to open a socket" ...