From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
/sbin/init is dynamically linked. Upgrades that change libc.so
or ld-linux.so may cause init to crash on startup. Upgrading
Redhat 7.3 (glibc 2.2.5) to Fedora Core (glibc 2.3.2) does this.
Upgrading glibc, glibc-devel, and bin-utils from 2.2.5 to 2.3.2
at the command line will do the same thing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start with a clean glibc 2.2.5 system
2.Upgrade glibc, glibc-devel, and bin-utils to 2.3.2
Actual Results: rpm seg faults, preventing upgrades or downgrades.
/sbin/init may or may not run. Trying chroot in
rescue mode seg faults
Programs used at boot time like /sbin/init should be statically linked,
as system upgrades are not atomic and can leave shared objects in
unpredictable and incompatible states.
Rpm and any support tools (like cpio) should be statically linked as well.
[notting@nostromo: ~]$ file /usr/lib/rpm/rpmi
/usr/lib/rpm/rpmi: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.2.5, for GNU/Linux 2.2.5, for GNU/Linux 2.2.5,
statically linked, stripped
That is statically linked. init has never been statically linked to
the best of my knowledge, and this is the first I've heard of this.
Just the glibc upgrade caused the crash for you.
Erm, that last statement was a question.
Closing, no response. Note that glibc does reexec init on upgrades.
Package name is now sysvinit in Fedora.