Hi,
> "rpm --query --scripts" on the package might be more helpful.
Okay...
preinstall scriptlet (using /bin/sh):
/sbin/modprobe loop 2> /dev/null > /dev/null || :
exit 0
postinstall scriptlet (using /bin/sh):
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --package kernel --
mkinitrd --depmod --install 2.6.10-1.1056_FC4
if [ -x /usr/sbin/hardlink ] ; then
pushd /lib/modules/2.6.10-1.1056_FC4/build > /dev/null ; {
cd /lib/modules/2.6.10-1.1056_FC4/build
find . -type f | while read f; do hardlink -c /lib/modules/*/build/$f
$f ; done
}
popd > /dev/null
fi
preuninstall scriptlet (using /bin/sh):
/sbin/modprobe loop 2> /dev/null > /dev/null || :
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --rminitrd --
rmmoddep --remove 2.6.10-1.1056_FC4
> Many scriptlets are executed in /bin/sh, so first make sure your
> /bin/sh works completely, then look what script contents fail.
I can start /bin/sh from the command line. Is there any way to test
everything is functioning under it? Installing a kernel always fails on
pre.
I can run the preinstall script happily within /bin/sh
TTFN
Paul
--
"He's not the Messiah, he's a very naughty boy!"
- Life of Brian, Monty Python
Attachment:
signature.asc
Description: This is a digitally signed message part
