1. Content of .iso file under 99% scenario, is readonly. As far as mount is concerned, it doesn't even have the capability to modify the content of .iso file, it wouldn't make sense to specify 'rw' for mount anyway, not to mention updating the metadata of .iso file this is just too far stretched.
2. In manual it says 'ro Mount the filesystem read-only.' 100% of our use cases would interpret this option as applicable to the content, wouldn't it? But we are talking about the metadata of the .iso file being modified. This is just wrong.
mount should just leave the cd/dvd/blueray etc image file untouched. period.
Bug or not, this is a very bad one.
1. Content of .iso file under 99% scenario, is readonly. As far as mount is concerned, it doesn't even have the capability to modify the content of .iso file, it wouldn't make sense to specify 'rw' for mount anyway, not to mention updating the metadata of .iso file this is just too far stretched.
2. In manual it says 'ro Mount the filesystem read-only.' 100% of our use cases would interpret this option as applicable to the content, wouldn't it? But we are talking about the metadata of the .iso file being modified. This is just wrong.
mount should just leave the cd/dvd/blueray etc image file untouched. period.