From: "Peter A. Cejchan" <pac@next.gli.cas.cz>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What is this?
Date: Wed, 24 Apr 2002 08:12:11 +0200 [thread overview]
Message-ID: <20020424081211.A211@next.gli.cas.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 37 bytes --]
this is ++pac intruding, again:-)
[-- Attachment #2: TORUSS --]
[-- Type: text/plain, Size: 1164 bytes --]
#########################
term% file ./pstotext
.../pstotext: 386 plan 9 executable
term% grep denied *.[ch]
term% grep 'Permission denied' *
[the following is piggy, but worked :-) ... ]
pstotext: [snip] ... blah blah blah ...Directory not emptyNottyNxioPermission deniedBroken pipeRead-only file system ... blah blah blah ...[snip]
[...thus pointing me at sys libs]
term% rgrep 'Permission denied' '*.c' /sys/src/ape
/sys/src/ape/cmd/pdksh/missing.c: return "Permission denied";
/sys/src/ape/lib/ap/stdio/strerror.c: "Permission denied",
term% rgrep 'Permission denied' '*.h' /sys/src/ape
term%
[rgrep is "recursive grep" script]
term% rgrep 'EPERM' '*.h' /sys/include
/sys/include/ape/errno.h:#define EPERM 30
term%
[thus, it is probably #define EPERM 30 from /sys/include/ape/errno.h ... however, errno.h is included so many times from allmost everywhere, that I am (hopefully temporarily) lost :-((( ... I'm digging. ]
#########################
C gurus: Any hints, please? A more comprehensive description of errno 30 than "Permission denied" is welcome...
#########################
TIA,
cheers,
++pac.
next reply other threads:[~2002-04-24 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 6:12 Peter A. Cejchan [this message]
2002-04-24 9:45 ` peter a. cejchan
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 14:19 [9fans] what " cej
2004-10-20 14:22 ` Russ Cox
2002-10-11 8:23 Petr Cejchan
2002-10-11 7:32 Fco.J.Ballesteros
2002-10-04 15:36 Russ Cox
2002-10-04 14:17 Peter A. Cejchan
2002-04-23 15:26 [9fans] What " Russ Cox
2002-04-23 13:49 Peter A. Cejchan
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=20020424081211.A211@next.gli.cas.cz \
--to=pac@next.gli.cas.cz \
--cc=9fans@cse.psu.edu \
/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).