[LUNI] [kgarner@kgarner.com: Re: redhat 7/rpm woes]From: Keith T. Garner (kgarner@kgarner.com)Date: Mon Mar 05 2001 - 09:42:01 CST
Anyone with more experiance with RH7 have any (more) ideas about the
Keith
-- Keith T. Garner kgarner@kgarner.com The Net Squad, Internet Solutions Architect garner@thenetsquad.com "Yea though I walk through the valley of point-and-click, I will fear no command line: for UNIX art with me; thy kernel and thy shell they comfort me." attached mail follows: On Sun, Mar 04, 2001 at 11:44:00, Mark Notarus said: > ok, so i've had a wierd problem with my ipchains stuff under linux @ 2.2.x > for some time now, and recompiling the kernel hasn't helped. So, i decided > to install fresh and clean, install the 2.4 kernel, and see if the problem > goes away under the new ip/firewall stack. > > I downloaded the entire RedHat/base and RPMS dir to a hard drive, and did a > local install. > > Upon rebooting, i discovered that rpm is broken. It knows how to query the > RPM db, because it can figure out what's installed or not. But any attempt > to install a new RPM fails after the first file with a seg fault. > > Any idea? Ever heard of this? The machine's stock as hell right now... all > I did was edit passwd .... RedHat 7 is the devils tool. You should never use it. :) Honestly, with RedHat you're best to avoid x.0 releases and RedHat 7 sets a new record for suckiness because they shipped a version of gcc "that doesn't exist" as well as some other premature packages. RedHat walks a fine line between pushing the community forward and just making crap. Most of the time they walk the line with skill (using glibc prematurely, for example, worked out pretty well in the long run) but this time they screwed up big time. (Also, because I'm pedantic, its important to point out that this is a redhat problem, not a "linux" problem. Linux does have its problems, but redhat breaking rpm is not one of them.) IMHO, you're better off installing 6.2, and upgrading what you need to upgrade for the 2.4 kernel. Mostly this is the modutils (available in rpm form) as well as the iptables binaries. (I've done this on both my laptop and my desktop and its working like a champ.) In either case, the only thing I can think that would cause this would be somehow some RPMs got curropted and installed, mostly based on the fact that after a web search I don't find any other mention of this. That shouldn't happen because the RPMs should be checking for that, but I'm at a loss to any other explanation. Maybe something in the rpm database is slightly corrupted in a way just to make the binary crash in certain situations. You could try doing an rpm --rebuilddb and see if that does it. If it doesn't, you could reinstall like I've suggested or you could try some more radical procedures. There's a program called rpm2cpio that will turn rpm into a cpio package. Then you could "un-cpio" the package and trying replacing the binaries by hand and see if that fixes it. This procedure becomes more difficult if you have limited access to other machines if your machine doesn't have the required tools installed. If RPM is broken you're stuck if you're a fan of using rpm. :) What a weird problem. Keith -- Keith T. Garner kgarner@kgarner.com The Net Squad, Internet Solutions Architect garner@thenetsquad.com "Yea though I walk through the valley of point-and-click, I will fear no command line: for UNIX art with me; thy kernel and thy shell they comfort me."
This archive was generated by hypermail 2b29 : Mon Mar 05 2001 - 09:43:31 CST |