Clay Barnes wrote:
I like using a term that is already in an accepted part of the
kernel. Extensions might smack of plugins a bit much, and we're
trying to avoid just doing a s/plugins/extensions/ of the
arguments we're seeing now.
We could do that with almost anything:
Or just modules... netfilter has modules that allow us to write
very cool and weird stuff (like unclean match once was) and
nobody complains.
Except that modules could also possibly remind people of proprietary
modules, like the nvidia/ATI/vmware stuff.
Still, if we allow netfilter, why not Reiser4 modules?
Another word could be 'hooks'
I don't think this would quite work. A hook describes more the place
you connect to, whereas a module/plugin/whatever...
Think of it this way -- the hook is what a plugin would plug in to.
So it may not matter much what we name them, we're probably still going
to need that cut'n'paste argument. Might be easier with "modules", though.
