From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CAB08-qoDwuhCB2-uqPEGgHVziEdzpedhugMsvXH0mGhVM8ESbQ@mail.gmail.com>
References: <CAB08-qoDwuhCB2-uqPEGgHVziEdzpedhugMsvXH0mGhVM8ESbQ@mail.gmail.com>
From: =?UTF-8?Q?Iruat=C3=A3_Souza?= <iru.muzgo@gmail.com>
Date: Tue, 12 May 2015 09:24:09 -0300
Message-ID: <CABJnqBShfOCtcuHbeSNPBWSODGnGWp1qZSb51njjPEaATy5LEA@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] on cp /fd/1 /fd/0
Topicbox-Message-UUID: 526dcd54-ead9-11e9-9d60-3106f5b1d025

--r-------- d 0 glenda glenda 0 May 10 18:57 0
--rw------- d 0 glenda glenda 0 May 10 18:57 1
---w------- d 0 glenda glenda 0 May 10 18:57 2

is that what you want to know? or the reasons why the permissions are like that?

On Tue, May 12, 2015 at 8:56 AM, Daniel Bastos <dbastos@toledo.com> wrote:
> Good morning.
>
> % cp /fd/1 /fd/0
> cp: can't open /fd/1: '/fd/1' inappropriate use of fd
>
> I can't open it for reading, but I could open it for writing. Why can't I
> open it for reading?