From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: capset() capget() syscalls
Date: Thu, 6 Sep 2012 11:28:04 +0200 [thread overview]
Message-ID: <20120906092804.GC1104@port70.net> (raw)
In-Reply-To: <CAK4o1WwZsgX8bOTR7NiEjjViO_uMgqvOaqGdvU+HNja_EHUtZA@mail.gmail.com>
* Justin Cormack <justin@specialbusservice.com> [2012-09-06 09:22:58 +0100]:
> 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.
>
so these are functions not present in any standard and any libc
why do you want to include them in musl?
that would mean applications will break using glibc vs musl
why not use a separate library (libcap2)
> 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.
>
this is the question
and we need an authorative answer
> 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
>
these are non-standard functions, but the non-broken
ones should be provided eventually
the ugly ones are those which glibc declares in standard
headers (eg readahead, tee)
(timerfd* functions are easy to provide as they live in
their own header)
some of them might be obsolete
(eg posix_fallocate is in musl and can be used instead
of fallocate, and posix_fadvise may be used instead of
readahead)
> And neither provide the non obsolete
> clock_getres, clock_settime, clock_gettime
>
these are posix standard api and musl provides them
if the necessary feature test macros are defined when
time.h is included
next prev parent reply other threads:[~2012-09-06 9:28 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
2012-09-06 9:28 ` Szabolcs Nagy [this message]
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=20120906092804.GC1104@port70.net \
--to=nsz@port70.net \
--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).