PDA

View Full Version : iso not generated from lb build



Lensing
2013-09-07, 06:01
After following http://docs.kali.org/downloading/live-build-a-custom-kali-iso and running lb build I do not get a .iso in the chroot directory, nor in any directory (find -name "*.iso" returns nothing).
The only changes I made were to the desktop environment (in config/package-lists/kali.list.chroot) as described in the docs.
lb build seems to run normally without any errors that I can see.

I've looked for other people having the same problem, but I found nothing. I might be doing something really stupid, as I've been through the whole process a few times on different systems.

uname -a

Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux

live-build-config contains

auto binary binary.log binary.packages build_all.sh cache chroot chroot.packages.install chroot.packages.live config local README
and chroot contains

bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux srv sys tmp usr var
I've tried messing around with lb config options, like lb config --architecture amd64 -b iso after the original method didn't work, which didn't help any.

Kaliprom
2013-09-08, 13:19
Same here dude :(

DavyJones
2013-09-19, 06:59
i have the same issue, where is the .iso supposed to be located? what is it supposed to be named?

en3rgetic
2013-09-27, 12:16
Hi guys,

I have the same. Where is the ISO.

And is the site www.lwfinger.com down? During the build it can't fetch the broadcom drivers from there.
Checking via the browser shows a "Oops" in Chrome. Page not found.

I hope someone can help.

Thanks.

Snizz
2014-02-12, 18:11
I have experienced a similar problem. I'm curious if others could share tail end of their build/binary.log file to see if there is a commonality here. My hunch (in my case) is the /usr/bin/env is looking for /root/openvpn.chroot rather than /chroot/root/openvpn.chroot.

Curious if others are seeing this same issue which might be preventing the ISO from being created.



# tail -20 binary.log

...
Setting up user-setup (1.48) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.12-kali1-amd64
cryptsetup: WARNING: could not determine root device from /etc/fstab
libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.7-trunk-amd64/modules.dep.bin'
intel-microcode: cpuid MSR kernel support missing
intel-microcode: disabling IUCODE_TOOL_SCANCPUS option
live-boot: core filesystems devices utils memdisk udev wget blockdev ftpfs.
[2014-02-12 12:00:29] lb chroot_includes
P: Begin copying chroot includes...
22 blocks
[2014-02-12 12:00:29] lb chroot_hooks
P: Begin executing hooks...
/usr/bin/env: /root/openvpn.chroot: No such file or directory
E: config/hooks/openvpn.chroot failed (exit non-zero). You should check for errors.
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...





Example of "chroot/root/openvpn.chroot"

#!/usr/bin/bash
update-rc.d openvpn enable
update-rc.d ssh enable





Example of config/hooks/openvpn.chroot

#!/usr/bin/bash
update-rc.d openvpn enable
update-rc.d ssh enable

Snizz
2014-02-13, 18:00
For the Kali ISO of Doom Blog Post -(http://www.offensive-security.com/kali-linux/kali-linux-iso-of-doom/)

My issue above turned out to be a fairly easy fix for me, the blog post called had #!/usr/bin/bash in the file config/hooks/openvpn.chroot. Just remove the /usr and I was good to go. Hope this helps others.


Example of config/hooks/openvpn.chroot

#!/usr/bin/bash
update-rc.d openvpn enable
update-rc.d ssh enable


The following corrected the issue for me:


Corrected config/hooks/openvpn.chroot

#!/bin/bash
update-rc.d openvpn enable
update-rc.d ssh enable

Snizz
2014-02-14, 20:32
Another minor bug in the Kali ISO of Doom Blog Post (http://www.offensive-security.com/kali-linux/kali-linux-iso-of-doom/) that required me to rebuild the ISO. The following line should be broken up, else you'll get a password mismatch when the ISO boots.


d-i passwd/root-password-again password toor popularity-contest popularity-contest/participate boolean false

Here is the full config/debian-installer/preseed.cfg file:



root@kali:~/build# cat << EOF > config/debian-installer/preseed.cfg
d-i debian-installer/locale string en_US
d-i console-keymaps-at/keymap select us
d-i mirror/country string enter information manually
d-i mirror/suite string kali
d-i mirror/codename string kali
d-i mirror/http/hostname string archive.kali.org
d-i mirror/http/directory string /kali
d-i mirror/http/proxy string
d-i clock-setup/utc boolean true
d-i time/zone string US/Eastern
# Disable volatile and security
d-i apt-setup/services-select multiselect
# Enable contrib and non-free
d-i apt-setup/non-free boolean true
d-i apt-setup/contrib boolean true
d-i partman-auto/method string regular
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-md/device_remove_md boolean true
d-i partman-lvm/confirm boolean true
d-i partman-auto/choose_recipe select atomic
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true # Add our own security mirror
d-i apt-setup/local0/repository string http://archive.kali.org/kali-security kali/updates main
d-i apt-setup/local0/comment string Security updates
d-i apt-setup/local0/source boolean false
d-i apt-setup/use_mirror boolean true
tasksel tasksel/first multiselect standard
d-i pkgsel/upgrade select full-upgrade
# Install a limited subset of tools from the Kali Linux repositories
d-i pkgsel/include string openssh-server openvas metasploit-framework metasploit nano openvpn ntpupdate
# Change default hostname
d-i netcfg/get_hostname string unassigned-hostname
d-i netcfg/get_domain string unassigned-domain
d-i netcfg/hostname string kali # Do not create a normal user account
d-i passwd/make-user boolean false
d-i passwd/root-password password toor
d-i passwd/root-password-again password toor
d-i popularity-contest popularity-contest/participate boolean false
d-i grub-installer/only_debian boolean true
d-i grub-installer/with_other_os boolean false
d-i finish-install/reboot_in_progress note
EOF

cadash
2014-02-18, 01:11
Make sure you are using Debian and not Ubuntu, I couldn´t the the latter to make a good build but that´s ok because there are some differences between these two and Kali is Debian based. Use the root dir, sometimes I had to issue lb build a few times to have the image finally built. The name of the file is binary.hybrid.iso and is located in the root dir. Try also using lb build --verbose, it might give you some clues about where the error is