From: Al Viro <viro@ZenIV.linux.org.uk>
To: NeilBrown <neilb@suse.de>
Cc: David Heidelberger <david.heidelberger@ixit.cz>,
linux-nfs@vger.kernel.org
Subject: Re: DNOTIFY to INOTIFY migration
Date: Mon, 10 Mar 2014 00:20:15 +0000 [thread overview]
Message-ID: <20140310002015.GH18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20140310102102.3c886726@notabene.brown>
On Mon, Mar 10, 2014 at 10:21:02AM +1100, NeilBrown wrote:
> On Fri, 07 Mar 2014 21:30:34 +0100 David Heidelberger
> <david.heidelberger@ixit.cz> wrote:
>
> > Hello,
> >
> > in linux kernel is DNOTIFY actually marked as deprecated, with superior
> > replacement INOTIFY.
>
> Where is it marked as deprecated? I would be very surprised if dnotify
> wasn't supported indefinitely.
Unfortunately, it will be - once it's in, it's in.
> (I have no opinion on whether rpc.idmapd should be changed to use inotify,
> except based on the "if it ain't broke, don't fix it" principle).
I still don't understand WTF does rpc.imapd *want* either of those, TBH.
Said that, the original posting does read a bit like "herpes is so last century,
shouldn't we upgrade to clap by now?"...*0O(and I don't want to think what
that makes fanotify, thank you very much)
next prev parent reply other threads:[~2014-03-10 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 20:30 DNOTIFY to INOTIFY migration David Heidelberger
2014-03-09 23:21 ` NeilBrown
2014-03-10 0:20 ` Al Viro [this message]
2014-03-10 0:56 ` NeilBrown
2014-03-10 1:45 ` Al Viro
2014-03-12 22:52 ` David Heidelberger
2014-03-12 23:11 ` NeilBrown
2014-03-10 0:55 ` David Heidelberger
2014-03-10 0:15 ` NeilBrown
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=20140310002015.GH18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=david.heidelberger@ixit.cz \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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