Yes, the term "obsolete" is a bit confusing to end-users.
When applied to a device driver, there are three separate definitions
that are at risk of being conflated:
- The hardware it supports is obsolete (EISA is obsolete)
- The code (which may still work) has been superseded by a new improved
version (OSS is obsolete, Linus' original HD driver is obsolete)
- The code has not kept up with the kernel and no longer works with the
current kernel.
The third category is what we're trying to identify here.
The risk of confusion is particularly large because often two of those
definitions apply at once.
If you want a suitably specific term for #3, I'd try CONFIG_BITROT.
I think that clearly conveys, in one word, "this code used to work, but
no longer does due to a lack of maintenance, and unless someone
breathes life back into it it will be given a decent burial."
(The other option that comes to mind is CONFIG_ORPHANED, which says
about the same thing, but might be unnecessarily insulting to a nominal
maintainer who hasn't been able to keep it up to date. "Orphaned" implies
that nobody's trying. "Bit rot" implies only a lack of *success*.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:34 EST