Linked by Thom Holwerda on Tue 3rd Jan 2006 16:45 UTC, submitted by diegocg
Linux Linux 2.6.15 has been released after two months and a week of development. You can check the comprehensible changelog or grep the full changelog. There are some new features like shared subtrees, UDP fragmentation offload, PPP MPPE encryption (VPN), NTFS write support (except for creating files), PPC64 thermal improvements, support for the late-2005 powerbook series, SATA passthru support (for SMART), console rotation for fbcon, nf_conntrack subsystem, some scalability and performance improvements, and lots of other changes. As always, download it from, or wait for your distributor to ship it.
Thread beginning with comment 81357
To read all comments associated with this story, please click here.
by Cramit on Tue 3rd Jan 2006 21:47 UTC
Member since:

Are they ever going to stabiliz the 2.6 kernal and start a 2.7 dev kernal. I don't really like the fact that features are being added to the main branch of the kernel...I like stability, and I don't think i am the only one

Reply Score: 2

RE: 2.7?
by Rahul on Tue 3rd Jan 2006 22:26 in reply to "2.7?"
Rahul Member since:

Features are not orthogonal to stability. As long the changes you make are not intrusive like adding a a new driver which doesnt require changing existing infrastructure or if you are fixing things which are already known to be broken like better write support for a filesystem then there isnt a problem with changing stuff.

Reply Parent Score: 1

RE[2]: 2.7?
by BryanFeeney on Tue 3rd Jan 2006 22:36 in reply to "RE: 2.7?"
BryanFeeney Member since:

Unfortunately the changes are all relatively intrusive, with many significant API changes, thus stability is comprised (which is why Greg KH is working on his 2.6.x.y semi-stable tree). What's more highly intrusive work with the potential for a big payoff (real-time Linux, Reiser4 integration / fs upgrades) is rejected out of hand as it would be too hard to get any sort of a release out the door in a reasonable amount of time.

The result is something that's fun to work on, but hard for distributors to maintain (I dread to think how the Debian developers are maintaining 2.6.8 for example, given that it's totally orphaned at this stage), and which also sees no major work in hard areas.

Reply Parent Score: 1

RE: 2.7?
by tihirvon on Tue 3rd Jan 2006 22:41 in reply to "2.7?"
tihirvon Member since:

No they are not. Having one branch has the advantage there's no need to backport features to old kernel. Also new features come available sooner.

Actually there are two 'branches', 2.6 and -mm which contains experimental patches. When the code in -mm has been proven stable and useful enough it is merged to mainline.

Stability might suffer a little though but not much really because there's two weeks time frame after a new release (like 2.6.15) when new features are added. After that only bug fixes are accepted. Release candidates are released until kernel becomes stable. As you can see from the changelog there are only small changes after the latest -rc.

Of course 2.6.15 can still contain some bugs (especially in drivers) if not enough people have tested the -rc kernels.

Reply Parent Score: 1

RE: 2.7?
by cendrizzi on Wed 4th Jan 2006 00:10 in reply to "2.7?"
cendrizzi Member since:

Are you personally experiencing stability issues related to the kernel? My issues tend to revolve around X server and higher up the stack personally (and even those are not common).

Reply Parent Score: 1