[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Obtaining a Newer Kernel



On Mon, 27 Aug 2012 01:25:11 -0500
Stan Hoeppner <stan@hardwarefreak.com> wrote:

> On 8/26/2012 7:44 PM, Alex Robbins wrote:
> 
> > need something more recent than testing
> 
> Why?  IIRC you previously mentioned you *needed* 3.3 or higher.  Can you
> tell use what feature it is you need that was introduced in 3.3?
> 
> > not asking which of the above options is stable and secure (I know it
> > is neither),
> 
> Correct.  It's a kernel, not an entire distro.  Debian changes very
> little, if any, kernel code, for its distributed kernels.  As with any

Debian definitely *does* change *some* kernel code:

"The source from which the Debian binary kernels are built is obtained
by taking the source from linux_version.orig.tar.xz (that is, pristine
kernel source with problematic parts removed) and applying a set of
Debian patches. These patches typically implement essential fixes for
serious bugs and security holes. The Debian version of the kernel
packages has the form version-revision where version is the upstream
version of the kernel (like 3.2.20) and revision determines the
patchlevel. For example, the packages with version 3.2.20-1 are built
from the linux_3.2.20.orig.tar.xz source, patched up to patchlevel.
Certain packages include extra 'featuresets' not included in the
upstream source, such as rt."

http://kernel-handbook.alioth.debian.org/ch-source.html

> distro, Debian sets various configuration options and excludes certain
> kernel features from its kernels, such as all the non-free bits of the
> vanilla source.  Debian makes no changes to the vanilla kernel that make
> it more or less stable or secure.  Note that the Debian kernel team is
> one of the largest contributors to upstream source.  Thus when Debian
> pulls vanilla source into experimental, they're receiving all of their
> own recent kernel patches to the stable branch.

I don't think this is quite true; while there is an explicit
preference for patches that have already been accepted upstream, it
seems that this is not a rigid rule:

http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines

Celejar


Reply to: