This is the config I have used when I had the error and subsequent failure. It is a modified version of what used to be use by Ozzie (STAR Linux). This configuration works for everything I have done until the 2nd flavour as per Subhani's suggestion is added and that breaks this configuration.
#!/bin/sh set -e #_A="amd64" \ CPU Architecture i386 = 32 BIT (686 and 686-pae) amd64 = 64 BIT. It would be great if we could build ARM images for RPi. _A="i386" \ #_AA="main contrib non-free" \ Archive Areas must have at least main, contrib and non-free are optional _AA="main contrib non-free" \ #_BIT="x86-64" \ x86 = 32 BIT system x86-64 = 64 BIT system _BIT="x86" \ #_DD="buster" \ Debian Distribution e.g. buster _DD="buster" \ #_D="Rugged" \ Debian Derivative Distro e.g. Cobber or Rugged _D="Rugged" \ #_F="false" \ When the answer to a question is false _F="false" \ #_FL="amd64" \ Linux Flavour as in BIT. Options (currently) are 686 686-pae amd64. Flavor MUST match _A="" (CPU Architecture) to work _FL="686-pae amd64" \ #_MB="http://deb.debian.org/debian/"; \ Repository Mirror to be used _MB="http://deb.debian.org/debian/"; \ #_MS="http://security.debian.org/"; \ Security Repository Mirror, this is usually always http://security.debian.org/ unless you are building a non Debian system _MS="http://security.debian.org/"; \ #_T="true" \ When the answer to a question is true _T="true" \ #_DE="builder-choice" \ Desktop Environment or Window Manager used in the build. Choices are Cinnamon, Gnome, KDE, LXDE, LXQT, Mate, TDE (Trinity), XFCE, etc etc etc. _DE="Mate" \ #_WM="builder-choice" \ Window Manager used in the build. Choices are, currently, Fluxbox. _WM="Fluxbox" \ lb config noauto \ --apt "apt" \ --apt-indices "${_F}" \ --apt-options "--yes" \ --apt-recommends "${_F}" \ --apt-secure "${_T}" \ --apt-source-archives "${_F}" \ --aptitude-options "--assume-yes" \ --architectures "${_A}" \ --archive-areas "${_AA}" \ --backports "${_F}" \ --binary-filesystem "fat32" \ --bootappend-live "boot=live config quiet splash keyboard-layouts=us" \ --bootappend-live-failsafe "boot=live components memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash vga=normal" \ --bootloaders "syslinux, grub-efi" \ --cache "${_T}" \ --cache-indices "${_F}" \ --cache-packages "${_T}" \ --cache-stages "bootstrap chroot" \ --checksums "md5 sha1 sha256" \ --chroot-filesystem "squashfs" \ --debian-installer "live" \ --distribution "${_DD}" \ --debian-installer-distribution "${_DD}" \ --debian-installer-gui "${_T}" \ --fdisk "fdisk" \ --firmware-binary "${_F}" \ --firmware-chroot "${_F}" \ --gzip-options "-6 --rsyncable" \ --hdd-label ""${_D}"Live" \ --initramfs "live-boot" \ --initramfs-compression "gzip" \ --iso-application ""${_D}"-Live-"${_DE}"" \ --iso-preparer "Michael" \ --iso-publisher ""${_D}" GNU/Linux" \ --iso-volume ""${_D}" "${_DE}" "${_BIT}" $(date +%Y%m%d)" \ --keyring-packages "mx19-archive-keyring" "antix-archive-keyring"/ --linux-flavours "${_FL}" \ --linux-packages "linux-image" \ --mirror-binary "${_MB}" \ --mirror-bootstrap "${_MB}" \ --mirror-debian-installer "${_MB}" \ --parent-mirror-binary-security "${_MS}" \ --parent-mirror-bootstrap "${_MB}" \ --parent-mirror-chroot-security "${_MS}" \ --quiet "${_F}" \ --security "${_T}" \ --source "${_F}" \ --source-images "${_F}" \ --system "live" \ --tasksel "apt" \ --uefi-secure-boot "enable" \ --updates "${_T}" \ --verbose "${_T}" \ --win32-loader "${_F}" \ --zsync "${_T}" \ "${@}" After reading Subhani's latest reply, and Subhani please don't call anything MichaelOS, there is much more to it that just a regular live build. Cheers. Michael. On 21/04/2020, jnq...@gmail.com <jnq...@gmail.com> wrote: > I've not really been following this thread, I've just previously given > it a brief read. > > I noticed this in the example config given: > >> --linux-flavours 686 amd64 > > This is obviously wrong, there needs to be quoting here! Could that be > the source of your problem? > > Also, I'm not entirely familiar with using the multi-flavour feature, > but I recall a mention of "686 amd64:amd64". > > On Tue, 2020-04-21 at 10:07 +1000, Michael . wrote: >> I just tried Subhani's tip and it failed with >> E: Error reading the CPU table >> P: Begin unmounting filesystems... >> P: Saving caches... >> E: Error reading the CPU table >> >> ... >> >> > > > > > > lb config --binary-images iso-hybrid --mode debian >> > > > --architectures i386 >> > > > > > > --linux-flavours 686 amd64 --distribution buster -- >> > > > > > > archive-areas >> > > > "main >> > > > > > > contrib non-free" --updates true --security true --cache >> > > > > > > true >> > > > > > > --apt-recommends true --debian-installer live >> > > > --debian-installer-gui >> > > > > > > true >> > > > > > > --win32-loader true --iso-application PakOS10.3 --iso- >> > > > > > > preparer >> > > > > > > subhaniminhas-https://sourceforge.net/projects/pakos/ >> > > > --iso-publisher >> > > > > > > subhaniminhas-https://sourceforge.net/projects/pakos/ >> > > > --iso-volume >> > > > > > > PakOS10.3 > >
