linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] pid_namespaces(7): minor grammar tweaks
@ 2014-10-27 20:42 Mike Frysinger
       [not found] ` <1414442573-19334-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Mike Frysinger @ 2014-10-27 20:42 UTC (permalink / raw)
  To: Michael Kerrisk; +Cc: linux-man-u79uwXL29TY76Z2rM5mHXA

---
 man7/pid_namespaces.7 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index db6618a..2090101 100644
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -128,7 +128,7 @@ and so will result in the usual actions associated with those signals
 
 Starting with Linux 3.4, the
 .BR reboot (2)
-system causes a signal to be sent to the namespace "init" process.
+system call causes a signal to be sent to the namespace "init" process.
 See
 .BR reboot (2)
 for more details.
@@ -154,7 +154,7 @@ In this context, "visible" means that one process
 can be the target of operations by another process using
 system calls that specify a process ID.
 Conversely, the processes in a child PID namespace can't see
-processes in the parent and further removed ancestor namespace.
+processes in the parent and further removed ancestor namespaces.
 More succinctly: a process can see (e.g., send signals with
 .BR kill (2),
 set nice values with
@@ -243,7 +243,7 @@ will defeat that.
 .BR CLONE_VM
 requires all of the threads to be in the same PID namespace,
 because, from the point of view of a core dump,
-if two processes share the same address space they are threads and will
+if two processes share the same address space then they are threads and will
 be core dumped together.
 When a core dump is written, the PID of each
 thread is written into the core dump.
-- 
2.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] pid_namespaces(7): minor grammar tweaks
       [not found] ` <1414442573-19334-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
@ 2014-10-28 13:15   ` Michael Kerrisk (man-pages)
  0 siblings, 0 replies; 2+ messages in thread
From: Michael Kerrisk (man-pages) @ 2014-10-28 13:15 UTC (permalink / raw)
  To: Mike Frysinger
  Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w,
	linux-man-u79uwXL29TY76Z2rM5mHXA

Thanks, Mike. Applied.

Cheers,

Michael


On 10/27/2014 09:42 PM, Mike Frysinger wrote:
> ---
>  man7/pid_namespaces.7 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
> index db6618a..2090101 100644
> --- a/man7/pid_namespaces.7
> +++ b/man7/pid_namespaces.7
> @@ -128,7 +128,7 @@ and so will result in the usual actions associated with those signals
>  
>  Starting with Linux 3.4, the
>  .BR reboot (2)
> -system causes a signal to be sent to the namespace "init" process.
> +system call causes a signal to be sent to the namespace "init" process.
>  See
>  .BR reboot (2)
>  for more details.
> @@ -154,7 +154,7 @@ In this context, "visible" means that one process
>  can be the target of operations by another process using
>  system calls that specify a process ID.
>  Conversely, the processes in a child PID namespace can't see
> -processes in the parent and further removed ancestor namespace.
> +processes in the parent and further removed ancestor namespaces.
>  More succinctly: a process can see (e.g., send signals with
>  .BR kill (2),
>  set nice values with
> @@ -243,7 +243,7 @@ will defeat that.
>  .BR CLONE_VM
>  requires all of the threads to be in the same PID namespace,
>  because, from the point of view of a core dump,
> -if two processes share the same address space they are threads and will
> +if two processes share the same address space then they are threads and will
>  be core dumped together.
>  When a core dump is written, the PID of each
>  thread is written into the core dump.
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-10-28 13:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-27 20:42 [PATCH] pid_namespaces(7): minor grammar tweaks Mike Frysinger
     [not found] ` <1414442573-19334-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-10-28 13:15   ` Michael Kerrisk (man-pages)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).