Comment 45 for bug 571476

Revision history for this message
letstrynl (letstry-deactivatedaccount) wrote :

@Josh Brown: I really appreciate that you're trying to answer my questions, and thanks for your suggestion.
I'm not sure if a question there would produce any answers, though ;-)

From the the page at https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds:
1) "The mainline kernels builds are produced for debugging purposes and therefore come with no support. Use them at your own risk. "
2) "By definition the mainline kernel builds are made from virgin unaltered mainline kernel sources and therefore do not, and should not, include any Ubuntu patches or drivers. There are also no binary drivers for these kernels."
3) The v2.6.32.x/v2.6.33.y combined tree appears to be missing.

So my conclusion from the info on this page: yes, a Ubuntu kernel config, but no support and no Ubuntu specific patches in these custom kernels. And thus also no reason to run them on an LTS system.

I'm also fully aware of the fact that LTS versions are made for environments that require more stability.
That's why I am developing for LTS and not for other versions.
By the way: a lot of business users have SSD enabled laptops by now.
If their company (as it should) requires an LTS version to be installed, Canonical is creating a problem here.

For now I've installed 11.04 on my SSD enabled demo (as in 10.04 demo) laptop to check the 10.04 filesystem once-in-a-while.
I feel this is a crappy solution (as in: install Debian testing to make Debian Stable stable).
I've read that ext4 TRIM is supported from 2.6.33 and xfs TRIM is supported from 2.6.39 (!!!).
So I had to revert from using my favorite filesystem on my demo laptop. Grmpf.

I just would like Canonical to take a stand here (or elsewhere) and be clear and transparent about LTS on SSD.
Right now it's left to developers what is supported and what is not.

I've not found any remarks on stability anywhere, apart from what I've mentioned before.
Maybe you (or anyone) have a link to a developer thread where this is dicussed ?
I spent some time to find one, couldn't find any.

Maybe I'm totally wrong, and there is a simple (and stable) solution out of this situation.
I'm open to suggestions.