Report: Mylivecd behaviour and the 4GB limit

[Gagarin Gambit]

Yesterday I was on the process of creating my monthly backup remaster, and it proved to be more than the 4GB limit. When this had happen again some time ago (it might be so long ago that I was using the previous version of the remaster script, the one which included a gui), I received the message "something went wrong" and the script aborted without creating an iso. But this time a 4GB iso was created, and the command line was stuck in printing countless equation marks =====================

OK, it was no problem for me, I aborted the script manually, deleted the iso and the temporary files, and created a new remaster which included less data, resulting in a successful 3.8GB remaster. But, if what I saw is the default behaviour of trying to create a remaster exceeding the size limit, than it's clearly completely confusing for someone with no experience of creating remasters. If there is someone actively maintaining mylivecd, I believe that its behaviour in the event of failure should be modified.

[Just17]

You didn't perchance make a copy of the konsole output?  If yes please post it.

Did you test the created ISO to see if it worked or if all the required files were present?

Usually if the squashfile is over size the creation of the ISO fails, so what you are reporting does not seem like the usual behaviour.

I have no idea who, if anybody, is maintaining mylivecd presently.

[Gagarin Gambit]

I didn't bother testing the iso. I suspected it might fail because of the size, that's why I tried immediately afterwards (though judging by the size of the successful iso, it should be for a few MB, 100 at most). As for the konsole output... that's very easy

Code: [Select]

========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================It was the same when I scrolled all the way up. I'm sorry, I have no more information.
Oh. I didn't mention that the second time I didn't include the --md5sum option.

[Just17]

I didn't bother testing the iso. I suspected it might fail because of the size, that's why I tried immediately afterwards (though judging by the size of the successful iso, it should be for a few MB, 100 at most). As for the konsole output... that's very easy

Code: [Select]

========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================It was the same when I scrolled all the way up. I'm sorry, I have no more information.
Oh. I didn't mention that the second time I didn't include the --md5sum option.

Maybe it was calculating the MD5sum when you killed it ......... and thus never got to embed the MD5sum in the ISO .....