linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Wesley Aptekar-Cassels
	<w.aptekar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] errno.3: Add values for all errors
Date: Thu, 23 Nov 2017 10:23:02 +0100	[thread overview]
Message-ID: <5A169376.90002@bfs.de> (raw)
In-Reply-To: <f033a61a-f305-689d-b69a-72267ef767c1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>



Am 23.11.2017 10:07, schrieb Michael Kerrisk (man-pages):
> On 11/23/2017 09:31 AM, Christoph Hellwig wrote:
>> On Wed, Nov 22, 2017 at 07:15:45PM -0500, Wesley Aptekar-Cassels wrote:
>>> This patch documents the values of error numbers on linux. This is
>>> something that is in the OpenBSD errno man page, which I find quite
>>> useful.
>>
>> Error numbers are different for different architectures.
> 
> I was just about to say the same.
> 
> Someone else recently proposed the same change, and I should have
> thought then to add the text that I have added just now to errno(3).
> Hopefully this goes someway to addressing your requirements, Wesley.
> 
> New text:
> 
>        On  Linux, the error numbers that correspond to each symbolic name
>        vary somewhat across architectures.  Therefore, numeric values are
>        not  included in the list of error names below.  On any particular
>        system, one can obtain a list of all symbolic error names and  the
>        corresponding error numbers using the errno(1) command:
> 
If i read this that would mean the values differ between the linux architectures only.
I do not ting that was intended. What about that:


Portability:
 Programmers should use always the symbolic names as that the value of errno may vary
 across different systems. Always use strerror (3) (or compareable) to translate
 the errno code into a human readable string.

note: errno (1) is a nice programm and it could be mentioned but a propper programm
      simply should not say things like "Error: 13".

re,
 wh


>            $ errno -l
>            EPERM 1 Operation not permitted
>            ENOENT 2 No such file or directory
>            ESRCH 3 No such process
>            EINTR 4 Interrupted system call
>            EIO 5 Input/output error
>            ...
> 
>        The  errno(1) command can also be used to look up individual error
>        numbers and names as in the following examples:
> 
>            $ errno 2
>            ENOENT 2 No such file or directory
>            $ errno ESRCH
>            ESRCH 3 No such process
> 
> Cheers,
> 
> Michael
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-11-23  9:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23  0:15 [PATCH] errno.3: Add values for all errors Wesley Aptekar-Cassels
     [not found] ` <20171123001545.dp55g3pkdm5bzah3-8dEs2KUsCdXP0Z7Jsv878P8+0UxHXcjY@public.gmane.org>
2017-11-23  8:31   ` Christoph Hellwig
     [not found]     ` <20171123083109.GA25458-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-11-23  9:07       ` Michael Kerrisk (man-pages)
     [not found]         ` <f033a61a-f305-689d-b69a-72267ef767c1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-23  9:12           ` Christoph Hellwig
     [not found]             ` <20171123091247.GA7460-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-11-23  9:46               ` Eugene Syromyatnikov
     [not found]                 ` <CACGkJduG6oTqnGa4=COV2o+S2AtpGTVTPcV1Uz6J=M9+fZR1Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-23  9:48                   ` Michael Kerrisk (man-pages)
     [not found]                     ` <CAKgNAkj-_+o7sDWgn7CwR=Tm5TFdxLuVM+89779vZOL-2atCwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-23  9:50                       ` Michael Kerrisk (man-pages)
2017-11-23  9:51               ` Michael Kerrisk (man-pages)
     [not found]                 ` <CAKgNAkhcB-uGhEF_+wC5ut8a7fErv+Wijti9DNF5P7F6HMLbaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-23 12:56                   ` Christoph Hellwig
     [not found]                     ` <20171123125615.GA20708-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-11-23 12:58                       ` Michael Kerrisk (man-pages)
2017-11-23  9:23           ` walter harms [this message]
     [not found]             ` <5A169376.90002-fPG8STNUNVg@public.gmane.org>
2017-11-23  9:47               ` Michael Kerrisk (man-pages)
     [not found]                 ` <CAKgNAkiRdXxXWznvwOneU9uQqPYHs-JM0thiFEjveSPpt8GdNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-23 10:57                   ` walter harms
     [not found]                     ` <5A16A9A0.30605-fPG8STNUNVg@public.gmane.org>
2017-11-23 20:34                       ` Michael Kerrisk (man-pages)
     [not found]                         ` <a4fce689-60e8-38d2-6310-d90103532a0c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-24 15:37                           ` walter harms

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=5A169376.90002@bfs.de \
    --to=wharms-fpg8stnunvg@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=w.aptekar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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.
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).