Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks

[Axel <axel.ml@laposte.net>]

Le 23 déc. 2011 à 02:21, slo.sleuth@gmail.com a écrit :

> I attempted to follow the guidelines:
> 
> 
> You need a hook to fix this. Create a file named renamekernel.binary. Place this in the hook dir. The file should have the following contents:
> 
> mv binary/live/initrd.img-* binary/live/initrd.lz
> mv binary/live/vmlinuz-* binary/live/vmlinuz
> 
> I my config/hooks/renamekernel.binary is executable, and has the contents:
> 
> mv binary/live/initrd.img-* binary/live/initrd.img
> mv binary/live/vmlinuz-* binary/live/vmlinuz
> 
> but with 'lb build', I get this error:
> 
> P: Begin executing hooks...
> mv: target `binary/live/initrd.img' is not a directory
> mv: target `binary/live/vmlinuz' is not a directory
> E: config/hooks/renamekernel.binary failed (exit non-zero). You should check for errors.
> 
> I can change to binary/live/ and manually rename the kernel and initrd, but I can't figure out why the mv command fails in the hooks script.
> 
> Ah wait, I can, but I'll continue this in case someone else has the problem:  I have both 486 and 686-pae kernels and initrd in the directory, to mv is looking for a dir.  Deleting the unwanted kernel and initrd will fix.  Configuring lb config to only supply one kernel will prevent recurrence.


This cannot work since initrd.img-* matches many files (486 and 686 versions). By default, both 486 and 686 versions are built. Try to build only one flavour (by giving the following argument to lb config : --linux-flavours 686 ), this will build only one initrd file and your "mv" command will work.