9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "有澤 健治" <karisawa@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] ape/_errno: ENOENT
Date: Mon, 10 Jan 2022 10:55:22 +0900	[thread overview]
Message-ID: <82279cf9-ae80-810b-5335-6008e1a5f784@gmail.com> (raw)
In-Reply-To: <87lezsahx1.fsf@turtle-trading.net>

Hello,

hebe% gr 'No such file' /sys/src/
/sys/src/ape/lib/ap/stdio/strerror.c:33:     "No such file or directory",
/sys/src/cmd/hg/mercurial/context.py:184:             if match.bad(fn, 
'No such file in rev ' + str(self)) and match(fn):
/sys/src/cmd/python/Doc/lib/libcommands.tex:51: (256, 'cat: /bin/junk: 
No such file or directory')
/sys/src/cmd/python/Doc/lib/liberrno.tex:28: \begin{datadesc}{ENOENT} No 
such file or directory \end{datadesc}
/sys/src/cmd/python/Modules/errnomodule.c:53: e.g. os.strerror(2) could 
return 'No such file or directory'.");
/sys/src/cmd/python/Modules/errnomodule.c:414:     inscode(d, ds, de, 
"ENOENT", ENOENT, "No such file or directory");
/sys/src/cmd/python/README:336:         No such file or directory
/sys/src/cmd/spin/pc_zpp.c:320:     {    fprintf(stdout, "spin: error, 
'%s': No such file\n", fnm);
hebe%

On 2022/01/07 2:32, Benjamin Riefenstahl wrote:
> Hi ori,
>
>> Quoth Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>:
>>> Maybe the message is somewhere in APE, although I
>>> could not find it in /sys/src/ape either.
> ori writes:
>> ./lib/ap/stdio/strerror.c:33: 	"No such file or directory",
> But the actual error message is just "No such file", so some code would
> have to cut the rest explicitly to get from that bit in strerror.c to
> that result.
>
> It seems that the text does actually come from the syscall, see attached
> new test.  I can't find the implementation in the kernel right now,
> maybe somebody has a pointer.
>
> Thanks for any insight,
> benny
>


      parent reply	other threads:[~2022-01-10  3:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 19:50 Benjamin Riefenstahl
2022-01-05 19:13 ` cinap_lenrek
2022-01-06 13:35   ` Benjamin Riefenstahl
2022-01-06 16:27     ` ori
2022-01-06 17:32       ` Benjamin Riefenstahl
2022-01-06 20:24         ` Xiao-Yong Jin
2022-01-07 10:09           ` Benjamin Riefenstahl
2022-01-10  1:55         ` 有澤 健治 [this message]

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=82279cf9-ae80-810b-5335-6008e1a5f784@gmail.com \
    --to=karisawa@gmail.com \
    --cc=9front@9front.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).