Again, The problem was mis-set expectations. The rest of the industry,
while slow, seems to have no problem letting their current products work
with the newest kernels, because that's what is expected of them. Here we
have expectations set in a manner which were neither confirmed, nor denied
until recently about the state of which kernels are going to be supported
in the future. Any self respecting Linux zealot is going to use the latest
kernel. We use the latest kernels because we trust the community when they
say this is the latest stable kernel, we believe them. Since we believe
them and most of our other software projects in the OS community seem to
'keep up' with the current flow of kernels. Mainly because everyone want's
to make sure that all stuff works with everything. So, here we have a bit
of an issue.
1. Usual expectations were not met as the rest of the community seems to
just know to abide by. An unwritten law if you would.
2. Expectations were misset at a point in time saying that 2.0 would
support the 2.4.x kernel when it became 'stable'.
3. Netraverse messaged that only 3.0 will support 2.4.
4. Here we are.
--
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
