diff options
author | Eric Wong <e@80x24.org> | 2024-01-29 21:23:19 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2024-01-30 08:28:45 +0000 |
commit | 0a989e8abd36599abe13c36c2b30ab75232f9756 (patch) | |
tree | 96729179634660501350bf818dbf1bf5a1a70e9d /MANIFEST | |
parent | 8c911b8ea278ad36fcff0cee9a8ae3c061bae3ac (diff) | |
download | public-inbox-0a989e8abd36599abe13c36c2b30ab75232f9756.tar.gz |
While syscall symbols (e.g. SYS_*) have changed on us in FreeBSD during the history of Sys::Syscall and this project and did bite us in some cases; the actual numbers don't get recycled for new syscalls. We're also fortunate that sendmsg and recvmsg syscalls and associated msghdr and cmsg structs predate the BSD forks and are compatible across all the BSDs I've tried. OpenBSD routes Perl `syscall' through libc; while NetBSD + FreeBSD document procedures for maintaining backwards compatibility. It looks like Dragonfly follows FreeBSD, here. Tested on i386 OpenBSD, and amd64 {Free,Net,Open,Dragonfly}BSD This enables *BSD users to use lei, -cindex and future SCM_RIGHTS-only features without needing Inline::C. [1] https://cvsweb.openbsd.org/src/gnu/usr.bin/perl/gen_syscall_emulator.pl [2] https://www.netbsd.org/docs/internals/en/chap-processes.html#syscall_versioning [3] https://wiki.freebsd.org/AddingSyscalls#Backward_compatibily
Diffstat (limited to 'MANIFEST')
0 files changed, 0 insertions, 0 deletions