From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] on cp /fd/1 /fd/0
Date: Tue, 12 May 2015 06:20:00 -0700 [thread overview]
Message-ID: <df96ccde6bcee748edeb564fa1e13777@brasstown.quanstro.net> (raw)
In-Reply-To: <89c84da6265efed56fb5835276d4a2e0@proxima.alt.za>
> Except that OP wants to know why reading /fd/1 isn't allowed when the
> permissions allow it. I suspect something is a bit obscure, like the
> implementation being different from the stated permissions.
i imagine that the permissions on the underlying device are wrong.
"cons" is 600 in rio, and i suspect that's it. 'd' is the dup driver.
- erik
next prev parent reply other threads:[~2015-05-12 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 11:56 Daniel Bastos
2015-05-12 12:24 ` Iruatã Souza
2015-05-12 12:39 ` lucio
2015-05-12 13:20 ` erik quanstrom [this message]
2015-05-12 14:17 ` Daniel Bastos
2015-05-12 16:15 ` Charles Forsyth
2015-05-12 17:10 ` Daniel Bastos
2015-05-12 18:54 ` Charles Forsyth
2015-05-12 15:52 ` Charles Forsyth
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=df96ccde6bcee748edeb564fa1e13777@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).