Constantino Michailidis

I saw the message. Looks good... very helpful and informative IMHO.

Since I have ocs_daemonon="ssh" set, I was logged in via ssh... it makes testing easier. The strange colors are custom for my rxvt-unicode terminal via ~/.Xresources :-) So the screenshot is of a clonezilla live environment (PXE booted from the network). Naturally, the same problem happens at a console... but, again, only if clonezilla is PXE booted from the network. I think you should be able to reproduce the problem without much trouble.

You're saying I should be able to create an iso when clonezilla is PXE booted from the network, correct? I wonder what's causing this error message then?

I think it's because the latter looks more like sed or perl to me. Naturally, this clears things up a fair bit... https://www.gnu.org/software/bash/manual/bash.html#Shell-Parameter-Expansion

Also, assuming the patch is useful, I copy/pasted the following bash string replacement to report the script name: ${0##*/} but in retrospect, I think this one is more readable: ${0/#*\//} and may amount to the same thing; I'm certainly not the final authority on bash scripting. :-/

The directory structure is as so: . ├── efi32 │ ├── ldlinux.e32 │ └── syslinux.efi ├── efi64 │ ├── ldlinux.e64 │ └── syslinux.efi ├── filesystem.squashfs ├── initrd.img ├── ldlinux.c32 ├── notes.txt ├── pxelinux.0 ├── pxelinux.cfg │ └── default └── vmlinuz 3 directories, 11 files Also, you may find my pxelinux.cfg/default file attached.

ocs-iso functionality broken when booting via network PXE

:-)