From: Chad Brown <yandros@MIT.EDU>
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 10:05:12 -0700 [thread overview]
Message-ID: <4A07098C-633B-451A-8EB0-A5F24A948243@mit.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Jun 17, 2009, at 1:54 AM, 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.
They sort-of-kind-of got there in Mac OS X with `application bundles'
that are just specially named directories with some canonical
contents. It'll take another major systems change for them to wean
themselves off of resource forks entirely, I expect.
*chad
[-- Attachment #2: Type: text/html, Size: 1319 bytes --]
next reply other threads:[~2009-06-17 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 17:05 Chad Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-11 3:44 [9fans] Different representations of the same file/resource in a synthetic FS 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
2009-06-13 3:43 ` lucio
2009-06-16 23:15 ` Roman V Shaposhnik
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=4A07098C-633B-451A-8EB0-A5F24A948243@mit.edu \
--to=yandros@mit.edu \
--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).