I tested the bugfix with the Xubuntu Focal daily iso file in BIOS mode using the boot option 'toram', and it works :-)
See the attached screenshot: A casper-rw was not mounted; it was not even created. After that I rebooted without any extra boot option. The casper-rw partition was created and mounted to /var/crash and /var/log and /var/log was busy, could not be unmounted. 'As usual' with this new feature. Then I rebooted using the boot option 'toram', and it works, also when there is a casper-rw partition. It is not mounted :-) I tested also with the boot option 'persistent' works as expected (with and without 'toram') and did some basic checking in UEFI mode too. Everything seems to work as expected. Thank you Michael :-) -o- Olivier Robert raised the issue concerning what should be the default. Maybe it can be discussed here, maybe there should be another forum for that discussion, for example a new bug report or the Ubuntu Forums. ** Attachment added: "casper_1.432_fixes_bug_1851123_in_focal_daily_iso_file.png" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5305326/+files/casper_1.432_fixes_bug_1851123_in_focal_daily_iso_file.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851123 Title: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
