This shouldn't be in Slackware at all.
Gnome is the "Trojan horse" of Linux. Destroying Linux one commit at a time.
Distros need to put a stop to this and stop including this crap.

Is there a new version of these patches around for the Slackware -current ?
The -current udisks2 is 2.1.0 .

I appreciate everyones frustration. Its annoying when stuff moves around breaking your shell scripts and the assumptions made by other software. Personally I'd like to see things go back to sub-directories under /mnt I don't know why I need yet another top level file system directory.

That said I do think /{some-directory}/$user/$device is a better model; than /{some-directory}/$device. On multiuser systems it makes the ACL management easier and reduces naming conflicts. So maybe we should not hate on the udisks developers to much, or at least find better reasons.

We are not hating on the developers. We are not saying one option is better than another. The problem is that udisks made a change and did not make it optional while breaking the behavior of other software in the process. If it was configurable, then the devs would not get the rep of pushing things through or designing it poorly.

So is there any clean patch around ?

I tried to tweak the old one, but it ended with not deleting drive folders in /media/ when unplugged.

Just FWIW,
I don't have any desktop environment installed on my 14.0, and I use worker (file manager) which now prompts to "mount and cd" but only when worker is the focal window. This is ideal for me. Even better, there is no mounting under /run at all. worker somehow defaults to /media/whatever/

/FWIW

I wish GNU/Linux had never picked up that Godless, unholy, spawn of Satan project named udev.

DevFS/DevTmpFS, HALd, and Hotplug worked just fine IMO without all this babysitting bullsh*t we now have... udisks, udisk2, udevil, systemd... bah! Just more laziness, automation, and Windows-isms being shoved down our throats we could have, and should have said, "No thank you!" to a long time ago.

I wish Patrick could perform an exorcism and rid us of this vile hellspawn of udev, and find a way to import DevD from BSD into Slackware, and we could have the more sane, traditional, and easier to manage hald, hotplug, and DevFS back.

1 members found this post helpful.

Patrick should look into this.

I think it would just lead to more problems as software looks to the canonical path set by upstream and can't find things because we're moved them someplace else. I'm not personally thrilled about stuff like this being a moving target either, but in most cases Slackware won't attempt to swim against the current. You could try to take your concerns to upstream, but I doubt you'd have much luck.

Or you can do like I have and ignore all the modern gui related volume-management stuff and use an automount/autofs solution. I think Pat is right: trying to swim against the current isn't sensible; but sometimes getting out of the water and walking along the bank is a better option.

If you're constantly inserting/removing devices that your system has never seen before then maybe automount/autofs isn't going to be practical, but if like me you have half a dozen flashdrives that you can pre-register in an autofs map file then it's quite workable.

Huh, I just mount things with the mount command so I guess this change never really struck me as particularly significant. I really don't like having /mnt /media AND /run all for basically the same job, but that's not really the fault of the slackware team, that's all upstream nonsense, and fixing it would just be a lot of work and involve a lot of breaking things. Besides that, fixing it would go against one of the reasons I love slackware - very little actually being changed from upstream.

Until all the programs you are using that care about such things are updated to look in the new place, you should just look into a different solution that works, like the GazL recommended. Or you could forgo the automation and just mount things manually to wherever you need them, if that's a practical option for you.

This part of the arch wiki may be of interest to you though:
https://wiki.archlinux.org/index.php...nt_to_.2Fmedia


In the mean time you can tell the folks who are actually responsible for the move to another new location (presumably the udisk developers) about your disapproval, but I somewhat doubt they care.

Upstream isn't interested in any concerns. That's the issue here. Especially they will not get rid of /lennart (aka /run).

Last time I looked the FHS required /media for removeable media. Not /run/fancy/systemd/mount/point.

At least on 14.0 the patched udisks now works flawless in everyday usage.

It doesn't make sense, if you have devices with proper unix filesystems on it with file-based permissions, shared between multiple users. Because mounting them multiple times isn't going to work.

I will look into it, once Slackware 14.1 is out. Before the package versions are finally fixed and the result can be tested reliably, creating patches would be just a waste of time. I will also check the option of simply going back to the already proven modified udisks2-1.98.

Precondition is, that I consider upgrading to 14.1, of course. Currently I'm fine with Kernel 3.8 and I still need hald for compatibility reasons. I have no idea if this is going to work with the next -stable.

HAL works on modern kernels and Linux platforms. There are patches to build it on modern systems. I have it working on mine just fine along with Hotplug.

My next goal is to exorcise udev off my system in favor of mdev.