Description of problem: The dmraid binary in RHEL4.5.0 (dmraid-1.0.0.rc14-1_RHEL4_U5) now links to the dmraid library in /usr/lib: # ldd /sbin/dmraid libdmraid.so.1.0.0.rc14 => /usr/lib/libdmraid.so.1.0.0.rc14 (0x008cd000) libdevmapper.so.1.02 => /lib/libdevmapper.so.1.02 (0x0026c000) libselinux.so.1 => /lib/libselinux.so.1 (0x0046d000) libsepol.so.1 => /lib/libsepol.so.1 (0x00254000) libc.so.6 => /lib/tls/libc.so.6 (0x00121000) /lib/ld-linux.so.2 (0x00103000) This means that initscripts need to use the /sbin/dmraid.static version, as is already the case in the RHEL5 initscripts (initscripts-8.45.15.EL). Version-Release number of selected component (if applicable): initscripts-7.93.29.EL How reproducible: 100% Steps to Reproduce: 1. Install dmraid on a system with /usr on a separate file system 2. Reboot the machine Actual results: "/sbin/dmraid: error while loading shared libraries: libdmraid.so.1.0.0.rc14: can not open shared object file: No such file or directory" dmraid devices are not configured and must be manually activated by running dmraid after /usr is mounted. Expected results: dmraid runs successfully and configures attached devices if present. Additional info: This is a regression from U4 caused by the change in the dmraid package.
This would also break third-party customer scripts - I think the simpler solution is to not change how dmraid is built.
I agree unless I overlook an issue with running dmraid.static in initscripts. Size ?
*** Bug 234204 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0175.html