From: "J.A. Magallon" <jamagallon@able.es>
To: "Randazzo, Michael" <RANDAZZO@ddc-web.com>
Cc: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.x POSIX Compliance/Conformance...
Date: Wed, 4 Feb 2004 22:02:12 +0100 [thread overview]
Message-ID: <20040204210212.GA2646@werewolf.able.es> (raw)
In-Reply-To: <89760D3F308BD41183B000508BAFAC4104B16F38@DDCNYNTD> (from RANDAZZO@ddc-web.com on Wed, Feb 04, 2004 at 21:18:17 +0100)
On 2004.02.04, "Randazzo, Michael" wrote:
> Where are the kernel calls defined for locks and semaphores?
>
> How come the kernel headers don't define Posix.4
> semaphores (_POSIX_SEMAPHROES) or Posix itself
> (_POSIX_VERSION is undefined)
>
The kernel internals are not nor Posix, nor SysV nor anything. It is just
by chance (or logic ;)) that some functions in kernel are named like the
userspace similars. Kernel source is in its own namespace.
One example (not a syscall, but useful I expect):
- Kernel has a 'sys_clone()' function, numbered __NR_clone
- GLibc implements a linux-specific system-call 'clone()', using sys_clone
- Glibc uses 'clone()' to implement 'fork()'
So, don't try to look for fork() inside the kernel.
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.6.2-rc3-jam1 (gcc 3.3.2 (Mandrake Linux 10.0 3.3.2-4mdk))
next prev parent reply other threads:[~2004-02-04 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 20:18 Kernel 2.x POSIX Compliance/Conformance Randazzo, Michael
2004-02-04 20:21 ` Valdis.Kletnieks
2004-02-04 20:51 ` Torrey Hoffman
2004-02-04 21:02 ` J.A. Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 20:22 Randazzo, Michael
2004-02-04 21:39 ` Richard B. Johnson
2004-02-04 19:44 Randazzo, Michael
2004-02-04 19:58 ` Valdis.Kletnieks
2004-02-04 19:30 Randazzo, Michael
2004-02-04 19:40 ` Valdis.Kletnieks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040204210212.GA2646@werewolf.able.es \
--to=jamagallon@able.es \
--cc=RANDAZZO@ddc-web.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.