LinuxQuestions.org
Help answer threads with 0 replies.
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
  Search this Thread
Old 01-11-2014, 10:08 AM   #1
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,829

Rep: Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652
Recently Changed UDISK2 Rules


Greetings
I've noticed an annoying problem with automounts since upgrading to Slack 14. I'm confident I can fix it with specific declaration in "/etc/fstab", but then why do I even care about udisk2? The problem is that when I try to access many drives, a popup window asks for "authentication" but neither user nor root passwords are accepted.

This is what I presently have in "/etc/udev/rules.d/99-udisks2.rules"

Code:
 D_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1
 
Old 01-11-2014, 10:12 AM   #2
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2 and Slackware64 -current (AKA Slackware64 15)
Posts: 3,790

Rep: Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142
I don't understand the point of your post.
 
Old 01-11-2014, 05:57 PM   #3
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,829

Original Poster
Rep: Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652
I apologize for being less than firmly direct. I thought it would be obvious that if an authentication dialogue box pops up and will not accept the only 2 passwords that exist on the box, that it won't allow me, or anyone, access, until the rules specify who can have access. AFAIK udisk2 only recently began requiring authentication and it seems absurd to me that root password isn't sufficient to authenticate by default.

So, I would prefer to change the udisk2 rules so they behave with some modicum of good sense ie: specifying who can get in and with what authentication, not a requirement that has no solution. Why even pop up a dialogue if absolutely nothing can satisfy the conditions?

Last edited by enorbet; 01-11-2014 at 05:58 PM.
 
Old 01-11-2014, 09:48 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2 and Slackware64 -current (AKA Slackware64 15)
Posts: 3,790

Rep: Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142Reputation: 2142
What is the purpose of the udev rule that you posted? It is non-standard and it isn't obvious what it is doing.
 
Old 01-11-2014, 11:05 PM   #5
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,829

Original Poster
Rep: Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652
Greetings and thanks for responding. It is my understanding that it is Udisk2 that is responsible for defaulting to automounting non-system drives in "/media/user" and "/media/root". On this, my main PC I am the only user so I don't want any differentiation at all. I just want all to be mounted in the same place and I read that rule would do so here at http://pappp.net/?p=1290.

I know I took a chance because it was specified for udisk2 >= 2.09 and I'm using 1.98, but it was mounting in that utterly foolish manner and now it isn't. I just need to find how to set rules to properly authenticate. If I haven't found a udev rule for it, I guess I will just go back to firm declaration in "/etc/fstab" although that seems a step backward. The other possibility is trying to "upgrade" to a udisk2 version at or above 2.09.

He says on that page
Quote:
Originally Posted by pappp
No more tedious user,noauto,nofail fstab entries on all my machines, for all my frequently-used discs to prevent that behavior! Hurrah!
That sounds kinda nice
 
Old 01-12-2014, 02:35 AM   #6
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,460
Blog Entries: 15

Rep: Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040
Udisks2 shouldn't require any special rules or scripts. It's supposed to just auto-detect a new device, match the partition type to its library database, and mount it. In short, it's just supposed to work.

The latest version is udisks-2.1.1 by the way, however I'm uncertain if it can be used by Slackware as it requires gudev from the systemd-extracted-udev, and Slackware uses classic udev. I'm uncertain it 2.0.9 does or doesn't require this library.

Last edited by ReaperX7; 01-12-2014 at 02:40 AM.
 
Old 01-12-2014, 09:01 PM   #7
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,829

Original Poster
Rep: Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652
Greetings
Well it does just work... just badly. Unfortunately some fool programmer set defaults that create some problems and the interdependent nature of ALL of systemd stuff requires rules as the only means to edit how a device functions. Frankly I am grateful The Slackware Team has been slow to adopt much of this stuff. In a fight between convenience and solid, I'll pick solid every time.
 
Old 01-12-2014, 11:08 PM   #8
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,460
Blog Entries: 15

Rep: Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040
The good thing with udev is it can still be extracted from systemd safely along with other key components like gudev but yes the issue is getting worse. The concept of just working is getting to slowly become "if it works at all without ... It's a miracle".

Last edited by ReaperX7; 01-12-2014 at 11:12 PM.
 
Old 01-14-2014, 05:45 PM   #9
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,829

Original Poster
Rep: Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652Reputation: 3652
When KDE 4 was first released, if one declared a specific partition mount in /etc/fstab it would no longer show up in that handy bar on the left and CD/DVD would no longer properly automount. It seems as if this may have been fixed since I have declared all my ntfs-3g partitions in /etc/fstab and they still show up on the left bar now. I hope this behavior is basically global because on some boxes I have a lot of partitions and this is going to take awhile. I don't mind the work too much as long as it's fruitful.

Also I have another thread regarding the auto-refresh bug that is apparently fixed in Slackware 14.1 because it has upgraded KDE from 4.8.5 to 4.10.5. So I suppose I will do the entire system upgrade first and maybe this behavior is ixed as well. If not, I have 2 projects (at least)
 
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
I recently changed my password on Windows msrunner Linux - Newbie 3 07-17-2012 09:32 PM
cat: /etc/udev/rules.d/70-persistent-net.rules: No such file or directory rcg1984 Linux From Scratch 2 09-17-2008 07:02 AM
Shorewall rules mysteriously changed after system crash xnomad Linux - Security 1 06-28-2007 07:09 AM
Installed Ubuntu but it changed my boot loader. I want this changed... mdorries Linux - Distributions 8 05-31-2007 08:13 PM
motherboard recently changed! suse 8.0 mofo Linux - Hardware 1 03-03-2005 02:51 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:20 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration