From: Alejandro Colomar <alx@kernel.org>
To: technoboy85@gmail.com
Cc: linux-man@vger.kernel.org, Matteo Croce <teknoraver@meta.com>
Subject: Re: [PATCH v2] proc.5: document 'subset' mount option.
Date: Tue, 14 May 2024 21:54:42 +0200 [thread overview]
Message-ID: <kum6or4dlxvb3t3td5jcssv7pzwnbr3sygsowq4aqm6yrf5crd@os52p4yb24kp> (raw)
In-Reply-To: <20240514192110.84881-1-technoboy85@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Tue, May 14, 2024 at 09:21:10PM GMT, technoboy85@gmail.com wrote:
> From: Matteo Croce <teknoraver@meta.com>
>
> The 'subset=pid' option was added in commit 6814ef2d, document it.
>
> Signed-off-by: Matteo Croce <teknoraver@meta.com>
> ---
> man/man5/proc.5 | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/man/man5/proc.5 b/man/man5/proc.5
> index 8022ca49e..2567387d3 100644
> --- a/man/man5/proc.5
> +++ b/man/man5/proc.5
> @@ -105,7 +105,12 @@ This group should be used instead of approaches such as putting
> nonroot users into the
> .BR sudoers (5)
> file.
> -.\"
> +.RE
> +.TP
> +.BR subset "=\fBpid\fP (since Linux 5.8)"
This can be simplified as:
.BR subset = pid " (since Linux 5.8)"
> +.\" commit 6814ef2d992af09451bbeda4770daa204461329e
> +Show only the specified subset of procfs hiding all top level files
> +and directories in the procfs that are not related to tasks.
> .SS Overview
> Underneath
> .IR /proc ,
> --
> 2.43.0
>
--
<https://www.alejandro-colomar.es/>
A client is hiring kernel driver, mm, and/or crypto developers;
contact me if interested.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-14 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 19:21 [PATCH v2] proc.5: document 'subset' mount option technoboy85
2024-05-14 19:54 ` Alejandro Colomar [this message]
2024-05-14 20:15 ` G. Branden Robinson
2024-05-14 20:25 ` Matteo Croce
2024-05-14 20:41 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kum6or4dlxvb3t3td5jcssv7pzwnbr3sygsowq4aqm6yrf5crd@os52p4yb24kp \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=technoboy85@gmail.com \
--cc=teknoraver@meta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).