On 08/17/2014 12:31 PM, Nico Kadel-Garcia wrote:
On Sat, Aug 16, 2014 at 1:54 PM, Jon jdisnard@gmail.com wrote:
The rationale here is that media mounts for a seated user are part of that users run-time, or session. By placing them in an area exclusive to the seated user, the system as a whole is more secure.
And that could have been put at "/media/$username/$medianame". Not one part of that security practice change required using "/run" Calling stored content, typically used across multiple sessions and often used for archival or non-writable storage, part of the "run-time" data is a serious misreading of what the "run-time" data of the FHS spec describes. The language is clearly aimed at PID data and similar boot-time erasable data.
I've never personally used attachable media that I scrubbed, or expected to be scrubbale, with everey reboot.
The media would not get scrubbed since it is not yet mounted at that point in the boot sequence. What _does_ get scrubbed is any leftover /run/media/$USER directories and the temporary mount points they contain, which is arguably preferable to allowing that cruft to accumulate in /media.