All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Implement AT_SYMLINK_FOLLOW flag for linkat
Date: Sun, 18 Jun 2006 23:06:50 +0100	[thread overview]
Message-ID: <20060618220650.GG27946@ftp.linux.org.uk> (raw)
In-Reply-To: <4495AC3B.4020508@redhat.com>

On Sun, Jun 18, 2006 at 12:40:43PM -0700, Ulrich Drepper wrote:
> Linus Torvalds wrote:
> > Well, the patch as sent in does seem sane, as long as glibc doesn't start 
> > defaulting to the insane behaviour. Giving users the _ability_ to link to 
> > the symlink target is certainly not wrong, regardless of any standard. 
> > Doing it by default is another matter.
> 
> I do not intend to change the link implementation in glibc.  That would
> be majorly stupid, it'd break the ABI.
> 
> The AT_SYMLINK_FOLLOW flag to linkat was the result of the discussion
> how to resolve the issue of the conflict between POSIX and the Linux
> implementation of link (BTW: the Solaris link syscall behaves the same
> as Linux's).

... while FreeBSD still doesn't have that 4.2BSD bug fixed, the suckers.

>   This is an easy an non-intrusive way to help people who
> depend on the questionable POSIx-mandated behavior to work around the
> incompatiblity.  Nothing more.  Don't change the link syscall, don't
> assume the glibc will be changed.  This is only one little extra bit of
> new functionality.

*shrug*

Fine by me; it's not really useful, but it's not a serious bloat either.

ACKed-by: Al Viro <viro@zeniv.linux.org.uk>

      reply	other threads:[~2006-06-18 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17 19:13 [PATCH] Implement AT_SYMLINK_FOLLOW flag for linkat Ulrich Drepper
2006-06-18 19:16 ` Al Viro
2006-06-18 19:22   ` Linus Torvalds
2006-06-18 19:32     ` Al Viro
2006-06-18 19:40     ` Ulrich Drepper
2006-06-18 22:06       ` Al Viro [this message]

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=20060618220650.GG27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 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.