POSIX describes C library functions, not the actual system calls, right? So isn't this more of
a glibc issue, since its role is to provide library functions which invoke the proper system
calls?
Posted Aug 20, 2008 20:06 UTC (Wed) by asamardzic (guest, #27161)
[Link]
POSIX (actualy SUS nowadays) describes "system interfaces", which are exposed as C functions, usually directly mapping to actual system calls. As the links behavior is tightly coupled with file system implementation, related code is usually part of the kernel, thus link() has not much to do in userspace, and this particular issue probably has to be resolved within the kernel code.
System calls vs. library functions
Posted Aug 20, 2008 20:35 UTC (Wed) by nix (subscriber, #2304)
[Link]
Pedant point: POSIX incorporated all of SuS some years back; the result is
called POSIX. (Confusing, I know.)
System calls vs. library functions
Posted Aug 21, 2008 3:50 UTC (Thu) by michaelk (subscriber, #1978)
[Link]
Pedant point: POSIX incorporated all of SuS some years back; the result is called POSIX. (Confusing, I know.)
Well, to be extrememly pedantic, the work of the Austin group consolidated earlier POSIX standards and SUSv2, to create a new standard that defines two levels of conformance: base conformance (aka POSIX.1-2001), and XSI (X/Open System Interface) conformance (aka SUSv3). So the result is called both POSIX and SUS.
System calls vs. library functions
Posted Aug 21, 2008 3:52 UTC (Thu) by michaelk (subscriber, #1978)
[Link]
Posted Aug 21, 2008 9:06 UTC (Thu) by nix (subscriber, #2304)
[Link]
That manpage, and the posixoptions manpage it links to, are excellently done. (It is a tad
unclear, though, whether posixoptions describes the meaning of the options or whether it
instead describes what values those options have got on a Linux (glibc?) system...)