[libseccomp-discuss] Expose arch_syscall_resolve_num as seccomp_syscall_resolve_num public API

2012-12-04 Thread Thiago Marcos P. Santos
I would like to expose arch_syscall_resolve_num as a public API the same way as it is done for arch_syscall_resolve_name. Practical usage: On the syscall handler, you might want to print some pretty error message like: "Error: open() syscall is not allowed." Should I move forward with my patch?

[libseccomp-discuss] [PATCH] doc: fix seccomp_syscall_resolve_name manpage

2012-12-04 Thread Thiago Marcos P. Santos
0001-doc-fix-seccomp_syscall_resolve_name-manpage.patch Description: Binary data -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support I