lkml.org 
[lkml]   [2004]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRE: 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/

\
 
 \ /
  Last update: 2005-03-22 14:00    [W:1.428 / U:1.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site