diff options
| author | dillon <dillon@FreeBSD.org> | 2001-08-24 19:45:59 +0000 |
|---|---|---|
| committer | dillon <dillon@FreeBSD.org> | 2001-08-24 19:45:59 +0000 |
| commit | 5844ade67e0c0c49b90b0ef04b06eb2a2f8f2740 (patch) | |
| tree | faed8a53baf32f482b50ddb530a11831dd6750bb /lib | |
| parent | a8a9c78664ce34202a2458896979156283ffe4e3 (diff) | |
| download | FreeBSD-src-5844ade67e0c0c49b90b0ef04b06eb2a2f8f2740.zip FreeBSD-src-5844ade67e0c0c49b90b0ef04b06eb2a2f8f2740.tar.gz | |
Ok, third time is the charm. VM_INHERIT_XXX -> INHERIT_XX (use the same
semantics as PROT_XXX vs VM_PROT_XXX separating user-space defines from
kernel defines).
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/libc/sys/minherit.2 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/libc/sys/minherit.2 b/lib/libc/sys/minherit.2 index 6af3c88..e78c1d7 100644 --- a/lib/libc/sys/minherit.2 +++ b/lib/libc/sys/minherit.2 @@ -74,14 +74,14 @@ to share a block of memory between parent and child that has been mapped MAP_PRIVATE. That is, modifications made by parent or child are shared but the original underlying file is left untouched. .Bl -tag -width MAP_HASSEMAPHORE -.It Dv VM_INHERIT_SHARE +.It Dv INHERIT_SHARE This option causes the address space in question to be shared between parent and child. It has no effect on how the original underlying backing store was mapped. -.It Dv VM_INHERIT_NONE +.It Dv INHERIT_NONE This option prevents the address space in question from being inherited at all. The address space will be unmapped in the child. -.It Dv VM_INHERIT_COPY +.It Dv INHERIT_COPY This option causes the child to inherit the address space as copy-on-write. This option also has an unfortunate side effect of causing the parent address space to become copy-on-write when the parent forks. If the |
