| |||||||||||||
|
| |||||||||||||
Release synchronizationRelease synchronizationPosted May 26, 2008 13:22 UTC (Mon) by forthy (guest, #1525)Parent article: Release synchronization
One problem of the "backport" approach is that you live with an old kernel that won't support new machines. Just over the weekend I've installed OpenSuSE on a new machine, with a 780G chipset - no luck with 10.3, which is just half a year old. So I got the 11.0 beta 3 - that works. I had similar problems a few months ago, when I installed OpenSuSE 10.3 on a new Intel-based motherboard - there was a ethernet driver bug in the installer kernel that was triggered by 4GB of RAM or more. This bugfix has been backported, though, so after updating the kernel, everything was fine. Now, supposed I'd use an enterprise version, SLED 10, I would have a much more outdated kernel. Basically, a model like Debian testing or OpenSuSE Factory is more useful - keep up with the development of the underlying software. The release schedule of such a distribution then is just tied to the distribution specific parts. It also follows the "release early, release often" philosophy many open source projects have.
(Log in to post comments)
|
|
||||||||||||