From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] files vs. directories
Date: Thu, 3 Feb 2011 14:15:29 +0000 [thread overview]
Message-ID: <AANLkTimje_peQjPjpCU0bVcAL6SAH1k1P0NSUmGMZAU4@mail.gmail.com> (raw)
In-Reply-To: <201102031444.40895.dexen.devries@gmail.com>
On 3 February 2011 13:44, dexen deVries <dexen.devries@gmail.com> wrote:
> On Thursday, February 03, 2011 02:36:40 pm roger peppe wrote:
>> On 3 February 2011 11:45, dexen deVries <dexen.devries@gmail.com> wrote:
>> > read(open("/foo")) returns byte stream under entry `foo' in the root
>> > object.
>> >
>> > readdir("/foo") returns `bar' (and possibly others) -- entries in
>> > hierarchical section of object `/foo'.
>>
>> there's no distinction between readdir and read in plan 9.
>
> Forgot about that. Still, you can't chdir() into an inode that doesn't
> indicate being a directory. And the bytestream returned by
> read(SOME_DIRECTORY) is fixed-format and doesn't provide any space for free-
> form bytestream.
i don't think that helps you.
under plan 9, reading a directory is this:
translate(read(open(dir)))
i don't see how you can make read(open(dir)) return
something different.
oh yes, maintaining the usual semantics for cp becomes tricky.
mkdir z
cp x.c z
do i mean to write x.c to z itself, or to a new file within z?
next prev parent reply other threads:[~2011-02-03 14:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 11:45 dexen deVries
2011-02-03 13:05 ` erik quanstrom
2011-02-03 13:40 ` dexen deVries
2011-02-03 13:59 ` erik quanstrom
2011-02-03 13:36 ` roger peppe
2011-02-03 13:40 ` erik quanstrom
2011-02-03 13:44 ` dexen deVries
2011-02-03 14:15 ` roger peppe [this message]
2011-02-03 14:27 ` dexen deVries
2011-02-03 18:42 ` smiley
2011-02-03 22:33 ` dexen deVries
2011-02-04 1:42 ` Robert Ransom
2011-02-04 1:49 ` erik quanstrom
2011-02-04 3:30 ` Robert Ransom
2011-02-04 4:11 ` Eric Van Hensbergen
2011-02-04 4:17 ` andrey mirtchovski
2011-02-04 5:36 ` erik quanstrom
2011-02-03 14:35 ` dexen deVries
2011-02-03 16:58 ` Bakul Shah
2011-02-03 23:13 ` Eric Van Hensbergen
2011-02-04 0:24 ` smiley
2011-02-04 0:45 ` Skip Tavakkolian
2011-02-04 1:29 ` Nick LaForge
2011-02-04 18:26 Lucio De Re
2011-02-04 18:28 Lucio De Re
2011-02-04 18:31 Lucio De Re
2011-02-04 18:41 ` Lucio De Re
2011-08-21 17:33 ` Enrico Weigelt
2011-02-04 18:38 Lucio De Re
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=AANLkTimje_peQjPjpCU0bVcAL6SAH1k1P0NSUmGMZAU4@mail.gmail.com \
--to=rogpeppe@gmail.com \
--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).