# Okay, per-program ways of doing this that don't share code and databases
# are a bad idea, I agree. But that still doesn't mean it can't be done
# in userspace via generic shared libraries, or that keeping track of this
# information in kernel space is necessarily the way to go. Are you
# objecting to the lack of code re-use, or to the fact that too much is
# being done in user space?
Well..considering that this stuff is already supported in three of the
filesystems Linux supports (although Linux itself doesn't), it makes
reasonable sense that this stuff should go kernel-side. Even if the more
generic stuff lies in userland, you've still got to have kernel-side stuff
in order to handle existing filesystems' implementations.
-- Mo McKinlay Chief Software Architect inter/open Labs ------------------------------------------------------------------------- GnuPG Key: pub 1024D/76A275F9 2000-07-22 Mo McKinlay <mmckinlay@gnu.org>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:29 EST