Amaury Pouly wrote:
> A simple solution would
> be to prevent opening opening a file for writing for example.

Gracefully handling read-only media requires at least a thorough review of the relevant file-writing code paths to ensure failure to write shows a (single) sensible message to the user and fails in a sane way.

It's probably even better to have a media flag that the code can check to completely avoid going into those code paths. If a user has the media write protected by choice, she will not want to be annoyed by error messages about it.

-- 
Björn