LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 10-13-2012, 02:47 PM   #16
Slackovado
Member
 
Registered: Mar 2005
Location: Burnaby, BC, Canada
Distribution: Slackware 14 32bit, Debian, Arch
Posts: 213

Rep: Reputation: 27

Quote:
Originally Posted by Linux.tar.gz View Post
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.
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.
 
Old 07-12-2013, 05:00 AM   #17
Linux.tar.gz
Senior Member
 
Registered: Dec 2003
Location: Paris
Distribution: Slackware forever.
Posts: 2,223

Original Poster
Rep: Reputation: 86
Is there a new version of these patches around for the Slackware -current ?
The -current udisks2 is 2.1.0 .

Last edited by Linux.tar.gz; 07-12-2013 at 05:09 AM.
 
Old 07-13-2013, 05:53 AM   #18
chemfire
Member
 
Registered: Sep 2012
Posts: 67

Rep: Reputation: Disabled
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.

Last edited by chemfire; 07-13-2013 at 05:54 AM.
 
Old 07-13-2013, 08:57 AM   #19
the3dfxdude
Member
 
Registered: May 2007
Posts: 304

Rep: Reputation: 66
Quote:
Originally Posted by chemfire View Post
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.
 
Old 09-01-2013, 11:10 AM   #20
Linux.tar.gz
Senior Member
 
Registered: Dec 2003
Location: Paris
Distribution: Slackware forever.
Posts: 2,223

Original Poster
Rep: Reputation: 86
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.
 
Old 09-01-2013, 01:36 PM   #21
STDOUBT
Member
 
Registered: May 2010
Location: Stumptown
Distribution: Slackware 14.0~xmonad @ 32bit flavor on a T60p (2007-YS3)
Posts: 249

Rep: Reputation: 59
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
 
Old 09-01-2013, 03:20 PM   #22
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,427
Blog Entries: 14

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
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.
 
Old 09-01-2013, 03:26 PM   #23
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,427
Blog Entries: 14

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
Quote:
Originally Posted by jtsn View Post
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.
Patrick should look into this.
 
Old 09-01-2013, 03:49 PM   #24
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620
Quote:
Originally Posted by ReaperX7 View Post
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.
 
Old 09-02-2013, 03:32 AM   #25
GazL
Senior Member
 
Registered: May 2008
Posts: 3,231

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
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.
 
Old 09-02-2013, 07:53 PM   #26
Jenni
Member
 
Registered: Oct 2011
Distribution: Slackware, Fedora
Posts: 158

Rep: Reputation: Disabled
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.
 
Old 09-03-2013, 11:49 AM   #27
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 691

Rep: Reputation: 276Reputation: 276Reputation: 276
Quote:
Originally Posted by volkerdi View Post
You could try to take your concerns to upstream, but I doubt you'd have much luck.
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.
 
Old 09-03-2013, 11:55 AM   #28
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 691

Rep: Reputation: 276Reputation: 276Reputation: 276
Quote:
Originally Posted by chemfire View Post
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.
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.
 
Old 09-03-2013, 12:13 PM   #29
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 691

Rep: Reputation: 276Reputation: 276Reputation: 276
Quote:
Originally Posted by Linux.tar.gz View Post
Is there a new version of these patches around for the Slackware -current ?
The -current udisks2 is 2.1.0 .
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.
 
Old 09-04-2013, 04:05 PM   #30
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,427
Blog Entries: 14

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Android media players hot up LXer Syndicated Linux News 0 03-21-2011 11:21 PM
Media streaming between WMP and Linux media players (preferably Amarok) EducatedWhiteTrash Linux - Software 2 08-20-2010 08:11 PM
Can I install Media Jukebox 12 with Ubuntu OS? Needs Windows Media Player Files. tlcmd Linux - Newbie 2 01-08-2010 03:29 PM
hot to make vlc defualt media player negrito211 Linux - Software 4 01-03-2009 11:23 AM
Storage Media Lost Hot Plugging issue evodawg Mandriva 3 08-10-2008 02:05 PM


All times are GMT -5. The time now is 03:19 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration