mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Raphael Cohn <raphael.cohn@stormmq.com>
To: musl@lists.openwall.com
Subject: Re: What would make musl 1.2?
Date: Fri, 13 Feb 2015 15:27:45 +0530	[thread overview]
Message-ID: <CACCP0Grkh4QjhL-9R-VkXuhUrzCAJ7M=q+9zsyE2EFC4JVowbw@mail.gmail.com> (raw)
In-Reply-To: <CACCP0GpVO+EOZiCqwoQhrOWypHV-h4h2v0O5CnsJNuewzfwMMQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]

Actually, answering my own question - a quick back of the packet
calculation suggests about 8,500 packages in OpenBSD, vs 65,000+ for Debian
- although it does depend how you count. And there are a lot more
'unofficial' Debian repos and packages, too... There's no doubt that
OpenBSD includes the most popular.

On 13 February 2015 at 15:20, Raphael Cohn <raphael.cohn@stormmq.com> wrote:

> Do they use a third party support lib?
>
> If it's possible to support use cases with a third party lib, then I'm
> less concerned - provided that that lib also works with musl. Given the
> nature of ucontext, that may not be so. A musl native solution would be
> optimal for performance - and performance is a common reason for going down
> this route. It allows for far greater scale in certain server designs then
> either thread-per-connection or a thread-pool can do.
>
> Out of interest, how many packages are in the OpenBSD repository? How does
> it compare to Debian's, say? For me, Debian's repo contents is a yardstick
> of what Linux + Musl could be expected to work with.
>
>
> On 13 February 2015 at 15:08, Anthony J. Bentley <anthony@cathet.us>
> wrote:
>
>> Raphael Cohn writes:
>> > Is there any possibility of adding in the ucontext.h functions? I know
>> > they're deprecated, but they're still widely used - particularly by go
>> for
>> > goroutines, IIRC.
>>
>> It's worth mentioning that OpenBSD doesn't have ucontext, so given the
>> size of its package repository (which also contains Go), ucontext can't
>> be *that* widely used.
>>
>> --
>> Anthony J. Bentley
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2423 bytes --]

  reply	other threads:[~2015-02-13  9:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13  7:46 Rich Felker
2015-02-13  9:29 ` Raphael Cohn
2015-02-13  9:38   ` Anthony J. Bentley
2015-02-13  9:50     ` Raphael Cohn
2015-02-13  9:57       ` Raphael Cohn [this message]
2015-02-13 10:45     ` Justin Cormack
2015-02-13 11:07       ` u-wsnj
2015-02-13 11:09 ` Justin Cormack
2015-02-13 13:02   ` Justin Cormack
2015-02-14 23:23     ` Felix Fietkau
2015-02-15  2:44       ` Rich Felker
2015-02-15  4:07         ` Isaac Dunham
2015-02-15 12:09       ` Sebastian Gottschall
2015-02-14  0:06   ` Isaac Dunham
2015-02-14  2:21     ` Rich Felker
2015-02-14 10:23     ` Justin Cormack
2015-02-14 20:35       ` Isaac Dunham
2015-02-14  2:23 ` 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='CACCP0Grkh4QjhL-9R-VkXuhUrzCAJ7M=q+9zsyE2EFC4JVowbw@mail.gmail.com' \
    --to=raphael.cohn@stormmq.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).