Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks
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-* 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks
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 filesystem.packages-remove filesystem.squashfs initrd.img-3.1.0-1-486 initrd.img-3.1.0-1-686-pae memtest vmlinuz-3.1.0-1-486 vmlinuz-3.1.0-1-686-pae BTW, is it expected to correct that upstream (i.e. in live-build itself ?) Cheers -- http://tartine-blog.blogspot.com/ jabber:georges.mari...@jabber.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks
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.
Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks
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: ~ cat isolinux/live.cfg default live label live menu label ^Live menu default kernel /live/vmlinuz append initrd=/live/initrd.img boot=live config ~ ls live filesystem.packages filesystem.squashfs memtest filesystem.packages-remove initrd.img-3.1.0-1-amd64 vmlinuz-3.1.0-1-amd64 The isolinux configuration refers to missing files: /live/vmlinuz /live/initrd.img I'm using the iso-hybrid target type. Placing the hard links manually and rebuilding the image with lb binary_iso fixes the problems (but uncovers other ones, more on that later). Cheers, Vincent -- Package-specific info: -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii cdebootstrap 0.5.8+b1 ii debootstrap 1.0.38 Versions of packages live-build recommends: ii cpio2.11-7 ii gettext-base0.18.1.1-5 ii gnu-fdisk none ii live-boot-doc 3.0~a24-1 ii live-config-doc 3.0~a31-1 ii live-manual-html [live-manual] 1:3.0~a9-1 Versions of packages live-build suggests: pn dosfstools 3.0.12-1 pn fakeroot1.18.2-1 pn genisoimage none pn memtest86+ | memtest86 none pn mtools none pn parted none pn squashfs-tools | mtd-tools none pn sudo1.8.3p1-2 pn syslinux | grub none pn uuid-runtimenone pn win32-loadernone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks
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 Van: Vincent Fourmond [fourm...@debian.org] Verzonden: vrijdag 9 december 2011 14:00 To: Debian Bug Tracking System Onderwerp: Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks 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: ~ cat isolinux/live.cfg default live label live menu label ^Live menu default kernel /live/vmlinuz append initrd=/live/initrd.img boot=live config ~ ls live filesystem.packages filesystem.squashfs memtest filesystem.packages-remove initrd.img-3.1.0-1-amd64 vmlinuz-3.1.0-1-amd64 The isolinux configuration refers to missing files: /live/vmlinuz /live/initrd.img I'm using the iso-hybrid target type. Placing the hard links manually and rebuilding the image with lb binary_iso fixes the problems (but uncovers other ones, more on that later). Cheers, Vincent -- Package-specific info: -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages live-build depends on: ii cdebootstrap 0.5.8+b1 ii debootstrap 1.0.38 Versions of packages live-build recommends: ii cpio2.11-7 ii gettext-base0.18.1.1-5 ii gnu-fdisk none ii live-boot-doc 3.0~a24-1 ii live-config-doc 3.0~a31-1 ii live-manual-html [live-manual] 1:3.0~a9-1 Versions of packages live-build suggests: pn dosfstools 3.0.12-1 pn fakeroot1.18.2-1 pn genisoimage none pn memtest86+ | memtest86 none pn mtools none pn parted none pn squashfs-tools | mtd-tools none pn sudo1.8.3p1-2 pn syslinux | grub none pn uuid-runtimenone pn win32-loadernone -- no debconf information -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111209130036.5716.88261.report...@nausicaa.bip.glm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651520: live-build: booting a custom image fails because of missing /live/vmlinuz and /live/initrd symlinks
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 binary/live/vmlinuz-* binary/live/vmlinuz That does the trick, thanks ! (although mind it is not initrd.lz but initrd.img). I will see if now my other problems go away with a sid-based live image. Cheers, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
