This is still a problem. Isn't the primary purpose of `toram` to enable destructive action on the partition that held the ISO?
I spent DAYS trying to figure out what was wrong with my boot script for resetting student laptops (carts, wifi only so no PXE option). I finally figured out approximately what the problem was, spent $10 in AI tokens to code up a fix, and came here to report the bug and submit a possible patch... only to find the bug's been known, and a fix has been available for six years... and it IS a fix, since it's nearly identical to the fix the AI 'discovered', which I applied successfully to fix the patch and allow remote wipes of the laptop carts without any all my hacks. Either document the behavior of toram (the behavior that makes it not fit for purpose), or merge the patch. I don't understand why it's been left on the table. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684280 Title: casper toram forgets to disconnect loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/684280/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
