From: "Alexander G. M. Smith" <agmsmith@rogers.com>
To: "Burnes, James" <james.burnes@gwl.com>
Cc: reiserfs-list@namesys.com
Subject: RE: ".meta." as a Name Prefix
Date: Thu, 22 Apr 2004 20:18:36 -0400 EDT [thread overview]
Message-ID: <2452111248-BeMail@cr593174-a> (raw)
In-Reply-To: <3DF9165145FACB4C96977FF650C1E9040C469E75@its-mail1.its.corp.gwl.com>
Burnes, James wrote on Wed, 21 Apr 2004 17:10:00 -0600:
> In the same way that 'ls <directory>' is ambigous. Does it mean I want
> to look at the attributes of the directory itself, or does it mean that
> I'm referring to the contents of the directory? That's why they
> invented 'ls -d'
Good analog. There would have to be some OS and application level
changes to support having both read/writeable data and child objects.
For backwards compatiblity, calling ReadDir() would likely hint that
you want a list of child objects, and read() means you want the data.
The feature I want is that you can do both to any file system object.
Plus of course indexing of attributes and other BeOS style goodies.
- Alex
next parent reply other threads:[~2004-04-23 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DF9165145FACB4C96977FF650C1E9040C469E75@its-mail1.its.corp.gwl.com>
2004-04-23 0:18 ` Alexander G. M. Smith [this message]
2004-04-17 2:55 "Metas" The Amazing Dragon
2004-04-18 23:16 ` ".meta." as a Name Prefix Alexander G. M. Smith
2004-04-21 1:00 ` David Masover
2004-04-21 2:56 ` John D. Heintz
2004-04-25 5:44 ` David Masover
2004-04-25 14:02 ` Alexander G. M. Smith
2004-04-25 15:07 ` John D. Heintz
2004-04-25 19:33 ` David Masover
2004-04-21 12:03 ` Alexander G. M. Smith
2004-04-25 5:27 ` David Masover
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=2452111248-BeMail@cr593174-a \
--to=agmsmith@rogers.com \
--cc=james.burnes@gwl.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.