Date: Wed, 7 Apr 2010 22:00:41 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: standards@freebsd.org Subject: Non-POSIX compliant portions of FreeBSD Message-ID: <w2u7d6fde3d1004072200i6b1df9f5w780609c3265e400b@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi Standards folks,
I was recently piqued by Warner to look into open_posix_testsuite,
and I've noticed that there are some discrepancies in our compliance
with POSIX standards:
1. We don't implement any of the pieces in errno.h relating to POSIX
STREAMs (I assume this is intentional?). This includes:
- ENODATA
- ENOSR
- ENOSTR
- ETIME
- http://www.opengroup.org/onlinepubs/000095399/basedefs/errno.h.html
2. We don't define daylight or timezone in time.h -
http://www.opengroup.org/onlinepubs/009695399/basedefs/time.h.html
3. We don't define SIGPOLL -
http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html
4. We don't define SCHED_SPORADIC and friends -
http://www.opengroup.org/onlinepubs/000095399/basedefs/sched.h.html
5. We don't define the sched_param struct -
http://www.opengroup.org/onlinepubs/000095399/basedefs/sched.h.html
6. We don't define bsd_signal (snickers) -
http://www.opengroup.org/onlinepubs/000095399/functions/bsd_signal.html
7. We don't have clock_nanosleep, clock_getcpuclockid, or getdate
defined using the POSIX defined headers.
I'll keep on providing a full list of items where we aren't POSIX
compliant, but it'd be interesting to get a response about whether or
not the items I submit are known or not, and whether or not they were
conscious design decisions and/or items which need to be fixed.
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?w2u7d6fde3d1004072200i6b1df9f5w780609c3265e400b>