-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest version built fails with "unmkinitramfs" mission #208
Comments
Hi Kamilion, I have been able to build a i386 version, but I can't get the x86_64 to work. Here is the message:
$ ls -l /usr/bin/unmkinitramfs
|
All of the newer kernel builds contain intel and AMD microcode to be applied as early as possible to defend against speculative execution attacks like Spectre. Older images will not contain the unmkinitramfs script required to disassemble such an initramfs. you need the unmkinitramfs script inside the chroot's /usr/bin/unmkinitramfs so you'll have to copy it inside the FileSystem folder yourself during your own build process. |
Hello Kamilion, |
Do you know if it's possible to rebuild let's say, a 18.04 from within a 16.04 without meeting with issues? |
Hello Kamilion, I built the version customizer_4.2.0-0+20180825_all.deb as per the instructions on the present wiki, installed the new depends (especially qt5 as python3 was already there).
A search on the web brought me to install initramfs-tools-core in which "unmkinitramfs" should have been but it was not.
Here is the output from the "customizer -r" command:
" customizer -r
=> Checking
=> Doing sanity checks
=> Gathering information
=> Cleaning up
=> Updating initramfs
update-initramfs: Generating /boot/initrd.img-4.11.0-14-generic
cryptsetup: WARNING: could not determine root device from /etc/fstab
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
=> Copying boot files
=> Extracting casper UUID
/usr/sbin/chroot: failed to run command 'unmkinitramfs': No such file or directory
"
oops, I found your binary! Next step might see me succeed?
The text was updated successfully, but these errors were encountered: