[SOLVED] How to restore mounting in /media, not /run/media ?

Linux.tar.gz · 10-11-2012, 11:22 AM

Enough of this crap !
Many programs are not aware of this and are still searching in /media.

Is there a way to restore the old behavior, and mount medias in /media ?
Or at least to make a symlink ?

MensaWater · 10-11-2012, 12:14 PM

Does the following not work?

Code:

ln -s /run/media /media

Have you checked your /etc/auto* files for automounter to see if they're specifying /run/media? If so what happens if you change that to "/media" in those files?

Linux.tar.gz · 10-11-2012, 01:17 PM

Can't link, because there's the username in the path, ie. /run/media/my_name/drive_id

Auto-stuff isn't used, it's udisk2 that manages drives now.
As far as i understand, it's another intrusive gnome-crap.
The most criminal thing in it is that there's absolutely no default compatibility layer in it, which leads me to the conclusion that the guys behind this are total idiots.

Linux.tar.gz · 10-11-2012, 11:19 PM

I removepkg'ed the s**t named udisks2, but still no luck...

jtsn · 10-12-2012, 12:00 AM

Debian has made a patch for udisks2 to restore the FHS-compliant behaviour. You can apply it to the udisks2.SlackBuild by using the attached files. (You have to remove the .txt extension, because this forum software doesn't accept .diff or .patch as an attachment).

HTH.

jtsn · 10-12-2012, 12:28 AM

The Debian patch above uses /media/$USER instead of /run/media/$USER. For Slackers, who don't like this solution, I crafted an alternative patch, which uses plain /media just like the old hald.

Woodsman · 10-12-2012, 12:35 AM

Looks like this is the commit:

http://cgit.freedesktop.org/udisks/c...37ed543178965b

Seems to me /media and /run/media/$USER should be a build option or an /etc/ config option. The latter is better and allows everybody to choose and be happy.

jtsn · 10-12-2012, 12:45 AM

Quote:

Originally Posted by Woodsman

Seems to me /media and /run/media/$USER should be a build option or an /etc/ config option. The latter is better and allows everybody to choose and be happy.

Right, hard-coding paths into the source code is very bad behavior, such things belong to a configuration file. Also I found another correlation between bad software design and bad coding style (two-space indents? seriously?).

fgcl2k · 10-12-2012, 01:56 AM

Quote:

Originally Posted by jtsn

Also I found another correlation between bad software design and bad coding style (two-space indents? seriously?).

O.T.
Welcome to the GNU Coding Style :-)

BlackRider · 10-12-2012, 03:04 AM

It is no surprise for me that developers are trying to scape from this crap, spawning things like udevil. It is sad I see no alternative project receiving support enough to kick the udev/disks2 mess off.

You can have a look at udevil here: http://ignorantguru.github.com/udevil/

Linux.tar.gz · 10-12-2012, 10:44 AM

Thank you jtsn, it worked like a charm !!!

And thank you all other ;^).

GazL · 10-12-2012, 12:45 PM

Am I the only one still using automount for this sort of stuff?

Linux.tar.gz · 10-12-2012, 07:15 PM

I plan to use automount since a while ago, but always have something else to do ^^.

I used it for nfs network connections. Worked great.

Richard Cranium · 10-12-2012, 08:20 PM

Quote:

Originally Posted by Linux.tar.gz

Can't link, because there's the username in the path, ie. /run/media/my_name/drive_id

I don't see how that stops you from symlinking /run/media to /media

Linux.tar.gz · 10-12-2012, 10:19 PM

Because i need to know the username.
And because programs are looking in /media/drive_name/* , so as the username adds a directory level, they fail.