Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 22 Sep 2020 16:33:43 -0400
From: Jeffrey Walton <>
Subject: Re: Re: OS detection wrong on Alpine Linux 3.10

On Tue, Sep 22, 2020 at 4:18 PM Bruno Haible <> wrote:
> ...
> > It's true that implementations have a number of things that are
> > implementation defined, and that the standards specify this as having
> > a documented behavior (which the party reading the documentation can
> > then rely upon). At present musl does not have sufficient
> > documentation in this regard; I began the work of enumerating all the
> > impl-defined behaviors at one point with a goal of documenting them
> > but it was never completed.
> It is good to attempt to document such things. But I doubt anyone can
> ever produce a complete documentation of this kind:
>   * For many system calls, when POSIX specifies an errno X for condition A,
>     and an errno Y for condition B, then if both A and B apply, often
>     the implementation is free to return errno X or Y. There are many
>     system calls and many possible combinations of conditions...

Not to mention SELinux hijacking error codes and errno so you go
chasing the wrong cause of an error...


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.