I've previously asked about some fsnotifier behaviour.
We have a couple file systems we'd like to watch that don't support inotify, but that do support other kinds of (custom) watchers. At the moment we have a shim layer at the fsnotifier level, but this doesn't feel like it's the cleanest way to do it, and it's hard to debug.
Would it make sense to break out a file watching interface + extension point that can grab paths and watch them instead of them going to fsnotifier? This way we could ship optional plugins for watching these file systems for users that care about them.
If it makes sense I don't immediately know what would be the cleanest way of associating a path with a particular kind of file system, and how to deal with platform differences. We only support linux, and hard code paths, but that won't fly as a general solution.