some changes for (slightly) faster boot

[Michael Schwendt]

On Mon, 03 Jan 2005 23:34:28 +0000, Paul wrote:

> 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

As one observation, the scriptlet itself always returns exit code 0
(true), so that raises the question why rpm sees exit code 255?
What does an strace say at that part?

D:   install: kernel-2.6.10-1.1056_FC4 has 8380 files, test = 0
D:   install: %pre(kernel-2.6.10-1.1056_FC4.i686) asynchronous scriptlet start
D:   install: %pre(kernel-2.6.10-1.1056_FC4.i686)	execv(/bin/sh) pid 5058
D:   install: waitpid(5058) rc 5058 status ff00 secs 0.002
error: %pre(kernel-2.6.10-1.1056_FC4.i686) scriptlet failed, exit status 255
error:   install: %pre scriptlet failed (2), skipping kernel-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