| |||||||||||||
|
| |||||||||||||
Nested class devices and the future of the device modelNested class devices and the future of the device modelPosted Oct 20, 2005 21:22 UTC (Thu) by iabervon (subscriber, #722)In reply to: Nested class devices and the future of the device model by kleptog Parent article: Nested class devices and the future of the device model
Switch to 2.6.13.x, and apply backported security patches. The new scheme essentially pushes the "everything stays the same" level down a digit, so 2.6.13 to 2.6.14 is essentially like 2.2 to 2.4, except that it won't break nearly as much. The main caveat is that I think it's worth waiting either for 2.6.x.1 or for 2.6.x to turn out stable, because the quality control on 2.6.x as first released isn't that good; 2.6.x is the point at which the version is turned over to the "stable" maintainers, not their first release.
I also haven't heard anything about module loading breaking, except for between 2.4 to 2.6. There has been code that's had bugs, and if it's built as a module, it causes problems when you load it, but that's hardly the same thing, and it isn't unlike problems that crop up on occasion in 2.4.
(Log in to post comments)
|
|
||||||||||||