>>>>> "MM" == Matthew Miller <mattdm@xxxxxxxxxx> writes: MM> On Mon, Apr 11, 2005 at 09:26:32AM -0400, Jake Colman wrote: >> version. It is getting hung up on upgrading iptables since it thinks >> it needs a new kernel >= 2.4.20. My problem is that I build a custom >> kernel and do not use RPMs for kernel updates. I am currently at 2.4.30 >> but iptables won't update. MM> The "best practices" thing to do here is to actually build RPMs from MM> your updated kernel. (Which, if you know how to build a kernel, MM> shouldn't actually be very difficult to learn.) In addition to MM> allowing yum to work correctly, you also get the advantage of having a MM> packaged-up version of what you did, for use on other systems or for MM> when you do the next update. MM> Failing that, you could just install but not use the required kernel MM> package. Three questions: 1) If I install a kernel package does it not automatically make it bootable? Obviously, that would screw me over. 2) I like the idea of creating/installing my own 2.4.30 RPM. Can you give me a pointer to information on this? I can build my own kernel, and have done so for years, so I imagine I can handle the RPM part too. 3) How do I tell yum that I want to move from RH 7.2 to RH 7.3 (or something else)? A 'yum update' will update all packages for this version, right? How does a 'yum upgrade' know to move to a new version? Thanks! ...Jake -- Jake Colman Sr. Applications Developer Principia Partners LLC Harborside Financial Center 1001 Plaza Two Jersey City, NJ 07311 (201) 209-2467 www.principiapartners.com
