Am 10/05/2017 um 12:15 PM schrieb Johannes Meixner:
Or alternatively you may try "mksusecd" ... ... until now I used the y2mkiso from the yast2-product-creater. Is there a major difference between them? Or is the result the same?
How funny! Because SUSE's genisoimage does not work out of the box some kind of "freak show of four alternatives" emerged. I have no idea in which particular ways those little monsters may or may not differ.
Hello Johannes, I've looked over the help of mksusecd. It seems to do automatically what I did by my own script. But: - I have modified isolinux.cfg which special boot entrys for different hardware. Same for the grub2. Are they overwritten when I use mksusecd? - The content is signed with a gpg key which is protected by a passphrase. With my script I use gpg via batchmode and it gets the passphrase from a textfile. Does mksusecd support that scenario? - mksusecd need root privilegs, my script runs as user. That are the stumbling blocks I figured out till now. Who is the maintainer of that script? Looks great so far. Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds@marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org