From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: Re: capset() capget() syscalls
Date: Thu, 6 Sep 2012 09:22:58 +0100 [thread overview]
Message-ID: <CAK4o1WwZsgX8bOTR7NiEjjViO_uMgqvOaqGdvU+HNja_EHUtZA@mail.gmail.com> (raw)
In-Reply-To: <20120906030406.GY27715@brightrain.aerifal.cx>
On Thu, Sep 6, 2012 at 4:04 AM, Rich Felker <dalias@aerifal.cx> wrote:
>> I agree with Linus, provide all the headers in libc. I tried to write
>> some code to include all syscalls and constants needed for them, and
>> as far as I can see it is impossible with glibc due to conflicts. If
>> anyone has a set of includes that works let me know....
>
> Can you explain what you mean here?
WIth glibc I cannot seem to find a set of headers to include that will
give me access to all the system calls plus the types and constants
needed to call them. There are always conflicts. I am hoping I will be
able to with Musl.
>My impression was that the kernel developers intend for this API to be
>deprecated for use by applications, and the only reason they haven't
>replaced it with a proper kernelspace API is that they assume you'll
>be using libcap which wraps/hides the ugliness (and replaces it with
>something else that's just ugly in different ways...).
I don't see it can be deprecated if it has not been replaced... it is
one of the syscalls not generally intended for everyday use. But it is
a bit unclear.
For reference (this list is not complete), Musl is missing the
following syscalls that glibc has:
fallocate, acct, setns, sync_file_range, readahead, tee,
timerfd_create, timerfd_settime, timerfd_gettime
Musl has the following syscalls that glibc does not provide:
mknod, mknodat, clock_nanosleep
And neither provide the non obsolete
clock_getres, clock_settime, clock_gettime
So I don't think there is much rationale to this set right now...
Justin
next prev parent reply other threads:[~2012-09-06 8:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 11:51 igmar
2012-09-05 6:19 ` Rich Felker
2012-09-05 9:28 ` Igmar Palsenberg
2012-09-05 14:24 ` Rich Felker
2012-09-05 17:01 ` Justin Cormack
2012-09-06 3:04 ` Rich Felker
2012-09-06 3:10 ` John Spencer
2012-09-06 3:20 ` Rich Felker
2012-09-06 3:28 ` Kurt H Maier
2012-09-06 3:41 ` Rich Felker
2012-09-06 4:41 ` Kurt H Maier
2012-09-06 8:22 ` Justin Cormack [this message]
2012-09-06 9:28 ` Szabolcs Nagy
2012-09-06 14:23 ` Rich Felker
2012-09-07 4:56 ` Rich Felker
2012-09-08 16:02 ` Justin Cormack
2012-09-08 22:14 ` Rich Felker
2012-09-09 20:04 ` Justin Cormack
2012-09-09 20:14 ` Rich Felker
2012-09-09 21:13 ` James Cloos
2012-09-09 21:55 ` Rich Felker
2012-09-09 22:12 ` Justin Cormack
2012-09-09 22:29 ` Rich Felker
2012-09-09 22:37 ` Justin Cormack
2012-09-10 15:07 ` James Cloos
2012-09-08 21:25 ` Justin Cormack
2012-09-08 22:15 ` Rich Felker
2012-09-08 23:56 ` Rich Felker
2012-09-09 0:21 ` Rich Felker
2012-09-09 8:21 ` Justin Cormack
2012-09-09 19:40 ` Justin Cormack
2012-09-09 21:02 ` Rich Felker
2012-09-09 21:07 ` Justin Cormack
2012-09-09 21:23 ` Justin Cormack
2012-09-09 21:31 ` Justin Cormack
2012-09-09 21:58 ` Rich Felker
2012-09-09 22:14 ` Justin Cormack
2012-09-15 1:54 ` Rich Felker
2012-09-16 14:13 ` Justin Cormack
2012-09-17 2:27 ` Rich Felker
2012-09-06 11:47 ` Igmar Palsenberg
2012-09-06 11:36 ` Igmar Palsenberg
2012-09-06 14:11 ` Rich Felker
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=CAK4o1WwZsgX8bOTR7NiEjjViO_uMgqvOaqGdvU+HNja_EHUtZA@mail.gmail.com \
--to=justin@specialbusservice.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).