Le 23 déc. 2011 à 02:21, slo.sle...@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-*
2011/12/9 Vincent Fourmond fourm...@debian.org:
That does the trick, thanks ! (although mind it is not initrd.lz but
initrd.img).
Not in all cases.
I'm facing the same problem (I think) building a simple live-iso
following tutorial1 of live-build manual.
Thus I have :
filesystem.packages
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
Package: live-build
Version: 3.0~a40-1
Severity: important
Hello,
I've just built a custom image using live build, and it
unfortunately refuses to boot the linux image (hardware information
and memory test work).
Looking more closely at the generated iso image, here is what I found:
~
Hi Vincent,
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
Good luck!
Regards, Piethein
On Fri, Dec 9, 2011 at 2:23 PM, Piethein Strengholt
pieth...@strengholt-online.nl wrote:
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
6 matches
Mail list logo
