From: Davide Libenzi <davidel@xmailserver.org>
To: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Al Viro <viro@ftp.linux.org.uk>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [patch] F_GETPATH implementation (rev 2)
Date: Tue, 15 Apr 2008 10:43:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804151038250.8218@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <cfd18e0f0804142334w23a0f492we6b0a47ebee055f7@mail.gmail.com>
On Tue, 15 Apr 2008, Michael Kerrisk wrote:
> On Tue, Apr 15, 2008 at 4:41 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> >
> > On Mon, 14 Apr 2008, Davide Libenzi wrote:
> > >
> > > This is a small patch to support BSD's F_GETPATH on Linux.
> > > IMO the simplicity of the patch and the portability advantages makes it
> > > worth it. I'll leave to others to further comments it.
> >
> > So, I'd like to know who (if anybody) really uses F_GETPATH.
>
> Davide described this as "BSD's F_GETPATH". It's worth clarifying
> that more accurately this is "MacOS's F_GETPATH". I can't find any
> trace of F_GETPATH on Net/Open/FreeBSD, Solaris doesn't seem to have
> it either, and none of the other systems I checked has it either.
Oh, I thought it was a common BSD-isdh thing. I did find it inside some
OSX code indeed.
Given this, and given that the interface is not that great too (buffer
size bolt in), I think we can safely drop it.
- Davide
prev parent reply other threads:[~2008-04-15 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 0:35 Davide Libenzi
2008-04-15 2:41 ` Linus Torvalds
2008-04-15 6:34 ` Michael Kerrisk
2008-04-15 17:43 ` Davide Libenzi [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=Pine.LNX.4.64.0804151038250.8218@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=mtk.manpages@googlemail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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®