From: Roman V Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Different representations of the same
Date: Wed, 17 Jun 2009 17:20:35 -0700 [thread overview]
Message-ID: <1245284435.9513.24.camel@work> (raw)
In-Reply-To: <409a9964c8f20c0934ba6477744a2a89@terzarima.net>
On Wed, 2009-06-17 at 09:54 +0100, Charles Forsyth wrote:
> >The only drawback so far seems to be the fact that if one
> >needs flexibility, then every file becomes a subdirectory.
> >Not that it is scary or anything, but it smells too much
> >of resource forks (or may be I'm just too easily scared).
>
> it's the other way round: they ought to have represented
> collections of related data and metadata using directories
> instead of inventing rubbish like resource forks.
Having thought of this some more, I believe you're absolutely
right. Now, the *only* thing that you don't get if you go
that route is a read/write on a "default" file representation.
Thanks,
Roman.
next prev parent reply other threads:[~2009-06-18 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 17:14 [9fans] Different representations of the same file/resource in a synthetic FS Roman V Shaposhnik
2009-06-09 17:27 ` andrey mirtchovski
2009-06-09 18:10 ` erik quanstrom
2009-06-09 19:01 ` andrey mirtchovski
2009-06-11 3:44 ` Roman V. Shaposhnik
2009-06-11 4:49 ` [9fans] Different representations of the same lucio
2009-06-13 1:02 ` Roman V Shaposhnik
2009-06-13 1:56 ` erik quanstrom
2009-06-16 23:12 ` Roman V Shaposhnik
2009-06-17 8:54 ` Charles Forsyth
2009-06-18 0:20 ` Roman V Shaposhnik [this message]
2009-06-13 3:43 ` lucio
2009-06-16 23:15 ` Roman V Shaposhnik
2009-06-09 17:30 ` [9fans] Different representations of the same file/resource in a synthetic FS J.R. Mauro
2009-06-17 17:05 [9fans] Different representations of the same Chad Brown
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=1245284435.9513.24.camel@work \
--to=rvs@sun.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).