lostecho/ostep-projects
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Typos in xv6 vm proj

Browse Source
This commit is contained in:
Remzi Arpaci-Dusseau
2018-03-04 15:43:09 -06:00
parent 7c055ea4eb
commit f45d8f5c37
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
vm-xv6-intro/README.md
View File

@@ -23,7 +23,7 @@ again, this project is mostly about understanding the code, and not writing
very much. Look at how **exec()** works to better understand how address very much. Look at how **exec()** works to better understand how address
spaces get filled with code and in general initialized. spaces get filled with code and in general initialized.
You should also look at [code fork()], in particular the part where the You should also look at `fork()`, in particular the part where the
address space of the child is created by copying the address space of the address space of the child is created by copying the address space of the
parent. What needs to change in there? parent. What needs to change in there?
@@ -41,7 +41,7 @@ clearly the entry point will have to be somewhere else (e.g., the next page,
or 0x1000). Thus, something in the makefile will need to change to reflect or 0x1000). Thus, something in the makefile will need to change to reflect
this as well. this as well.
## Read-only Code] ## Read-only Code
In most operating systems, code is marked read-only instead of In most operating systems, code is marked read-only instead of
read-write. However, in xv6 this is not the case, so a buggy program could read-write. However, in xv6 this is not the case, so a buggy program could