From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: <fstab.h> / getfsent(3) and friends
Date: Sun, 25 Mar 2018 00:24:01 -0700 [thread overview]
Message-ID: <CAMKF1sq7jJQWHU+cfy9EPqemNbTqwQjcbTP4KP+JXzi-HkCeyg@mail.gmail.com> (raw)
In-Reply-To: <20180325005724.GE1436@brightrain.aerifal.cx>
On Sat, Mar 24, 2018 at 5:57 PM, Rich Felker <dalias@libc.org> wrote:
> On Sat, Mar 24, 2018 at 07:45:52PM -0500, A. Wilcox wrote:
>> Would a small module implementing <fstab.h> be accepted upstream into
>> musl? I looked on the mailing list and wiki and didn't see anyone
>> asking this question before.
>>
>>
>> This header and API are used by at least:
>>
>> - filelight (disk space usage tracker)
>>
>> - K3b (KDE disc ripper)
>>
>> - KDELibs 3.x, used by TDE (Trinity Desktop Environment, light Qt DE)
>>
>> - MythTV and XBMC (media center/players)
>>
>> - Pegasus (scientific computation management system by USC)
>>
>>
>> Since this is already implemented by glibc[1], FreeBSD[2], NetBSD[3],
>> OpenBSD[4], Mac OS X[5], AIX[6], HP-UX[7], QNX[8], and
>> others[9][10][11][12], all but TDE's fork of KDELibs 3 don't check for
>> it in configure. I would be more than happy to implement and maintain this.
>
> Seems plausible that it would be reasonable but I haven't looked at
> the specifics. How large would the implementation be? Are there ugly
> issues with thread-safety/global state that make the apis hard to use
> reasonably? Anything weird it has to hook into?
>
they dont look like being thread safe or async safe atleast in glibc
docs. perhaps you can use gnulib
implementation in apps where its needed.
> Rich
next prev parent reply other threads:[~2018-03-25 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 0:45 A. Wilcox
2018-03-25 0:57 ` Rich Felker
2018-03-25 7:24 ` Khem Raj [this message]
2018-09-10 2:30 ` A. Wilcox
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=CAMKF1sq7jJQWHU+cfy9EPqemNbTqwQjcbTP4KP+JXzi-HkCeyg@mail.gmail.com \
--to=raj.khem@gmail.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).