From: Michael Kerrisk Date: Sat, 27 Jul 2019 07:40:34 +0000 (+0200) Subject: pivot_root.2: Rework the text on "future changes" to reflect that 20 years have passed X-Git-Tag: man-pages-5.03~117 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a94f69d6db1f7e337f28b8f236c3ec6db0d9dd96;p=thirdparty%2Fman-pages.git pivot_root.2: Rework the text on "future changes" to reflect that 20 years have passed Some of the text was written long ago, and hinted that things might change in the future. However, 20 years have passed and these details have not changed, so rework the text to hint at that fact. Signed-off-by: Michael Kerrisk --- diff --git a/man2/pivot_root.2 b/man2/pivot_root.2 index 569faa5640..0428a5eb3e 100644 --- a/man2/pivot_root.2 +++ b/man2/pivot_root.2 @@ -50,8 +50,12 @@ root and current working directory to \fInew_root\fP before invoking .PP The paragraph above is intentionally vague because the implementation of .BR pivot_root () -may change in the future. -Currently, +may change in the future +(or so it was thought when this system call was first added). +However, +the behavior on this point has remained consistent since +.BR pivot_root () +was first implemented: .BR pivot_root () changes the root directory and the current working directory of each process or thread in the same mount namespace to @@ -61,7 +65,7 @@ This is necessary in order to prevent kernel threads from keeping the old root directory busy with their root and current working directory, even if they never access the filesystem in any way. -In the future, there may be a mechanism for +Perhaps one day there may be a mechanism for kernel threads to explicitly relinquish any access to the filesystem, such that this fairly intrusive mechanism can be removed from .BR pivot_root ().