From: Marcin Hlybin <marcin.hlybin@swmind.com>
To: linux-kernel@vger.kernel.org
Subject: Open Discussion, kernel in production environment
Date: Mon, 1 May 2006 23:57:48 +0200 [thread overview]
Message-ID: <200605012357.48623.marcin.hlybin@swmind.com> (raw)
Hello,
I always configure and compile a kernel throwing out all unusable options and
I never use modules in production environment (especially for the router).
But my superior has got the other opinion - he claims that distribution
kernel is quite good and in these days optimization has no sense because of
powerful hadrware.
What do you think? I have few arguments for this discussion but I wonder what
you say. Please, try to substantiate your opinions.
And the second question: which kernel branch/version *and why* do you use in
production environment?
Regards
--
Marcin Hlybin, marcin.hlybin@swmind.com
Sys/Net Administrator, tel. +48 12 2523 402
next reply other threads:[~2006-05-01 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 21:57 Marcin Hlybin [this message]
2006-05-01 22:36 ` Open Discussion, kernel in production environment Bernd Eckenfels
2006-05-02 6:57 ` Andi Kleen
2006-05-02 7:01 ` Arjan van de Ven
2006-05-02 11:29 ` Jan Engelhardt
2006-05-03 1:06 ` David Lang
2006-05-03 2:30 ` Grant Coady
2006-05-03 16:40 ` Jan Engelhardt
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=200605012357.48623.marcin.hlybin@swmind.com \
--to=marcin.hlybin@swmind.com \
--cc=linux-kernel@vger.kernel.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