Actually you can pass custom live-build options. Do it that way:
./build.sh --distribution sana --verbose -- <your options here>

Hi Raphael,

does it mean, I can add the same options to ./build.sh as I add to lb config?

I have now:

lb config -a i386 --bootappend-live "boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

then

lb build

So must I now do so?

lb config -a i386 --bootappend-live "boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

then

./build.sh --distribution sana --variant lxde --bootappend-live "boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

The manual of live-build is makimg those things not clear and describes the only the old way. I will be happy for enlightenment!

Best

Hans

You know build.sh is a simple shell script, you can read it :-)

The architecture option is handled by build.sh but not the --bootappend-live. Thus you need to put "--" before putting any unknown option that you want to forward to "lb config".

The correct call for you would be this one:
./build.sh --arch i386 --distribution sana --verbose -- --bootappend-live "boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

(no need to call lb config beforehand)

Reassigning to muts so that he can update the documentation on the website.

In Kali 2016.1 and higher

./build.sh --arch i386 --distribution kali-rolling --variant lxde --verbose -- --bootappend-live "boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

is working well!

I will try the "old" style (lb config --** , lb build) that is recommended by the live-build-manual again, so that apt-cacher-ng can be used again (the above ./build.sh-style starts with the command "lb clean --purge").

If that is working, I will report here, so that bugreport can be closed.

Hans

Bug can be closed, I found a solution. Thank you for all the tips and hints!
The command lb is working, too, at the moment.

It is working well at the moment.
So this bugreport can safely be closed.

Thank you for all the help!

Best

Hans

Asked to be closed