>>>>> "JC" == Jan Carlson <[EMAIL PROTECTED]> writes:
JC> Stripping down the RH config file IS going to require that you
JC> understand the whole spec file and how the patches interact, etc. etc.
I have a pretty good understanding of the normal kernel build process, how
all of the patches that Red Hat uses interact (even though I don't plan on
using most of them). Really, my problem is not building kernels but in
getting through the spec file. I don't doubt I can figure it out, I was
just hoping that someone else already had.
JC> 1. use RH's kernel with minor mods
That's what I have been doing. None of them work well because the VM
completely breaks down under high usage. (The machines have 700GB of disk
, 2 processors and 2GB of RAM.) 2.4.9-0.18 doesn't even boot on my
hardware. 2.4.3 doesn't support ext3 and hacking it in is beyond me. (I
can hack LVM in OK, but ext3 is much less localized.) 2.4.7-6 and 2.4.7-10
spend 99.9% of all available CPU time running kswapd and kreclaimd once the
cache eats all available memory. What other RH kernels should I try?
JC> I submit that the RH patches anc config file are GOOD things and 1. is
JC> the best way to a good kernel with your mods.
Well, as you can see, it's not really a solution for me. My machines are
atypical, which is why the RH kernels work for you. They don't work for
me, which is why I have to do something else. I could just build kernels,
but I'm trying to do it the "Red Hat way" for maintainability's sake. (I
have multiple machines that need to have the same configuration, and RPMs
are the best way I know to handle this.
So I guess I'll just have to sit down and figure out the spec file.
--
Jason L Tibbitts III - [EMAIL PROTECTED] - 713/743-3486 - 660PGH - 94 PC800
System Manager: University of Houston Department of Mathematics
And your voice is vast and achromatic. But still so precious...
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
