Thread (6 messages) 6 messages, 2 authors, 2012-01-11

Some help about backporting a nic module to 2.6.32 longterm

From: Greg KH <hidden>
Date: 2012-01-10 01:30:27

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Mon, Jan 09, 2012 at 11:08:18PM -0200, Andr? Ferraz wrote:
Hi Greg,
	the problem is that i need to stay with the 2.6.32 grsec
	patchset for my servers, if i didn't have any dependencies like
	that sure i'll be using the 3.2 kernel.
Why are you using grsec?  Why has it not been updated in the many years
since 2.6.32 was released?
	The idea is to just backport this device driver, the rest of
	the drivers works pretty well, but i didnt find any HowTo or
	some documentation specific to the process of update a driver
	on your kernel source.
Just backporting a single driver, usually isn't that easy, as it relies
on other parts of the kernel.

The kernel is ment to be used as a "whole" release, picking and choosing
is very tough at times, and you will be on your own.

I don't recommend it at all.

good luck,

greg k-h
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help