Messages in this thread | | | Date | Wed, 4 Feb 2004 16:39:07 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | RE: Kernel 2.x POSIX Compliance/Conformance... |
| |
On Wed, 4 Feb 2004, Randazzo, Michael wrote:
> ok...I think I get it.... > > I can't use any of the posix functions in > device drivers (modules).....is this correct? > > M.
You cannot ever use any 'C' runtime library functions in your modules. This means you cannot use open(), close(), read(), write(), lseek(), etc. However, the kernel has some of its own POSIX-compliant functions like memset(), memcpy(), strcpy(), etc. You can look in ../linux-nn.nn/lib or look through the headers to see what's available. There are semaphones and other locking mechanisms available for use in the kernel which, I recall, was your first inquiry.
Cheers, Dick Johnson Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips). Note 96.31% of all statistics are fiction.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |