RFC on a published change to FreeBSD 11 kqueue file ops.

[Tomoaki AOKI]

One (two?) question(s).

Any mechanism for monitoring file alternation (modify/create/rename/...)
should NOT avoid unmounting filesystem.

With this aspect, are these patches conforming?

If not, there should be some mechanisms to stop monitoring per device /
share basis. Are there some?

 *Imagine removable medias and network shares. Before I found some pages
  stating gvfs-trash is evil and began running script to stop it if
  running, I must shutdown my computer only for removing mounted SD
  card. It's not acceptable behavior for base system.


On Wed, 27 Apr 2016 11:32:05 +0800
Julian Elischer <julian at freebsd.org> wrote:

> the following change is sitting out at github, to add kqueue support 
> for more file operations:
> 
> https://github.com/dmatveev/libinotify-kqueue/blob/master/patches
> 
> does anyone have reasons why we shouldn't import this change.
> 
> libinotify is now a port and could use these.
> 
> 
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> 


-- 
Tomoaki AOKI    junchoon at dec.sakura.ne.jp