From: Al Viro <viro@ZenIV.linux.org.uk>
To: P??draig Brady <P@draigBrady.com>
Cc: linux-kernel@vger.kernel.org, Eric Blake <eblake@redhat.com>
Subject: Re: RFC: allow empty symlink targets
Date: Wed, 15 May 2013 23:03:35 +0100 [thread overview]
Message-ID: <20130515220335.GV25399@ZenIV.linux.org.uk> (raw)
In-Reply-To: <519381D8.5080206@draigBrady.com>
On Wed, May 15, 2013 at 01:38:48PM +0100, P??draig Brady wrote:
> >> In today's Austin Group meeting, I was tasked to open a new bug that
> >> would state specifically how the empty symlink is resolved; the intent
> >> is to allow both Solaris behavior (current directory) and BSD behavior
> >> (ENOENT). Meanwhile, everyone was in agreement that the Linux kernel
> >> has a bug for rejecting the creation of an empty symlink, but once that
> >> bug is fixed, then Linux can choose either Solaris or BSD behavior for
> >> how to resolve such a symlink.
Austin Group Is At It Again, Demands at 11...
Would you mind explaining who's "everyone" and why would we possibly
want to honour that agreement of yours? Functionality in question is
utterly pointless, seeing that semantics of such symlinks is OS-dependent
anyway *and* that blanket refusal to traverse such beasts is a legitimate
option. What's the point in allowing to create them in the first place?
next prev parent reply other threads:[~2013-05-15 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 13:03 RFC: allow empty symlink targets Pádraig Brady
2013-01-17 13:03 ` [PATCH] symlink: allow an empty target string Pádraig Brady
2013-01-17 16:22 ` RFC: allow empty symlink targets Pádraig Brady
2013-05-15 12:38 ` Pádraig Brady
2013-05-15 14:40 ` Eric Blake
2013-05-15 20:48 ` Pádraig Brady
2013-05-24 10:01 ` Pavel Machek
2013-05-15 22:03 ` Al Viro [this message]
2013-05-16 9:37 ` Pádraig Brady
2013-05-16 12:22 ` Eric Blake
2013-05-26 9:39 ` Pavel Machek
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=20130515220335.GV25399@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=P@draigBrady.com \
--cc=eblake@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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