Nested class devices and the future of the device model
Posted Oct 20, 2005 20:08 UTC (Thu) by kleptog
In reply to: Nested class devices and the future of the device model
Parent article: Nested class devices and the future of the device model
I'd even venture to say that the fact that you're still using 2.4 and not 2.6 is that there's a lot of incompatibility due to the 2.5 series in between. Going from 2.6.0 to 2.6.13 breaks compatibility less than 2.4.27 to 2.6.0, even though there is more total change, because there isn't the expectation that there will be a major transition that changes everything.
Maybe, maybe not. Near as I can tell you need different versions of udev and hotplug depending on whether you're running 2.6.8, 2.6.13 or (soon) 2.6.16. No matter which way you turn it they're changing user-visible interfaces every other release in a backward incompatable way.
It's a change though. During the 2.4 series I would regularly upgrade my kernel, fairly secure in the knowledge that after the reboot everything would just work. With 2.6 you upgrade and find that your module loading just broke, again. I'm glad there's a lot of guinea pigs out there willing to test the stuff, because I have a day job and work to do. Call me back we 2.8 releases and 2.6 stablises.
to post comments)