Linux Kernel 2.6.8 Released

J ROC writes "According to The Linux Kernel Archives kernel 2.6.8 is now out. It includes some fixes from 2.6.7. Happy upgrading." You may want to read this earlier story and think twice before upgrading.

Comments

Download Size

[RAMMS EIN]

I'm repeating this message from OSNews, which had the story first.

I think Linux is a great kernel, but a 42 MB download is really a bit too much for my liking. Much of that is code for hardware that I don't have or features that I don't want. I am a great advocate of modularity, and I would like to see it applied not only to the compiled kernel, but also to the sources. I am aware that this will add some administrative overhead, but it could save a lot of traffic and CPU time.

Here are some ideas:

- Split the distribution in a base that has the common stuff, and optional add-ons for lesser-used network devices, filesystems, etc. etc.

- Employ a BSD ports like system that downloads the sources on request (i.e. when compilation of some part is requested)

- Distribute only the configuration interface, and download only the parts actually needed based on the configuration selected.

I am too occupied now to come up with a proper proposal, but I hope this will set some people thinking.

Re:Download Size

[Anonymous Coward]

That would probably ultimately result in the definition of a stable module interface between the linux kernel and device drivers. This has been explicitly stated as a non-goal by Linus for his tree as it would facilitate the production of closed-source hardware drivers, and we/he wants to "encourage" open-source device drivers (quite rightly IMHO, but I disagree with his method*).

* I think a stable module interface might be _good_ for open-source drivers - hardware manufacturers may never produce their own open-source drivers, but if they are writing closed source drivers to a stable API, that stable API becomes a breakout point at which reverse engineers can install analysis and produce the information required to produce a community-written open source driver. But the trouble with that is that the United Reich of American Corporations has begun pushing for criminalistion of reverse engineering.

Re:Download Size

[Rich0]

Here's an idea, download the patch instead and apply it to your 2.6.7 kernel source.

I wonder if the gentoo maintainers have any plans to offer such a feature.

Gentoo frequently downloads just a patch for security fixes - which is really nice if you have a modem, and you still have the original source lying around (gentoo caches source files, and will re-download whatever it needs).

However, the routine isn't smart enough (to my knowledge) to determine what you already have and as a result what you need to download.

So, if you're running 2.6.7-r6 and -r7 comes out, it is reasonably likely to download a patch.

On the other hand, if 2.6.8 comes out it probably won't. If you go strait to 2.6.8-r1 it will probably download all of 2.6.8 and a patch to make it -r1.

Re:2.6.8.1 is really the latest

[Spirilis]

This might be a silly question, but what does "brown paper bag" release mean? (and how did the phrase come into use? :-D)

Re:2.6.8.1

[bfields]

I guess they were really serious when they said that the stabilization of the kernel was up to the distro maintainers. Guess I won't be downloading 2.6.8 until 2.6.9 comes out.

They've been saying for some time that they'd also release small updates (like 2.6.8.1) against previous releases when necessary, so it should be reasonably safe to take a recent kernel if you wait a couple weeks after the major release and check for any such updates.

For what it's worth, I've been upgrading on every major release (and most of the -rc's too) since 2.6.0, without any disasters.

Of course, depending on which particular drivers you care about and so on, your mileage may vary.

--Bruce Fields