From: deferraz@terra.com.br (André Ferraz)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Some help about backporting a nic module to 2.6.32 longterm
Date: Wed, 11 Jan 2012 19:42:04 -0200 [thread overview]
Message-ID: <20120111194204.64acb660@debo-air.ferraz.is-a-geek.net> (raw)
In-Reply-To: <20120110013027.GA11889@kroah.com>
> A: No.
> Q: Should I include quotations after my reply?
Sorry about that
> Why are you using grsec? Why has it not been updated in the many
> years since 2.6.32 was released?
Grsec patchset brings some security features that i need in my
servers, they are accessible for the clients via ssh and some
of them gets hacked, they try to exploit the system and other
things... and the project has patchet for the 3.1.8 kernel, but
is a test branch, the stable branch is based on the 2.6.32
longterm (http://grsecurity.net/download_stable.php)
> Just backporting a single driver, usually isn't that easy, as it
> relies on other parts of the kernel.
Indeed , but my problem now is to understand why still patching
my kernel with the modifications of a CentOS 6 (just bnx2x
driver) when i boot the kernel it still show me the old release
version, the patch is applied but looks like that i'm missing
some based on the firmware files that CentOS has on their
kernel, thats why i asked you guys from the mailing list if
there is some documentation that cold help me understand this
> good luck,
Thanks Greg
next prev parent reply other threads:[~2012-01-11 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 21:19 Some help about backporting a nic module to 2.6.32 longterm André Ferraz
2012-01-09 22:49 ` Greg KH
2012-01-10 1:08 ` André Ferraz
2012-01-10 1:30 ` Greg KH
2012-01-11 21:42 ` André Ferraz [this message]
2012-01-11 22:13 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120111194204.64acb660@debo-air.ferraz.is-a-geek.net \
--to=deferraz@terra.com.br \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).