On Thu, 2012-11-29 at 21:09 +0000, Myklebust, Trond wrote: > On Thu, 2012-11-29 at 15:05 -0500, simo wrote: > > On Thu, 2012-11-29 at 17:11 +0000, Myklebust, Trond wrote: > > > 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? > > > > Sorry Trond, > > but this is simply not true. > > > > inotify is a key feature at least in some packages I know, and makes > > some things *a lot* easier. > > > > Of course this are less visible features, that are easy to overlook, but > > they are not unused for sure. > > So why is it so difficult for anyone in this thread to name these killer > applications that would benefit from NFS+CIFS support? I keep asking, > and all I get is wishy-washy and hand-wavy answers. > > Without use cases, there is nothing to discuss on the implementation > front. Sorry for the misunderstanding, I wasn't talking about inotify *on CIFS/NFS*, I do not care about that use case, I'll gladly let Stef pitch it for himself :) Simo. -- Simo Sorce Samba Team GPL Compliance Officer <simo@xxxxxxxxx> Principal Software Engineer at Red Hat, Inc. <simo@xxxxxxxxxx> -- 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
