From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org, Jakub Wilk <jwilk@jwilk.net>
Subject: Re: [PATCH 2/2] sysctl.7: create as .so man5/proc.5
Date: Sun, 2 Apr 2023 01:28:32 +0200 [thread overview]
Message-ID: <da08294e-a491-d008-cda2-903d78e2b63f@gmail.com> (raw)
In-Reply-To: <a6w73aiesdbkrfv336oyvqg4r3mg6jti3lmqymcmnid57u5g4g@iltxswmiebf4>
[-- Attachment #1.1: Type: text/plain, Size: 881 bytes --]
On 4/2/23 01:26, наб wrote:
> On Sun, Apr 02, 2023 at 01:04:37AM +0200, Alejandro Colomar wrote:
>> On 4/1/23 00:04, наб wrote:
>>> This way "whatis sysctl" shows the list of sysctls and documentation,
>>> in addition to the syscall and program. Indeed, the latter two aren't
>>> all that useful without the former.
>>>
>>> Not a single concrete file, and it's more of an interface => goes in 7.
>> How about a SEE ALSO reference in the sysctl(8) page instead? I had
>> a look at that page, and it hints that you should look at proc(5)
>> --it mentions /proc/sys/, although there's no explicit reference to
>> proc(5)--.
> Sure, forwarded as
> https://gitlab.com/procps-ng/procps/-/merge_requests/177
Nice :)
Best,
Alex
>
> Best,
> наб
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-04-01 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 21:00 [PATCH] symlink.7: expound upon fs.protected_symlinks наб
2023-03-27 6:31 ` Jakub Wilk
2023-03-27 12:29 ` [PATCH v2] symlink.7: cross-link to proc.5 for fs.protected_symlinks наб
2023-03-31 21:44 ` Alejandro Colomar
2023-03-31 22:04 ` [PATCH 1/2] proc.5: add "system information, and sysctl" to .SH наб
2023-03-31 22:11 ` Alejandro Colomar
2023-04-01 22:58 ` Alejandro Colomar
2023-03-31 22:04 ` [PATCH 2/2] sysctl.7: create as .so man5/proc.5 наб
2023-03-31 22:14 ` Alejandro Colomar
2023-04-01 23:04 ` Alejandro Colomar
2023-04-01 23:26 ` наб
2023-04-01 23:28 ` Alejandro Colomar [this message]
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=da08294e-a491-d008-cda2-903d78e2b63f@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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