s/changed/extended/
If you extended the interface (either (a) adding majors 2 and 3,
which was done, or (b) using a devfs instead, which is a much much
better solution) you deal with that problem in a way that doesn't
promiscuously break old code.
.
.
.
>Supporting legacy software in this manner is a developers nightmare and
>-hinders- advancement.
Supporting `legacy'[1] interfaces is a developer's dream, as well as
a users dream, because you write to the interface once and don't have
to worry about it from there on in. And the major/minor code stuff
is a particularly bad blotch in the published interface, because this
is Yet Another Case where the major/minor assignments are hidden
inside the kernel with no easy programmatic way of getting them out.
____
david parsons \bi/ "frequently updating your kernel? Where did you
\/ get THAT from?"
-
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.altern.org/andrebalsa/doc/lkml-faq.html