From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Helge Hafting <helge.hafting@hist.no>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
William Stearns <wstearns@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: silent semantic changes in reiser4 (brief attempt to document the idea ofwhat reiser4 wants to do with metafiles and why
Date: Fri, 10 Sep 2004 13:42:34 -0400 [thread overview]
Message-ID: <200409101742.i8AHgY6i005015@localhost.localdomain> (raw)
In-Reply-To: Message from Helge Hafting <helge.hafting@hist.no> of "Fri, 10 Sep 2004 11:42:10 +0200." <414176F2.3030301@hist.no>
Helge Hafting <helge.hafting@hist.no> said:
> Theodore Ts'o wrote:
> >On Wed, Sep 08, 2004 at 12:09:52AM +0200, Robin Rosenberg wrote:
> >>Maybe file/./attribute then. /. on a file is currently
> >>meaningless. That does not avoid the unpleasant fact that has been
> >>brought up by others (only to be ignored), that the directory syntax
> >>does not allow metadata on directories.
> >*Not* that I am endorsing the idea of being able to access metadata
> >via a standard pathname --- I continue to believe that named streams
> >are a bad idea that will be an attractive nuisance to application
> >developers, and if we must do them, then Solaris's openat(2) API is
> >the best way to proceed --- HOWEVER, if people are insistent on being
> >able to do this via standard pathnames, and not introducing a new
> >system call, I would suggest /|/ as the separator as the third least
> >worst option. Why?
> What's wrong with using / as the separator? It is already
> used to separate components of pathnames. Named streams
> are very much like files in a subdirectory.
/ is separator for directories, POSIX mandates its exact use. No, POSIX
isn't broken here, and even if it was, you have to remain compatible.
> This scheme makes for very little change to existing tools,
... while breaking fundamental assumptions by all programs in a major way,
and no sane solution for legacy applications in sight, with unknown
(probably huge) correctness and security implications...
> users may then do a "gimp somefile/icon.jpg" for example.
> Or "ls somefile/*" to see all the named streams/forks.
Please don't rehash this one. It is fundamentally broken.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2004-09-10 17:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 20:21 silent semantic changes in reiser4 (brief attempt to document the idea of what " Hans Reiser
2004-08-31 13:12 ` Pavel Machek
2004-08-31 13:36 ` Christian Mayrhuber
2004-09-07 20:16 ` Hans Reiser
2004-09-07 20:59 ` Pavel Machek
2004-09-08 9:14 ` Romano Giannetti
2004-09-07 21:05 ` William Stearns
2004-09-07 22:09 ` Robin Rosenberg
2004-09-09 9:03 ` silent semantic changes in reiser4 (brief attempt to document the idea ofwhat " Theodore Ts'o
2004-09-09 17:23 ` William Lee Irwin III
2004-09-09 18:09 ` Gunnar Ritter
2004-09-09 19:15 ` Hans Reiser
2004-09-09 20:45 ` Paul Jakma
2004-09-10 0:57 ` Hans Reiser
2004-09-10 1:15 ` Paul Jakma
2004-09-10 5:04 ` Hans Reiser
2004-09-10 5:53 ` viro
2004-09-10 6:52 ` Hans Reiser
2004-09-10 7:05 ` viro
2004-09-10 7:30 ` Hans Reiser
2004-09-10 16:49 ` Lee Revell
2004-09-10 17:23 ` viro
2004-09-10 7:21 ` Hans Reiser
2004-09-10 7:33 ` viro
2004-09-10 7:46 ` Hans Reiser
2004-09-10 8:18 ` viro
2004-09-10 9:20 ` Alan Cox
2004-09-10 17:48 ` Hans Reiser
2004-09-10 17:07 ` Alan Cox
2004-09-10 13:08 ` Horst von Brand
2004-09-10 3:22 ` Horst von Brand
2004-09-12 20:43 ` Davide Inglima
2004-09-10 9:42 ` Helge Hafting
2004-09-10 17:42 ` Horst von Brand [this message]
[not found] ` <20040910201738.GB8698@eskimo.com>
2004-09-14 8:39 ` Helge Hafting
2004-08-31 14:09 ` silent semantic changes in reiser4 (brief attempt to document the idea of what " Mike Waychison
2004-08-31 17:55 ` V13
2004-08-31 18:17 ` Spam
2004-08-31 19:08 ` Tonnerre
2004-08-31 19:38 ` Spam
2004-09-01 3:11 ` Robin Rosenberg
2004-08-31 19:35 ` V13
[not found] ` <874qmjm51g.fsf@uhoreg.ca>
2004-08-31 20:31 ` Spam
[not found] ` <87vfezkm06.fsf@uhoreg.ca>
2004-08-31 22:15 ` Spam
2004-08-31 19:49 ` Chris Dawes
2004-09-01 6:03 ` Hans Reiser
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=200409101742.i8AHgY6i005015@localhost.localdomain \
--to=vonbrand@inf.utfsm.cl \
--cc=helge.hafting@hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
--cc=tytso@mit.edu \
--cc=wstearns@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®