Quote:
Or, alternatively, does it need certain kernel hooks to survive and indeed thrive?
I would think it is like the vfs and vfs_ops.h family of header files and accompanying calls.
You produce alternate functions to be called when the user
mounts/dismounts a file system as well as alternate functions for when any code uses typical file manipulation library calls (open(), stat(), read(), seek() or a dozen other typical calls).
You create kernel modules to load these into the kernel, and if any utility (anything from “ls” to “write()”, etc)performs an action within your file system, then your function gets the callout, and you can have your way with the data.
Well of course this makes sense - everything eventually relates back to the kernel, doesn’t it?
So is the suggestion that Linus can effectively block these hooks from being integrated in, or does he basically say I don’t like it but do it if you must and we’ll see who comes out the winner in the end?