-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thilo Bangert wrote: | Ramon van Alteren <[EMAIL PROTECTED]> 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----- -- [email protected] mailing list
