Re: reference syscall.h in pledge.2

[Theo de Raadt]

>Does it make sense to reference the syscall numbers in pledge(2)?

No not really.  By 5.9 release the kernel printf's will go away,
and people won't get such alerts.  Maybe they will get kernel log's,
but I will consider generating them with system call names.

reference syscall.h in pledge.2

[Jan Stary]

Does it make sense to reference the syscall numbers in pledge(2)?

Jan


--- /usr/src/lib/libc/sys/pledge.2  Thu Oct 15 00:39:04 2015
+++ ./pledge.2  Wed Oct 21 09:41:26 2015
@@ -468,6 +468,9 @@ All other paths will return
 .Er ENOENT .
 .Sh RETURN VALUES
 .Rv -std
+.Sh FILES
+.Pa /usr/include/sys/syscall.h
+defines the syscall numbers.
 .Sh ERRORS
 .Fn pledge
 will fail if: