From: "Pádraig Brady" <P@draigBrady.com>
To: linux-kernel@vger.kernel.org
Cc: Eric Blake <eblake@redhat.com>
Subject: Re: RFC: allow empty symlink targets
Date: Thu, 17 Jan 2013 16:22:04 +0000 [thread overview]
Message-ID: <50F8252C.2060404@draigBrady.com> (raw)
In-Reply-To: <1358427833-3847-1-git-send-email-P@draigBrady.com>
On 01/17/2013 01:03 PM, Pádraig Brady wrote:
> The discussion leading to this is at http://bugs.gnu.org/13447
> In summary other systems allow an empty target for a symlink,
> and POSIX specifies that it should be allowed?
In relation to this, Eric Blake said:
> 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.
>
> It will probably be a bug report similar to this one, which regarded how
> to handle a symlink containing just slashes:
> http://austingroupbugs.net/view.php?id=541
thanks,
Pádraig.
next prev parent reply other threads:[~2013-01-17 16:32 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 ` Pádraig Brady [this message]
2013-05-15 12:38 ` RFC: allow empty symlink targets 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
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=50F8252C.2060404@draigBrady.com \
--to=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