On Aug 15, 2014 7:21 PM, "Nico Kadel-Garcia" nkadel@gmail.com wrote:
On Fri, Aug 15, 2014 at 9:47 AM, Ondrej Vasik ovasik@redhat.com wrote:
On Fri, 2014-08-15 at 08:07 -0400, Nico Kadel-Garcia wrote:
On Thu, Aug 14, 2014 at 11:49 AM, Michal Schmidt mschmidt@redhat.com
wrote:
On 08/14/2014 12:17 PM, Matthew Miller wrote:
On Thu, Aug 14, 2014 at 10:06:11AM +0200, Ondrej Vasik wrote:
Actually I'm going to revert the /media -> /run/media change.
The above sentence is unfortunately ambiguous.
It is really not solving the issue it was trying to help with and
in
addition it might be fragile in some cases. Sorry for the noise.
Hmmmm... that should probablt be run through the change process...
it needs
release notes at least!
No, I'm sure Ondřej only meant that he'd revert the replacement of the /media directory with a symlink to /run/media, which was in
Rawhide
for only two weeks or so.
He does not intend to change the path where removable media get
mounted.
Michal
Ondrey, I hope that you meant you'd revert the entire change. and put removeable media mounting back in /media. I've still not seen a single reason for the move, only a bugzilla about getting it tot work correctly. Following the more recent File System hierarchy documents and putting it in the documented /media makes much more sense.
I just reverted the "two weeks in rawhide" symlink change already. /media is no longer symlink in Rawhide. Removeable media mount point is not under control of filesystem package (udisks2 mount them to /run/media/$USER/$Volname ). Based on Michal's suggestion, you can use UDISKS_FILESYSTEM_SHARED set to 1 to have removeable media mounted in /media instead of /run/media/$USER/ .
*sigh*. Then the default should have been to set UDISKS_FILESYSTEM_SHARED to 1. Let people who *want* it in the new "/run/media/$USER/mountdir" select it. And it's *still* a violation of even the most recent filesystem hierarchy standards, which discuss the use of "/run" and "/var/run" for pid files, not for removable media. Files in /run are supposed to be scrubbed or truncated at boot time!!!
Think I can get any traction getting that default reset at this point?
No, because:
- Security
- Automatically generated names will never reliably match you expectation in /media no matter what udisks does.
--Andy
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct