From: Ramon van Alteren <ramon@vanalteren.nl>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] binary kernel package
Date: Tue, 12 Feb 2008 09:19:56 +0100 [thread overview]
Message-ID: <47B156AC.4020400@vanalteren.nl> (raw)
In-Reply-To: <200802111925.09071.bangert@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thilo Bangert wrote:
| Ramon van Alteren <ramon@vanalteren.nl> said:
|> What's wrong with building your stage4 with catalyst and have it
|> include a kernel ?
|
| and what do you do after a weekend like this one: kernel upgrade on 1300
| hosts?
What would you do ?
But yes if there's a kernel vurnerability that affects our environment
we upgrade kernels on all servers starting with the internet-facing ones.
Although the question is interesting I fail to see any relevance to
installing (or upgrading) kernels in a automated manner.
Actually I'd say that if you have a trusted and well-defined automated
way to build and install/upgrade kernels you're actually better off.
|> We use catalyst to generate all our install images and catalyst uses
|> genkernel internally to include it in the image. Just specify which
|> kernel you'd like and provide a .config for it.
|>
|> We've installed 1300 servers that way, I'll personally guarantee you
|> that it works :-D
|
| :)
| thats more than good enough for me.
Grin, no thanks.
It also helps in other ways: You gain repeatable image builds including
kernels so after a weekend like this one you can easily rebuild your
kernel + image and *just* distribute the updated kernel to your serverpark.
Ramon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHsVaqwiVM6CtDHQ0RAgLmAJwJ9J1mQ2rPkRgndy0RFQ2SQX7IxACfV0oV
ntczcCCNwpd2xuqxKUnx1mI=
=9kGM
-----END PGP SIGNATURE-----
--
gentoo-server@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-02-12 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 11:15 [gentoo-server] binary kernel package Thilo Bangert
2008-02-10 12:44 ` "Todd M. Hébert"
2008-02-10 14:58 ` Thilo Bangert
2008-02-10 16:26 ` "Todd M. Hébert"
2008-02-10 18:59 ` Petteri Räty
2008-02-10 19:35 ` Todd Hebert
2008-02-10 19:54 ` Tom Grace
2008-02-11 4:03 ` RijilV
2008-02-11 9:13 ` Ramon van Alteren
2008-02-11 18:25 ` Thilo Bangert
2008-02-11 18:59 ` Brandon Adams
2008-02-12 9:45 ` Ramon van Alteren
2008-02-12 8:19 ` Ramon van Alteren [this message]
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=47B156AC.4020400@vanalteren.nl \
--to=ramon@vanalteren.nl \
--cc=gentoo-server@lists.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