From: "John D. Heintz" <jheintz@pobox.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Do xml-like namespaces make sense for Reiser4? (re: metas thread)
Date: Thu, 15 Apr 2004 10:15:27 -0500 [thread overview]
Message-ID: <407EA70F.6010301@pobox.com> (raw)
In-Reply-To: <407DD71D.30902@slaphack.com>
David Masover wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John D. Heintz wrote:
> | David,
> |
> | I think you might be onto something, but doing this manually for each
> | file isn't viable (in my opinion).
>
> It applies recursively. Let's assume for a moment that /..foo is a
> directory containing pseudo-files, metadata, or whatever the current
> term is, for the file '/'. By creating the file /..foo/something as a
> symlink to /..foo/<some long path>/something, you automatically create
> /bar/..foo/something, which is a link to /bar/..foo/<same long
> path>/something.
>
> | What I think might work is applying symlinks to all files hierarchically
> | so that all "*/nsa/*" names resolve to "*/nsa.gov/security/*".
>
> Just what I described above, only it is local to the tree I apply it to,
> and files deeper in the hierarchy take precedence. So, for example, if
> I create a link manually for /bar/..foo/something that points somewhere
> else, then /bar and all subdirs (and subfiles) of /bar contain that same
> link, instead of the one created for /.
>
Thanks for the explanation and I like the idea. Being able to define a
symlink and have it recursively apply might be exactly what is needed here.
Is this behavior currently part of Reiser4? I don't remember seeing it
anywhere, but I do remember reading something about inheritence being
needed for various features. Is this the same as inheritence?
Thanks,
John Heintz
next prev parent reply other threads:[~2004-04-15 15:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 15:45 Do xml-like namespaces make sense for Reiser4? (re: metas thread) John D. Heintz
2004-04-12 16:00 ` Hubert Chan
2004-04-12 19:21 ` John D. Heintz
2004-04-12 21:28 ` Hubert Chan
2004-04-12 18:15 ` Hans Reiser
2004-04-12 18:59 ` Hubert Chan
2004-04-12 19:12 ` John D. Heintz
2004-04-13 14:40 ` John D. Heintz
2004-04-13 16:31 ` Hans Reiser
2004-04-13 16:57 ` John D. Heintz
2004-04-13 17:06 ` Grant Miner
2004-04-13 18:09 ` John D. Heintz
2004-04-13 18:36 ` Grant Miner
2004-04-13 17:47 ` Hans Reiser
2004-04-13 18:23 ` John D. Heintz
2004-04-13 18:28 ` Hans Reiser
2004-04-13 18:47 ` John D. Heintz
2004-04-13 20:31 ` Valdis.Kletnieks
2004-04-14 2:18 ` Enrique Perez-Terron
2004-04-14 15:06 ` John D. Heintz
2004-04-14 23:39 ` Enrique Perez-Terron
2004-04-14 2:50 ` David Masover
2004-04-14 15:12 ` John D. Heintz
2004-04-15 0:28 ` David Masover
2004-04-15 15:15 ` John D. Heintz [this message]
2004-04-16 1:04 ` 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=407EA70F.6010301@pobox.com \
--to=jheintz@pobox.com \
--cc=ninja@slaphack.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.