FUSD's user-kernel interface won't change spuriously, but it sometimes
will need to change as features are added. Some such changes are
already in the works.
The fact that FUSD provides a semi-stable binary interface for servicing
device-file callbacks isn't really FUSD's design goal as much as it is an
accidental side effect. Making a stable binary interface for kernel
device drivers is the objective of, say, UDI (I think). The purpose of
FUSD is just to be able to proxy the callbacks to userspace.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/