Date: Wed, 11 Jul 2001 21:34:17 -0500 From: Mike Karels <karels@bsdi.com> To: arch@freebsd.org Subject: syscall numbering Message-ID: <200107120234.f6C2YLC14835@redrock.eng.bsdi.com>
next in thread | raw e-mail | index | archive | help
I am sending this message at Jordan's suggestion after corresponding with him. The subject is coordination of system call numbers. As some of you probably know, the syscall.master file in Berkeley BSD releases had some ranges reserved for "vendors". Unfortunately, both BSDI (now Wind River) and their customers were "vendors", and there have been some collisions. I would now like to reserve another range of system calls for those customers. This would not be of interest to FreeBSD, except that BSD/OS also picks up system calls from FreeBSD, and FreeBSD has a number of BSD/OS-compatible calls as well as other entries for compatibility with NetBSD and/or OpenBSD. In theory, it would be nice to coordinate all of this globally, but I understand that NetBSD doesn't even have consistent numbering across all of their platforms. I'm sure we won't be able to prevent conflicts completely, but it is convenient that we can mostly use a single system call table. For now, I'm tempted to reserve 400-449 for BSD/OS customers. FreeBSD seems to be using 300 up, to 374 currently, and BSD/OS calls are all below that. Does this sound plausible? Does that leave enough for FreeBSD expansion? I'm happy to consider other suggestions, including some larger level of coordination. Feel free to contact me directly, off the list. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107120234.f6C2YLC14835>