Well yes, if the syscall is correctly implemented in the library,
there's no problem.
> Besides, I don't think having a
> /proc/syscalls would be any better than having to do ifdefs or use
> kernel headers.
#ifdef may be hard pressed to identify a specific kernel with a
specific patch. Kernel headers are obviously a solution (although
this violates the "user space must never include kernel headers"
pseudo-rule), but add the problem of needing to identify the
"current" source tree, which is a configuration step almost always
requiring manual intervention.
My suggestion for /proc/syscalls isn't entirely serious, but it
would be nice if we could eventually solve this problem ...
- Werner
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/