public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Savage <Mike.Savage@datastream.net>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Kernel patching recommendations
Date: Thu, 14 Feb 2002 09:02:14 -0500	[thread overview]
Message-ID: <41ADD51AFBA1D311811300508B553F71016BCB32@DSMAIL2> (raw)

Good day,
I am in the process of setting up and configuring several Linux boxes to
perform as application servers (apache/jboss/tomcat/etc).  I am trying to
put together the best kernel I can.  While I haven't gotten a chance to
install Gentoo yet, I do follow everything that is going on in the Gentoo
world, as well as reading all of the insightful article on IBM Dev Works.
My question is this: Can you give me any recommendations on patches that I
would need to include for a server system while leaving out all of the
premptible kernel patches (ie, Robert Love, mjc).  I would like to
incorporate all of the security enhancements and the filesystem read latency
fixes (and more) that you have included in your linux-gentoo-2.4.18-pre3
patch, while leaving out the preempt stuff.  Is that possible?
Also, I see that there is now an mjc tree for the best preempt kernel
available.  Is there a similar tree that is compiling patches for server
oriented systems?

Thanks for your time...hopefully I can join the Gentoo movement in the next
couple of weeks, after I deploy these new boxes to production.

Mike

J. Michael Savage
DBA/Sysadmin
Datastream Development
Datastream ASP Hosting Services

<mailto:mike.savage@datastream.net>
(864) 422-7646



             reply	other threads:[~2002-02-14 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 14:02 Mike Savage [this message]
2002-02-14 15:09 ` [gentoo-dev] Kernel patching recommendations Thilo Bangert

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=41ADD51AFBA1D311811300508B553F71016BCB32@DSMAIL2 \
    --to=mike.savage@datastream.net \
    --cc=gentoo-dev@gentoo.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