2012/11/29 Myklebust, Trond <Trond.Myklebust@xxxxxxxxxx>: > On Thu, 2012-11-29 at 17:39 +0100, Stef Bon wrote: >> 2012/11/29 Myklebust, Trond <Trond.Myklebust@xxxxxxxxxx>: >> > On Thu, 2012-11-29 at 10:22 -0500, simo wrote: >> >> On Thu, 2012-11-29 at 15:49 +0100, Stef Bon wrote: >> >> > 2012/11/29 Myklebust, Trond <Trond.Myklebust@xxxxxxxxxx>: >> >> > >> -----Original Message----- >> >> > >> >> >> No, sure, you should not do anything because others do it. But on the >> other hand, if others do it, why don't you? Better copy a good idea >> than be stubborn for ever. > > The idea that "if we build a bridge, they will come to us" is what gave > rise to dnotify, then inotify (nobody came, so let's build a bigger > bridge) and fsnotify (make it a toll bridge). Nobody is using those > interfaces much on local filesystems, so why is adding it to NFS and > CIFS going to be such a game changer? Well that's a good question. I've been working on this issue for some time now, and do not find much interest in it. I do not understand! Although I find this a bit frustating, I still beleive it's a good feature. And yes, I believe that what you suggest with building a bridge (having a good idea) they will come to us. And I've [posted on qt dev platforms, and they mentioned me that they need much more fine grained methods, that just "something has changed". But ok, that has nothing to do with nfs ... > >> And yes there is no such thing as a killer app, but in my opinion it's >> the user experience. It's so much better when your system keeps track >> on shared network resources. > > What does it enable us to do that we can't already do? This is precisely > the question that I asked you in the previous email. Huh? Is it possible to monitor directories and other objects for changes already with network fs's?? By polling? The poor mans fs notify service? Stef -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
