1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Mark Shields wrote: |
5 |
|
6 |
> Sane defaults? Sounds a bit redundant to me. You will have to |
7 |
> tweak the kernel sources since your not using genkernel (my |
8 |
> experience with Redhat is minimal, I assume they use a type of |
9 |
> generic kernel?). There's no way around it. Short story, if you |
10 |
> want "sane defaults", stick with the genkernel. |
11 |
> |
12 |
> On 10/1/05, *John Jolet* < john@×××××.net <mailto:john@×××××.net>> |
13 |
> wrote: |
14 |
> |
15 |
> I've got a farm of 32-bit redhat 7 web servers that we're about |
16 |
> to start |
17 |
> migrating to gentoo on amd64 servers. One question my boss had |
18 |
> that I can't |
19 |
> seem to answer is this. Redhat kernels are supposedly tuned for |
20 |
> "sane |
21 |
> defaults" and I've done no "tuning" at all on the gentoo |
22 |
> boxes. Using gentoo |
23 |
> sources and NOT genkernel, can anyone give me some hints about |
24 |
> what I need to |
25 |
> look at? I'd be very embarrased if I replaced older 32-bit |
26 |
> redhat 7 boxes |
27 |
> with 64-bit gentoo boxes and the migration failed because I |
28 |
> didn't change |
29 |
> some parameter to tweak these guys for apache/zope. |
30 |
> -- |
31 |
> John Jolet |
32 |
> Your On-Demand IT Department |
33 |
> 512-762-0729 |
34 |
> www.jolet.net <http://www.jolet.net> |
35 |
> john@×××××.net <mailto:john@×××××.net> |
36 |
> -- |
37 |
> gentoo-user@g.o <mailto:gentoo-user@g.o> mailing list |
38 |
> |
39 |
> |
40 |
> |
41 |
> |
42 |
> -- |
43 |
> - Mark Shields |
44 |
|
45 |
IIRC, RedHat kernels are relatively generic in that they have almost |
46 |
everything turned on, and/or build the modules so that they can |
47 |
maximize the hardware compatibility. So it is likely that there will |
48 |
be tones of stuff that was turned on, or had modules build for it, |
49 |
that you didn't need. The same will likely be the case for the gentoo |
50 |
kernel. You're best bet is to spend the time on one system going |
51 |
through each kernel option (within reason), if you don't know what it |
52 |
does, read the help and/or turn it off (it will give a recommended |
53 |
setting in the Help). Once you've got your config, use that to build |
54 |
the kernels for the rest fo your systems. |
55 |
|
56 |
I know it's a lot of work, but once you've done it, subsequent |
57 |
configs/compiles for kernel upgrades, security patches, etc. will go |
58 |
MUCH faster. 1) Because you'll have a pre-defined kernel config. 2) |
59 |
You'll know what most of the kernel options are (at least |
60 |
superficially) and which ones you need enabled. You'll just have to |
61 |
read the help for any new ones that pop up. ;-) |
62 |
|
63 |
HTH |
64 |
|
65 |
|
66 |
|
67 |
- -- |
68 |
gentux |
69 |
echo "hfouvyAdpy/ofu" | perl -pe 's/(.)/chr(ord($1)-1)/ge' |
70 |
|
71 |
gentux's gpg fingerprint ==> 34CE 2E97 40C7 EF6E EC40 9795 2D81 924A |
72 |
6996 0993 |
73 |
-----BEGIN PGP SIGNATURE----- |
74 |
Version: GnuPG v1.4.1 (GNU/Linux) |
75 |
|
76 |
iD8DBQFDPuqXLYGSSmmWCZMRAhxlAKDrXCbDtafJPdObBrot58t9Zxuv8ACgjQtw |
77 |
g2gJWap5M6/a415dDccJpdU= |
78 |
=NRaR |
79 |
-----END PGP SIGNATURE----- |
80 |
|
81 |
-- |
82 |
gentoo-user@g.o mailing list |