http://bugzilla.suse.com/show_bug.cgi?id=1099548 http://bugzilla.suse.com/show_bug.cgi?id=1099548#c5 --- Comment #5 from Marcus Schaefer <ms@suse.com> ---

is kiwi something special and only for openSUSE?

nope, we address all distributions The dracut upstream modules handling livenet are 90livenet and 90dmsquash-live whereas livenet calls dmsquash-live once livenet has loaded the data from the pxe server. The 90kiwi-live dracut module is based on overlayfs not dmsquash and as of today implements this variant plus the upstream features of iso-scan. We didn't had time to implement support for livenet in that module so far which is the reason why you ran into the issue The structure to of the live iso from a data perspective is the same as upstream defines it. Therefore you have the choice to either use dmsquash from upstream (including its livenet support) or the overlayfs based variant we added as a plus. The decision for a) or b) is done in the KIWI image description with: <type ... flags="overlay" | "dmsquash"/> afaik the SUSE live images specifies "overlay" or nothing which then defaults to this module * Feel free to open an issue on https://github.com/SUSE/kiwi to remind us for adding livenet integration of the upstream module to the kiwi-live dracut module * Changing to upstream dmsquash will bring back the feature you want but imho requires rebuild of the live image with the flags set to dmsquash. This can be done by branching the project in obs and change the flag Hope this helps -- You are receiving this mail because: You are on the CC list for the bug.