From: mjt@nysv.org (Markus Törnqvist)
To: David Dabbs <david@dabbs.net>,
'Christian Mayrhuber' <christian.mayrhuber@gmx.net>,
linux-fsdevel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [RFC] Pathname Semantics with //
Date: Fri, 10 Sep 2004 12:11:03 +0300 [thread overview]
Message-ID: <20040910091103.GA26192@nysv.org> (raw)
In-Reply-To: <20040909204102.GB27331@schnapps.adilger.int>
On Thu, Sep 09, 2004 at 02:41:02PM -0600, Andreas Dilger wrote:
>One problem that using "//" may have (thought it is personally my favourite
>option right now) is that "realpath(3)" may cause the "//" to be eaten, and
Exactly.
However, I must say that adding // somewhere is IMO _much_ uglier than
doing ./file/..metas/ for real.
I'd also imagine that it's easier to teach progs ..metas/ than ^//(.*)
but I may be proven wrong and my opinion cated to /dev/null ;)
>this is used by many programs to "resolve" pathnames to remvoe symlinks,
>bogus "/./" etc. This may need a small fix in glibc, but at least it is
>still central instead of teaching a million apps about different sematics.
Different semantics?
Like you wouldn't teach old programs the // syntax? Or what am I missing :)
You don't have to teach them "streams as files-as-dirs" if you have a mirror
namespace with //?
Well, I'd rather stick to teaching progs about ..metas/ :P
--
mjt
next prev parent reply other threads:[~2004-09-10 9:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 10:41 [RFC] Pathname Semantics with // David Dabbs
2004-09-09 10:41 ` David Dabbs
2004-09-08 16:13 ` Hans Reiser
2004-09-09 16:36 ` Peter Foldiak
2004-09-09 19:21 ` David Dabbs
2004-09-09 19:21 ` David Dabbs
2004-09-10 0:49 ` Hans Reiser
2004-09-10 3:06 ` David Dabbs
2004-09-10 3:06 ` David Dabbs
2004-09-10 5:40 ` Hans Reiser
2004-09-09 21:51 ` David Dabbs
2004-09-09 21:51 ` David Dabbs
2004-09-09 6:10 ` Hans Reiser
2004-09-09 17:33 ` Christian Mayrhuber
2004-09-09 20:17 ` David Dabbs
2004-09-09 20:17 ` David Dabbs
2004-09-09 20:41 ` Andreas Dilger
2004-09-10 9:11 ` Markus Törnqvist [this message]
2004-09-10 10:37 ` Christian Mayrhuber
2004-09-09 23:03 ` Jamie Lokier
2004-09-10 1:37 ` David Dabbs
2004-09-10 1:37 ` David Dabbs
2004-09-10 9:53 ` [SPAM] " Jamie Lokier
2004-09-10 17:11 ` David Dabbs
2004-09-10 17:11 ` David Dabbs
2004-09-10 11:47 ` Christian Mayrhuber
2004-09-10 11:06 ` Christian Mayrhuber
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 17:49 David Dabbs
2004-09-10 17:49 ` David Dabbs
2004-09-09 18: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=20040910091103.GA26192@nysv.org \
--to=mjt@nysv.org \
--cc=christian.mayrhuber@gmx.net \
--cc=david@dabbs.net \
--cc=linux-fsdevel@vger.kernel.org \
--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.