[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMKF1sq7jJQWHU+cfy9EPqemNbTqwQjcbTP4KP+JXzi-HkCeyg@mail.gmail.com>
Date: Sun, 25 Mar 2018 00:24:01 -0700
From: Khem Raj <raj.khem@...il.com>
To: musl@...ts.openwall.com
Subject: Re: <fstab.h> / getfsent(3) and friends
On Sat, Mar 24, 2018 at 5:57 PM, Rich Felker <dalias@...c.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
