> According to /usr/src/sys/kern/syscalls.master, sysctl is system call
> number 202. But its manual page is in section 3, at
> Should it actually be in section 2?
It used to be wrapped in an odd way. The manual page could now be renamed,
but we have to find all the tendrils.
date: 2015/09/13 17:08:03; author: guenther; state: Exp; lines: +4 -4; commitid: BssYI6s6zozAyfkk;
Rename __sysctl syscall to just sysctl, as the userland wrapper is no longer
ok deraadt@ jsing@
Theo de Raadt wrote on Thu, Jan 11, 2018 at 08:48:32PM -0700:
> Anthony Coulter wrote:
>> Should it actually be in section 2?
> It used to be wrapped in an odd way.
> The manual page could now be renamed,
We rarely do that, though. There are many edge cases and historical
accidents regarding which pages are in which section, and the benefit
of moving them is limited.
> but we have to find all the tendrils.
Finding them is easy:
$ man -k Xr~sysctl.3 | wc -l
So, we change sixty manual pages referencing sysctl(3) and lose
the history of the file? I'm not convinced it's worth the work,
and the churn.
Then again, if a developer wants to do the work, i don't object
to it either (non-developers please refrain from sending patches
in this case, that wouldn't reduce the work for the developer
actually committing it).