Remove text saying that specifying invalid flags "is likely

to cause compatibility problems" since the kernel now
(2.6.17-rc1) contains an explicit check for invalid buts
with a consequent EINVAL error.
This commit is contained in:
Michael Kerrisk 2006-04-03 23:55:40 +00:00
parent 0c373d0150
commit cdc9620e3a
1 changed files with 0 additions and 10 deletions

View File

@ -96,16 +96,6 @@ as well.
.\" Unshare virtual memory, so that the calling process no
.\" longer shares its virtual address space with any other process.
.PP
Specifying any other bits in
.I flags
is likely to cause compatibility problems if the corresponding
.B CLONE_*
values are implemented in future kernels.
Avoid doing this.
.\" FIXME . Check if a later kernel (e.g., 2.6.17) makes explicit
.\" checks to prevent unimplemented bits being set in 'flags'.
.\"
.PP
If
.I flags
is specified as zero, then