FD_CLR FD_ISSET FD_SET FD_ZERO accept acct adjtime adjtimex bdflush
bind break brk cacheflush capget capset chroot clone connect
-create_module delete_module execve exit fcntl flock fork
+create_module delete_module execve exit flock
fstatfs ftime getcontext getdents getdomainname
getdtablesize getgroups gethostid gethostname getitimer
getpeername getpriority getrlimit getrusage getsockname getsockopt
-gettimeofday gtty idle init_module ioctl ioctl_list ioperm iopl listen
+gettimeofday gtty idle init_module ioctl_list ioperm iopl listen
llseek lock madvise mincore mknod mlock mlockall
modify_ldt mount mprotect mpx mremap msgctl msgget msgop msgrcv msgsnd
munlock munlockall nanosleep nice pause poll
sigpending sigprocmask sigreturn sigsetmask sigsuspend sigvec socket
socketcall socketpair ssetmask statfs stime stty swapoff swapon
syscalls sysctl sysfs sysinfo syslog time times
-ulimit umount uname ustat utime utimes vfork vhangup wait wait3
-wait4 waitpid write writev
+ulimit umount uname ustat utime utimes vfork vhangup wait3
+wait4 write writev
4) In the spec but not implemented:
9) proper alien definitions of structures [ possibly an sb-grovel
problem, but the way we define calls exposes the problem -- see
-readdir() ]
+readdir() ] [ isn't this done? ]
+
+10) some functions (e.g. fdatasync, putenv) have a return value which
+is purely an error indicator. Currently we're returning the 0 on
+success, but maybe it would make more sense for them to return
+(values).