Anyway, when are we coming up with a snappy "Linux 2000" before Bill
"The Monster" Gates puts his foot in the door?
I do not have any such problems, but sometimes my colleagues have:
"It worked yesterday now it is broken." If Linux wants to be mainstream,
it got to be less destructive. I have now converted an industrial group
with a $3M budget to linux and they would like to get something for
their money :-)) - obviously linux is MORE than just hacking away on
the kernel.
WE are taking linux very seriously - even if we had to pay for it -
"no, you said it, you pay, not me".
If we would like to be the elephant couldn't we just ring a bell
before the porcelain is broken to notify the clerk to clean up?
As in "kernel-space--user-space" interaction? Or as in API -
APIs are sacred, let people know about changes IMMEDIATLEY if
anything changes? I've written a device driver for a since
deceased co-processor board (it WAS fast in 1993) and I have
sevreral generations of patches to cope with API changes.
Arno