Regarding ISO9660 level 4, it is supported by mkisofs (search for an updated mkisofs' manual) from cdrtools.
So, "level 4" is an adequate option for UBCD, especially considering that advance users would be using the script so as to generate a customized UBCD.
Now, for the main issue...
When using the original script without patching it, please note that the first argument is the root _directory_ of the extracted (and optionally modified) ubcd tree.
I would suggest a test, using "root" (or superuser or sudo) permissions:
Note that the first argument of the ubcd2iso script ends with a slash ("/") character (indicating a directory). Please use it.
Please let us know the result.
So, "level 4" is an adequate option for UBCD, especially considering that advance users would be using the script so as to generate a customized UBCD.
Now, for the main issue...
When using the original script without patching it, please note that the first argument is the root _directory_ of the extracted (and optionally modified) ubcd tree.
I would suggest a test, using "root" (or superuser or sudo) permissions:
Code:
cd ~/Downloads/ubcd537-extracted/ubcd/tools/linux/ubcd2iso/
chmod a+x ubcd2iso.sh
.ubcd2iso.sh ~/Downloads/ubcd537-extracted/ ~/foo.iso
chmod a+x ubcd2iso.sh
.ubcd2iso.sh ~/Downloads/ubcd537-extracted/ ~/foo.iso
Note that the first argument of the ubcd2iso script ends with a slash ("/") character (indicating a directory). Please use it.
Please let us know the result.